A writing tool first, with the rest built on the same files.
Everything here is written, tested, and running today.
- A block editor over Markdown
- Slash commands, callouts, collapsible sections, tables, checklists, colour and highlighting. Everything round-trips through Markdown rather than HTML, so a save is a clean diff.
- Wiki links and backlinks
-
Write
[[Target]]with a page picker, and every page shows what points at it. Links follow a permanent id, so renaming a page never breaks one. - Search and a command palette
- Full-text search across the workspace, offline, over an index that is only a cache: delete it and it is rebuilt.
- Tasks and Kanban boards
- Boards, list views, filters, and tasks that link to pages. A board can be embedded in a page, where it stays a real board.
- Templates and a new-page dialog
- Mark any page as a template and it is offered as a starting point. A template is an ordinary page with one line in its frontmatter.
- A trash you can undo
-
Deleting moves a file to
.trash/. A restored page keeps the id every link points at. - Export to HTML and PDF
- One self-contained file with the images inlined, for sending a page to somebody who does not have the workspace.
- Local snapshots
- A copy of everything you have written, taken on a schedule you set and kept inside the workspace. Version history for a page is read from them, so it goes back as far as your backups do.
- A calendar, and tables
- A month drawn from whatever the other modules publish, and rows with typed columns that can be embedded in a page. Both are modules you can switch off.
- Four languages, and modules
- English, Dutch, French and German. The tasks module was added without changing the core, through the same interface any other module would use.
What choosing your own storage buys you.
- Nothing is locked to us
- There is nothing to migrate out of. Your pages are already files, already readable, and already in a place you named, so leaving is a directory you keep rather than a download you wait for.
- Changing your mind is cheap
- A workspace that outgrows a folder can be connected to an account, and one that no longer wants an account is a directory you keep. Neither rewrites a page.
- Coming from Notion
- Hand over a Markdown and CSV export and it becomes pages, tables and files of your own. Links are rewritten to point by id, and nothing is uploaded: it is a folder being read on your machine.
- One workspace, several machines
- With the bucket we host, the laptop, the phone and the browser tab open the same pages; with your own GitHub or Dropbox, every computer you connect does. What that costs in each case is spelled out under Synchronisation.
Back it up by copying the directory.
One workspace, three ways in.
The same pages, the same Markdown, the same rules about what a workspace is. What each one cannot do is on the card, not in a footnote.
macOS, Windows, Linux
The full application. A workspace is a folder you point at, and everything on the landing page is here: synchronisation to your own account, the Notion import, publishing, local snapshots.
iOS and Android
The same workspaces, the same editor, reading and writing the same files. On iOS the folder shows up in Files, so the promise that your pages are yours is something you can see rather than read. The youngest of the three: it synchronises through the bucket we host, while it is open, and search, backlinks, boards, tables, the calendar, templates, export, snapshots, the Notion import and publishing are on the desktop for now.
Any tab, offline
Load it once and it works with the network off: a service worker holds the application and the workspace lives in the browser's own storage. Clearing the site's data clears that too, so the whole workspace downloads as a folder of Markdown from Settings, Backups. No updater, no Notion import, and it synchronises with the bucket we host only, through us rather than straight to storage.
A workspace is a folder. That is the whole format.
There is no database and no proprietary container. Read it on a machine that has never heard of Noodletail by opening the files in any text editor.
The directory
my-workspace/
workspace.json name and id
pages/ one .md file per page
projects.md
website-rebuild.md
assets/
images/ images used by pages
files/ attachments
modules/ module data, as JSON
tasks/
.trash/ deleted pages, recoverable
.index/ search cache, safe to delete
.backups/ local snapshots of the text
.sync/ state, if you connect a remote
A page
---
id: 01M07YY25YGGV74PZVQ46SDJG6
title: Website Rebuild
parent: 01M07YY2545ET5Y9JVZWF0DP4S
order: 1024
icon: null
created_at: '2026-08-17T13:35:18.717Z'
updated_at: '2026-08-17T13:35:18.830Z'
---
# Website Rebuild
A paragraph with **bold**, _italic_
and `code`.
- The hierarchy is metadata
- Moving a page in the sidebar edits one field. No file moves, so no link and no image path breaks.
- Nothing is ever dropped
- Markdown the editor does not model, such as footnotes or raw HTML, is kept exactly as written and shown as read-only source.
- Formatting is normalised
- The first save rewrites bullet markers and table padding into one style. The content does not change, but the bytes may.