WitWiki

Editing pages: blocks, tables, code and diagrams

Open a page and press Edit. The page becomes an editor that works in blocks: click into a paragraph and change it, or start a new block with the slash menu. Blocks is the default view; Source shows the markdown underneath. The bar above the page has the two as tabs, says whether you have Unsaved changes, and keeps Cancel and Save in reach however far down the page you are. ⌘S to save (Ctrl S on Windows and Linux) works too.

Everything you write is stored as markdown, which is what your agents read and write over MCP. The editor is a way of writing that markdown without looking at it.

Blocks and the slash menu

An empty block reads Write, or type / for a block. Type / and pick:

BlockWhat it is
TextA paragraph
Heading 1 – Heading 6Section headings — ## and ### are the ones a wiki page usually needs
Bullet List, Ordered ListLists; press Tab to nest
Task ListCheckboxes
QuoteA pulled-out passage
DividerA horizontal rule
CodeA fenced code block with a language
TableA table you can add rows and columns to
DiagramA Mermaid code block with a rendered preview under it

Drag a block by its handle to move it. Select text for the inline toolbar — bold, italic, code, a link. Paste markdown and it arrives as blocks, not as a wall of text.

Type [[ and a picker opens over the pages in this project; keep typing to filter by path, press Enter to insert [[path]]. Write [[path|display text]] by hand when the prose should read differently from the path. These are wikilinks — the same links your agents write — and they are what builds the link graph and what wiki_lint checks. A link inside a code block or inline code is text, not a link.

Code and diagrams

A Code block takes a language; the read view highlights it and shows the language in the corner. A Diagram block is a code block in the Mermaid language: write the diagram source and a rendered preview appears under it (Hide diagram folds it away; Edit brings the source back). Flowcharts, sequence diagrams, pies, git graphs and state diagrams all work, and the read view renders them in colour.

Tables

A Table block is a real table. In the read view a table wider than the column scrolls sideways rather than squeezing the page.

What is deliberately off

Images and math (LaTeX) are switched off in the editor. A wiki page is text that people and agents both write; a file you need to keep belongs in Sources, which your agents can read. This may change.

Source

Source shows the page's markdown and lets you edit it directly. Switch back to Blocks at any time.

Some pages open in Source on their own, with a note naming the line: it means the block editor would change that line's spelling — a table alignment marker, an unusual list marker, an HTML block — and WitWiki would rather show you the markdown than silently rewrite it. Change that line and Blocks becomes available.

Saving

Press ⌘S or Save; if a save fails, the bar says Not saved and keeps what you wrote. A successful save also clears any kept edit of that page. A save only rewrites the blocks you changed, so a one-word edit is a one-line diff in History, and an agent reading the page afterwards sees exactly what moved. Every save carries the version you opened with; if the page changed while you were editing — usually an agent — the editor shows the change and asks what to do. See History and conflicts.

Cancel, leaving, and not losing your edit

Cancel with nothing changed simply returns to the page. Cancel with changes returns to the page at once and shows Edit discarded with an Undo button for ten seconds. Undo reopens the editor exactly as you left it: the same title, the same text, the same view (Blocks or Source). When the message goes, the discarded edit is gone. Nothing asks "are you sure" first, and nothing is saved by itself.

If you leave an edit by following a link instead — a page in the tree, a word in the navigation, the breadcrumb or the Back button — WitWiki keeps your unsaved edit in the browser's memory for the rest of the session. When you are back on that page, a note under the byline says You have an unsaved edit with Open it and Discard. Open it (or Edit) opens the editor with your title and text; Discard drops the edit for good. If the page changed in the meantime, saving shows the same merge, discard or overwrite choice as any other stale save.

Kept edits live only in that tab. Reloading or closing it loses them, so the browser asks you to confirm before it does either while you have unsaved changes or a kept edit. Signing out clears them.

New pages

On any page, New page creates a page linked from the one you are on: give it a path like concepts/my-new-topic, and WitWiki creates it, adds a [[concepts/my-new-topic]] link to the current page, and opens the new page in edit mode. Paths are lowercase, hyphenated, use / for hierarchy, and never end in .md; the title starts as the last segment and you can change it. Agents create pages over MCP with wiki_updatePage, and change them with wiki_patchPage against the version they read.

In an organisation with task boards on, New page can make a task board instead.

Was this page useful?

The foot of every page asks Was this page useful? with a thumbs up and a thumbs down. Anyone who can read the page can vote. A thumbs down opens an optional note, What is wrong or missing?, of up to 2,000 characters. Click the same thumb again to take your vote back. Members, admins and owners can list a project's voted pages, most thumbs down first, with the notes, at GET /api/feedback. Votes do not change search or anything else.