Why this site is markdown-first
The site uses markdown because the medium matches the work: fast, versionable, structured, portable, and agent-editable.
This site is markdown-first because the medium should match the work.
The work is writing, structuring, revising, and publishing small pieces of context around AI-native creative systems. It does not need a heavy CMS at this stage. It needs a clean place where notes can be written, inspected, changed, versioned, and shipped without much ceremony.
Markdown is not a nostalgia choice. It is a useful constraint.
Fast and inspectable
A markdown note is easy to open. The title, description, date, status, and tags are visible at the top. The body is plain text. There is no hidden database field, editor state, or plugin layer between the material and the site.
That matters when the site is meant to behave like a working surface. If a note is weak, it should be easy to edit. If a title is wrong, it should be obvious. If a draft should not publish, the status field should make that explicit.
The structure is simple enough to keep in view.
Versionable by default
Markdown works well with Git. Changes are visible as diffs. A note can be reviewed line by line. The content layer can move with the codebase instead of sitting in a separate system.
That is useful for AI-assisted work. Agents can read the same files the site builds from. They can propose edits, update metadata, and keep content close to the actual implementation. The source of truth remains the file, not a generated copy in another tool.
This also makes the site portable. If the build system changes later, the notes can move. The content is not trapped inside a CMS schema or a hosted editor.
Structured, but not heavy
The site still needs structure. A loose folder of text files is not enough.
Astro content collections provide the useful minimum: frontmatter validation, typed entries, static routes, and a clear publishing rule. A note can be draft or published. The index can display only published entries. The build can fail if the content shape is wrong.
That is the right level of machinery for now.
Agent-editable publishing
Markdown also makes the site easy to work on with AI agents.
An agent can inspect the repository, read existing notes, add a new file, update frontmatter, and run the build. The workflow stays close to how software projects already operate. There is no need to click through a dashboard or reconcile CMS state after the fact.
The point is not to avoid tools. The point is to keep the publishing layer small enough that the work remains legible.
For this site, markdown is the right default: fast, structured, versionable, portable, and easy to edit with both humans and agents in the loop.