docs
- Building and Deploying
Build with Node in under a second, test with node --test, and deploy to Cloudflare Workers, with or without the login.
- Design Decisions
The choices behind the site and why: plain Markdown as the source of truth, no framework, static pages, word search only, and failing closed.
- How Search Works
Word search in the browser, ranked so a match in the title beats a match in the body, with | for alternatives.
- Links and Backlinks
Notes link with standard Markdown links, relative to the file. The site turns them into page addresses and lists backlinks under each note.
- Privacy and Hosting
The private version publishes only files Git tracks, sits behind Cloudflare Access, and turns everyone away if Access is ever misconfigured.
- Readwise and Other Highlights
Two folders I don't write by hand: readwise/, synced from Readwise, and highlights/, saved by a separate reading app.
- Recipe Format
Recipes live in recipes/<course>/ with time, servings, and effort in the front matter, and get their own filterable section.
- The Design
Engineering Pad: green computation paper with a title block on every note and numbered sections, drawn as a blueprint in dark mode. This note shows everything a note can contain.
- The Notes CLI
The command-line tool I use alongside the site, for search by meaning, links, and convention checks. It isn't part of this repository.
- Using Tags
Each tag gets a page listing its notes. Pattern tags, like idea/atomic-parts, mark ideas that turn up across unrelated topics.
- Welcome
What this site is: a read-only web version of my plain-Markdown notebook, shown here with sample notes that double as its docs.
- Writing a Note
A note is one Markdown file with a short front matter block: title, summary, tags, and dates. The file name is its id.