Compiled Notebook

This site works best when it behaves like a notebook that gets compiled, not like an app that keeps asking for more machinery.

I want publishing to stay close to writing:

• open a Markdown file
• think clearly
• revise
• publish

That constraint is useful. It blocks a lot of accidental complexity before it starts.

Static content ages well. It is easier to inspect, easier to move, and easier to maintain after long gaps between edits. That matters more to me than adding dashboards, workflows, or integrations that make the system look sophisticated while making the writing process worse.

The practical test is simple: if JavaScript disappeared, the reading experience should still hold up. The pages should load, the words should be there, and the structure should make sense without hidden dependencies.

That is the direction I want the blog to keep.