SnapBoard is the next major addition to the SnapDock ecosystem. It begins as a lightweight, minimal, offline‑first kanban board — but its real purpose is much bigger. SnapBoard introduces the idea of a virtual workspace, a way to organise writing and Markdown‑based work that doesn’t fit inside a traditional folder structure. This page explains the concept, why it matters, and how SnapBoard and SnapDock will eventually work together.
SnapDock has always been built around code‑style workflows: load a folder, browse the file tree, open files, edit, save. That model works perfectly for development, but writing is different. Markdown moves across repos, projects, and tasks. A single day might involve editing README files in multiple repos, drafting notes, and preparing documentation — none of which live in one neat folder.
SnapBoard exists to bridge that gap. It gives writers, maintainers, and multi‑repo developers a way to organise their work in a way that reflects how writing actually happens: fluidly, across boundaries, and driven by tasks rather than directories.
Most entries in DocsHub describe features you can already use. SnapBoard is different. It’s still early, but the concept needs to be documented now because:
SnapBoard is not just “another app” — it’s the missing piece that lets SnapDock evolve beyond folder‑bound work.
A virtual workspace is a collection of files, notes, and tasks that behave like a workspace inside SnapDock, but don’t come from a single folder on disk.
Instead of loading a directory, SnapBoard lets you build a workspace out of:
SnapDock will then load this virtual workspace and render it in the file tree exactly like a normal workspace — but the files can come from anywhere.
This unlocks workflows that were previously impossible, such as:
SnapBoard keeps the familiar kanban layout — columns, cards, drag‑and‑drop — but each card can represent more than a task. Cards can contain:
When you’re ready to work in SnapDock, you’ll be able to:
From SnapDock’s perspective, it behaves like any other workspace — open files, edit, save, navigate — but the underlying structure comes from SnapBoard, not the filesystem.
This creates a seamless loop:
SnapBoard is the foundation for a more flexible ecosystem. It enables:
It also sets the stage for SnapDock 3, which will be built with virtual workspace support in mind.
SnapBoard is still in early development. The layout, drag‑and‑drop system, and core kanban behaviour are being built first. Virtual workspace export will come next, followed by integration with SnapDock.
This page will expand as the concept solidifies and the implementation becomes available.
SnapBoard will grow into a central part of the ecosystem. As development continues, this entry will gain sections covering:
For now, this page serves as the conceptual foundation for everything SnapBoard will become.
The SnapDock ecosystem is growing, and a lot of the foundation is being built right now. If you’re a developer or writer who wants to get involved early, there’s room to help shape how these tools evolve.
The ecosystem is looking for:
If that sounds like you, reach out and get involved at the ground level.