snapboard documentation
Choose a version
Version 0.2.5
SnapBoard is archived and active development has ended. It is not part of current SnapDock and was never integrated with it. These pages are retained for historical and technical reference; workflow instructions describe the final archived alpha implementation.
SnapBoard Archive #
SnapBoard was a lightweight, local-first kanban experiment for personal boards, columns, Markdown cards, and local file references. Development stopped at the 0.2.5 Alpha codebase. The repository was subsequently marked archived.
The final source contains a functional core alongside unfinished UI wiring. This archive distinguishes what users could reach in the final interface from state methods and interaction prototypes that existed only in code.
Archive Contents #
- Archived Usage Guide — how the final application was built, launched, and used
- Boards & Columns — the board model and the limits of the final interface
- Cards & Markdown — implemented editing, rendering, attachments, and incomplete interactions
- Storage & Persistence — the actual JSON schema and save path
- SDWS & SnapDock Integration — the proposed integration that was not implemented
- Archive Status & Support — final status, limitations, and historical reporting information
Final Implementation at a Glance #
The application used Electron with a CommonJS main process, a context-isolated preload bridge, and a bundled browser renderer. It created a default board with To Do, Doing, and Done columns, rendered Markdown cards locally, and saved one JSON document beneath Electron’s per-user application-data directory.
The following areas remained incomplete at archival:
- the sidebar displayed board controls but did not wire board listing, creation, switching, renaming, or deletion;
- card movement and several card-opening handlers used obsolete selectors and did not operate on the final rendered markup;
- column deletion used an obsolete layout selector;
- file references were stored but could not be opened from the card;
- no board import, board export, SDWS generation, or SnapDock integration existed;
- packaging configuration existed for Windows and Linux, but automated release builds had been disabled.
Relationship to SnapDock #
SnapBoard was described as part of the broader SnapDock ecosystem and optional integration was a historical ambition. No integration bridge, workspace provider, supported interchange format, or SnapDock consumer was completed. For the maintained writing application, use the current SnapDock documentation.