Architecture
Neoma is a React and TypeScript application that runs entirely on your device. Here is how the pieces fit, for anyone who wants to check the claims or change the code.
The interface never touches IndexedDB or file APIs directly. Writes to folders are atomic, deletes go to a recoverable trash, and a file changed on disk is never silently overwritten.
Raw HTML in notes is dropped, never executed. The same pipeline renders the editor's reading view, published sites and these docs.
The worker owns note text. The main thread keeps only light metadata, so typing stays smooth on large vaults.
The same graph answers backlinks, broken links and orphans, and plans the link updates you review when you rename a note.
Only the chosen notes are read. Links to unpublished notes render as text, and vault paths never reach the output.
Native shells add platform storage, window controls and packaging. They do not add network access: the shipped security policy has no remote host.
Extending
Neoma's own features register through four documented registries, exactly as a future plugin would. There is no plugin runtime yet, and Neoma does not run third-party code today. The extension points are already the architecture.
Source map
A tour of the repository in one tree. Start with src/storage and
src/app/vaultStore.ts.
src/ ├── app/ shell, stores, registries ├── components/ interface ├── editor/ CodeMirror 6 setup and slash menu ├── markdown/ frontmatter, metadata, render pipeline ├── storage/ StorageAdapter and its backends ├── search/ search client and query parser ├── workers/ the index and search worker ├── links/ link graph, backlinks, renames ├── graph/ graph view, lazy loaded ├── publish/ the static site builder ├── templates/ templates and starter vaults └── themes/ design tokens and CSS