Documentation
Go Scribi keeps notes, checklists, maps and boards in one place, and makes all of them findable. These pages say what each kind is for and every key it answers to.
One idea, four shapes
A note is text. A checklist is a tree of text you can tick. A map is that same tree drawn as a picture. A board is that same tree in columns. They are deliberately alike: the keys you learn on one work on the next, and every one of them exports as plain text. You can make a new checklist, map or board from another of those three: the original stays exactly as it is, and the confirmation says what the new one will leave behind before you make it.
Everything you write is Markdown — a note's body, a checklist item's note, a card's description, a map node's note. Every one of those areas gets every Markdown feature, including tables and diagrams.
- Notes Text in Markdown, with its own history and a way to add to it in one line.
- Checklists A tree of things to tick off, typed without the mouse.
- Maps The same tree, drawn — and drawn by the server, so it prints and exports.
- Boards Columns and cards, with a log of what moved where and when.
- Notes and folders The tree down the left: folders, sharing, and moving things about.
- Markdown Everything the text understands, with every example rendered by the real thing.
- Diagrams Flowcharts, sequences and the rest — drawn from text, in any note.
- Comments Say something about a sentence, without writing it into the note.
- Mentions and your inbox Write somebody's name, and where it reaches them.
- Saved views A search you keep, as a folder that is a question.
- Keeping things for later Save it now, decide where it belongs later.
- Webhooks Tell another system when something happens here, instead of it asking.
- Repeating tasks and reminders A card or a row that comes back — monthly, or a few days after you finish.
- Backups and restoring Taking a copy — and finding out whether the copy would bring it back.
- Note properties A review date, a status, where it came from — as fields, not as words in a title.
- Writing that has not been saved Every box keeps what you type until the server has it — on this device, and never called saved.
Writing a program against your notes, or connecting Claude to them? The API — keys, errors, and everything a program can do.
Things that are true everywhere
- Esc lets go
- From editing it saves and stops; from a list, a map or a board it hands focus back. It never throws away what you just typed.
- Every note keeps its history
- All four kinds. You can read an older version, compare two, and put one back.
- Nothing is deleted for being over a limit
- A workspace past its note limit becomes read-only. Everything is still there, exporting still works, and deleting always works — which is the way out.
- Your work is yours
- Any note, any folder, or the whole workspace exports as a zip: Markdown with the files beside it, an HTML page that opens offline, or plain text for another program.