Blog handbook

This handbook explains how to write for this blog, develop its application, and keep it maintainable. The Markdown files in docs/ are also the source of the documentation published at /docs.

For blog authors

Start with your first post, then use the references for Markdown and math, images, diagrams, and embeds, and citations. The publishing checklist covers previewing, updates, and moving an existing article.

Authors importing old material should also read content migrations. The ML Revisited series has additional editorial principles.

For developers

Follow local development to install the pinned toolchain and start the watcher. Read architecture before changing generation or browser lifecycles. Use configuration, testing, and deployment for the corresponding workflows.

Maintaining documentation explains which pages to update with a code change, how the documentation site works, and how to add a page. Dependency policy records upgrade constraints; browser troubleshooting covers host-specific setup problems.

Where things live

Reading maintenance records

The ordered maintenance tasks explain the completed six-dimension review and its validation. The original audit is a historical snapshot: its findings describe the code before those fixes. Use the current developer guides for present behavior and the records to understand decisions, measurements, and known tradeoffs.

Documentation and changes

Update the relevant guide in the same change as code, configuration, or authoring behavior. Local development regenerates documentation when saved; production publishes it with the next site deployment. There is no separate copy of the prose and no separate documentation deployment.