Projects

READ-ONLY

This board is live — clear it and/or press e to make your own. You can then Export it host it yourself. (Nothing you change here touches the published copy.)

Keyboard — move

h j k lMove the cursor: lane left / down / up / lane right. Arrow keys do the same. g gFirst card in the lane GLast card in the lane 0Leftmost lane $Rightmost lane 3 jCounts work on any motion

Keyboard — change

These need edit mode — press e first.

H J K LCarry the card with the cursor. Shift + arrows do the same. i Open the card for editing (Enter too) oNew card below the cursor · O above bMark what it's waiting on · b again clears it SpaceTick the next open step on the checklist d dDelete the card into the register y yCopy the card into the register pPaste below the cursor · P above AAppend a lane uUndo · U redo

Keyboard — everything else

eToggle edit mode /Filter. Motions still work on what's left. ?This panel EscClear the count, then the filter, then the cursor. Closes any open panel first.

The mode line sits bottom right, and shows pending keys as you type them.

Keyboard — checklists

s drops the cursor into a card's checklist; the card opens out and the mode line reads STEPS. The keys mean the same things one level down.

sEnter the checklist. On a card without one, starts it. j kWalk the steps SpaceTick or untick · x does the same J KReorder the step oNew step below · O above iRename the step in place (Enter too) d dRemove the step EscBack to the board · h and s too

Editing a step happens on the card itself — Enter commits, Esc discards. Outside the checklist, Space still ticks a card's next open step without descending into it.

Publishing, hosting, and the JSON

How publishing works

The board renders whatever is in board.json sitting next to this file. Editing here changes only your own browser's copy — anyone visiting can toggle edit too, and it never touches what you published.

To update a DEN board: edit → Export → drop the new board.json next to index.html → deploy.

Cloudflare Pages

Once, to make the project and take the domain:

npx wrangler login
npx wrangler pages project create den \
  --production-branch main

Then every publish is ./publish.sh — it checks the JSON, keeps the last one as board.bak.json, and uploads index.html, board.json and _headers from a staging directory, so nothing else in the folder goes public by accident. Point it at a fresh export to take that first:

./publish.sh ~/Downloads/board.json

Connecting the repo to Git instead would publish the app without the board — board.json is data, and stays out of version control.

Your own VPS

It's two static files — any web server will do. With Caddy:

board.example.com {
    root * /srv/board
    file_server
}

Then scp index.html board.json vps:/srv/board/ after each export. Add basicauth on a /edit path if you ever want the write side gated.

The JSON

Hand-editable if you wish. Lanes hold cards, ids are strings, dates are ISO 8601.

{
  "schema": "kanban.v1",
  "title": "Projects",
  "lanes": [{
    "id": "l1",
    "name": "Building",
    "tone": "hot",
    "cards": [{
      "id": "c1",
      "title": "Public project board",
      "note": "Optional detail.",
      "tags": ["web"],
      "link": "https://example.com",
      "created": "2026-07-08T10:00:00Z",
      "updated": "2026-07-28T09:00:00Z",
      "moved": "2026-07-26T18:00:00Z",
      "movedFrom": "To do",
      "movedBy": 1
    }]
  }]
}

moved is stamped whenever a card crosses into another lane — the card then reads → moved 2d ago instead of its edit date, and wears a hot mark for the first three days. Reordering within a lane isn't a move.

movedBy is how many lanes it crossed and which way: positive is rightward, one arrow per lane. Leave it out and it's worked back out from movedFrom; leave all three out for a card that has never travelled.

Starting clean

Clear board, top right, wipes everything back to three empty lanes and drops you into edit mode. Your published board.json is untouched until you export a new one and deploy it.