Archived Usage Guide

Archive notice: These instructions describe the final SnapBoard 0.2.5 Alpha source. SnapBoard is no longer developed or supported and is not part of current SnapDock.

What Was Available

The repository configured desktop packages for:

• Windows through an NSIS installer;
• Linux through AppImage and Debian packages.

The README historically listed Windows 10 or later and Linux as its targets and said macOS was unavailable. The Electron main process contained normal macOS window lifecycle handling, but no macOS package target or release workflow was configured. WSL and hardware/performance figures in the old documentation were README claims rather than verified application constraints, so they are not treated as guarantees here.

Running the Archived Source

The source requires Node.js and npm. From a checkout of the archived repository:

npm install
npm start

npm start launches Electron directly. The build command first bundles the renderer with esbuild and then invokes electron-builder:

npm run build

The package metadata targeted SnapBoard-Setup.exe on Windows, SnapBoard.AppImage on Linux, and an amd64 Debian package. The repository’s automated build-and-release workflow was commented out when the project was archived, so these commands are historical developer instructions rather than a maintained installation path.

First Launch

With no saved data, SnapBoard created one board named My Board with three columns:

1. To Do
2. Doing
3. Done

The final reachable workflow was:

1. Use Add Column to add an empty column.
2. Use + Add Card at the bottom of a column to open the card editor.
3. Enter a title and Markdown body.
4. Optionally drop one local file into the editor’s attachment area.
5. Select Save or press Ctrl/Cmd + S.
6. Double-click a column name to rename it.
7. Delete a card with its X button.

The editor could also be closed with Esc, its close button, its cancel button, or a click outside the dialog.

Important Final-Build Limitations

Some controls were visible but not connected to working behavior:

• New Board and the board list had no renderer logic, despite multiple-board methods existing in the state module.
• Existing cards could not be reopened through the final rendered UI because the handler used an obsolete card selector.
• Card reordering and movement between columns were similarly disconnected from the final markup.
• Column deletion used an obsolete layout selector and could fail.
• A stored file attachment was displayed by name only; the app did not open, copy, validate, or embed the file.

Changes were saved locally as JSON after a short debounce. See Storage & Persistence for the exact model.