Article
Readable Source Files Age Better
Why document source should stay legible to people before it becomes convenient for tooling.
Readable source is not nostalgia. It is a practical constraint that keeps documents inspectable, transferable, and resilient.
A file should explain itself
When the source becomes opaque, every future change depends on a toolchain and a layer of guesswork. A readable file gives you a fallback path when the UI is gone, the product has changed, or you need to inspect a problem directly.
Structure is still useful
The answer is not plain text with no discipline. Structure matters because it enables indexing, export, and reuse. The trick is to make the structure legible enough that it still reads as part of the document.
Tooling should follow the file
If a document format is good, you should be able to open it in a normal editor and still understand where the important facts live. The application should enrich that file, not monopolize it.
Why this matters for Semnote
Semnote is being scaffolded around that constraint first. The public site, the docs pages, and the search index are all fed from content files directly so the product starts from the file instead of an opaque database abstraction.