Writing

Complete & incomplete

One completion system for everything. Any block — not just checkboxes — can be marked done, from anywhere, and every view in Nomima agrees instantly.

How completion works

A block counts as complete when either of two things is true:

It’s a checked task — a checkbox you ticked, or
It carries a #complete status tag — a hashtag of the Status type stamped onto the block.

That’s it. There’s no hidden “done” database that can drift out of sync with what you see — completion is always visible right in the note, either as a tick or as a tag.

A checked task

✓Book the venue for @Sara Chen

Any other block

Sponsor logos signed off#complete

Any block — not just a checkbox — is “done” once it carries the #complete status tag.

Every way to mark something done

Where	How
In a task list	Tick the checkbox.
On any other block	Type #complete on the line — the line greys out and gets struck through. Delete the tag to un-complete it.
Overdue date pill	An overdue date shows a red “done?” shortcut — one click stamps #complete for you.
Smart View lenses	Every block listed under a tag’s card has a checkbox — checking it completes the block back in the source note.
Home agenda	Every overdue/today/upcoming row has a checkbox too.
Dates lens	Both dated tasks and dates mentioned in prose get checkboxes.
Alerts lens	The ✓ button completes a reminder or task without leaving the list.
Reminder	The Clear button completes it (and stamps #complete).

Two-way sync: these are all the same action. Checking a row in a Smart View edits the actual note; un-checking in the note updates every view. Progress bars, briefs and badges recompute immediately.

Completion in container blocks

Task List — shows a live 3/5 progress badge and auto-completes (turns green) when every item is checked. Adding a new item reopens it.
Section — stamp #complete on the summary line and the whole section greys out, contents included.
Callout — a completed callout swaps its icon for a green checkmark.
Kanban — a card completes by being dragged to the Done column or by carrying a #complete tag (cards have no checkbox); the whole board completes when everything reaches Done.
Gantt — rows complete individually; the chart completes when all rows are done.

Complete a whole container

Container blocks — a task list, a Section/Toggle, a Kanban board, a Gantt chart — have a title line of their own. Completing that title is a bulk action: it cascades down to every child at once. And most containers roll the other way too: finish every child and the title completes itself. These are two separate mechanisms, and it’s worth keeping them straight.

Down-cascade: header → children

Mark the container’s title done and Nomima immediately marks everything inside it. How you “mark the title” and what happens to the children depends on the block:

Container	Complete its header by…	…and every child
Task list	Ticking the list title’s checkbox, or typing #complete on the title line.	Every row is checked — top-level rows and every Tab-indented subtask, at any depth. Each row also gets its #complete pill so it reads done everywhere else.
Section / Toggle	Adding #complete to the section’s summary line.	The whole collapsible subtree greys out and strikes through — prose, bullets, and any nested containers. Nested task lists, boards, charts and sub-sections have their titles stamped too, so their own down-cascade runs and their rows/cards/tasks complete in the same pass.
Kanban board	Typing #complete on the board title.	Every card is stamped #complete and flies to the Done column (each card remembers where it came from, so un-completing sends it back).
Gantt chart	Typing #complete on the chart title.	Every task is stamped #complete and greys/strikes in place (Gantt tasks don’t move — there’s no Done lane).

Section greying is clean, not litter. When a Section is complete, its plain paragraphs and bullet lists are greyed and struck by the section itself — they don’t each sprout a visible #complete pill. Only the section’s own summary keeps a visible tag (and its un-complete toggle). Child containers inside it still stamp their own titles, because that’s what drives their rows to complete.

▾ Launch checklist #complete

Everything below ships together for the #launch.

Press kit approved

Pricing page live

▤ Pre-flight

✓Final QA pass

✓Tag the release

Marking a Section’s summary #complete greys and completes everything nested under it in one step.

Up-rollup: all children done → header

The reverse happens automatically, and it’s a different path. As you check off children one at a time, Nomima watches each container: the moment every child is complete, it stamps #complete on the container’s title for you; if any child later reopens, it strips that tag right back off. You never have to complete the header by hand — finishing the work does it.

Task list: the header shows a live N/M progress badge (top-level rows) plus a percentage bar; a subtask badge like 4/6 tallies indented rows separately. When the last row is checked the title turns green and gains its check; adding a fresh (unchecked) row flips it straight back to open.
Kanban & Gantt: once every card sits in Done (board) or every task is #complete (chart), the title auto-completes; move one card out of Done, or reopen one task, and the title re-opens.
Section / Toggle: a section rolls up from everything inside it — every child container (task list, board, chart, sub-section) and every plain-paragraph to-do (a line like “Send email to @Dom”, gated the same way a To do row is) must be complete before the summary auto-stamps. It works both ways: marking the section complete by hand also stamps those prose to-do lines done. Empty lines and plain bullet lists (no to-do of their own) don’t gate it, so a section of ordinary notes never gets stuck “incomplete.”

Rule of thumb. Down = you complete the header, children follow. Up = children complete themselves, the header follows. Down is a deliberate bulk action; up is bookkeeping Nomima does so a container’s title always tells the truth about what’s inside.

Empty containers never auto-complete. A list, board, chart or section with no completable children stays open — an empty to-do is a to-do, not a finished one. Roll-up only fires once there’s something inside to finish.

✓ Release steps #complete 5 / 5

✓Tag the release

✓Build & notarize the DMG

✓Upload to GitHub

✓Update #launch latest.json

✓Post the changelog

Check every row and the title completes itself — the N/M badge and the auto-stamped #complete both reflect the roll-up.

Dashboard blocks are the exception. A Dashboard can be marked done — #complete on its caption — but it does not cascade. Completing it won’t touch its widgets, and completing widgets won’t roll it up; it’s a single completable block, not a roll-up container.

What changes when something is done

In the note — the text greys out and gets a strikethrough; its date pills turn grey and stop counting as overdue.
Smart Scrollbar — the block’s minimap dash turns grey, so a glance at the rail shows how much of a note is finished.
Smart Views — the item moves under the collapsed “N completed” toggle; the tag’s progress bar and “open” badge update.
Home — it leaves Overdue/Today; when nothing is pending, Home shows your recently completed items instead.
Knowledge Graph — the node dims to grey.
Briefs — per-tag summaries recount open vs. done work.

Changing your mind

Completion is never destructive. Untick the checkbox or delete the #complete tag and the block returns to open everywhere — overdue dates turn red again, badges recount, and the item reappears in your agendas.