dotodo

A local, Markdown-driven project management app. dotodo puts a tactile interface on top of Markdown so you can manage projects visually while keeping your data portable and text-first.

What you can do

• Use a visual interface on top of Markdown to manage projects
• Work directly in the UI and export project state as Markdown
• Load a board from an existing Markdown file
• Link a local Markdown file so file edits update the UI
• Update tasks in the UI and sync those changes back to the file
• Keep your project and project management together.
• Integrate with coding agent to plan and act upon tasks.

dotodo-smaller.mp4

Agent Instruction : add this to your AGENT.md file

dotodo — Markdown Task Editing Instructions

Use the Markdown format below to update tasks. You may:

• Update status by moving tasks under the correct section.
• Create new tasks by adding new lines (omit id to create).

Format

Project: Name (id:UUID) # optional, do not change id unless instructed

TODO

IN PROGRESS

DONE

• (id:UUID) [feature|medium] Task title - Optional description

Rules

• Status is determined by the section header (TODO / IN PROGRESS / DONE).
• To create a task, omit (id:...):
  • - [ ] [feature|low] New task title - Description
• To update a task, keep its (id:...) and edit title/description.
• Description comes after " - " on the same line. Remove it if not needed.
• Keep type as feature or bug. Priority is low, medium, or high.
• Move tasks to the correct section to change status.

Template

Project: NAME (id:UUID)

TODO

• [feature|medium] New task title - Short description

IN PROGRESS

• (id:EXISTING-ID) [bug|high] Existing task title - Updated description

DONE

• (id:EXISTING-ID) [feature|low] Completed task title - Final notes

Examples

Create:

• [feature|medium] Add onboarding hints - Guide new users through actions

Update:

• (id:abc123) [bug|high] Fix sync race - Handle file update conflicts

Move to done:

DONE

• (id:abc123) [bug|high] Fix sync race - Handle file update conflicts

How to use

visit the official app : https://dotodo.dev

run the app yourself

1. Open index.html directly, or serve the folder for file-linking features:

python -m http.server 8000

2. Visit http://localhost:8000.
3. Create a project, add tasks, drag cards between columns.
4. Use Markdown pane to import/export board state.
5. (Optional) Link a Markdown file for live sync (requires HTTPS/localhost).

How the code works

• index.html is the entry point and UI layout.
• css/styles.css defines the skeuomorphic hybrid theme, depth system, and typography.
• js/app.js wires UI interactions, keyboard shortcuts, rendering, and data flow.
• js/db.js provides IndexedDB storage for projects, tasks, and file links.
• js/markdown.js handles Markdown parsing and export.
• js/linker.js wraps the File System Access API for optional file sync.
• js/ui/ contains dialog and toast widgets used by the app.

Data flow (high level)

1. openDB() initializes IndexedDB stores.
2. BoardUI loads projects + tasks into memory.
3. UI interactions update the store and cache, then re-render columns.
4. Markdown or file linking read/write passes through markdown.js and linker.js.

Notes

• Data is stored locally in IndexedDB and localStorage.
• Clearing site data resets boards.
• File linking works only in secure contexts (HTTPS/localhost).

File sync details

• The linked Markdown file is the source of truth.
• External edits to the file are reflected in the UI and IndexedDB on the next sync cycle.
• New tasks added without ids are assigned ids, synced into the UI, then written back to the file immediately.
• Tasks removed from the file (TODO / IN PROGRESS / DONE) are removed from the UI and IndexedDB.
• If there is any conflict, the Markdown file wins.