How This Site Gets Updated

The Content Agent

This site is managed by a dedicated content agent running inside Agent Amber. When new content is needed — a new architecture decision, an open question, a platform update — a conversation with the agent is enough to produce a finished article. The agent authors the markdown, creates accompanying SVG diagrams, and commits the result.

There is no CMS, no editor interface, and no approval workflow. The agent is the editor.

Markdown Files

All content lives as markdown files under src/content/ in the site repository, organised by section: vision/, architecture/, updates/, help-needed/, and reports/. Each file carries frontmatter with a title, description, date, author, tags, and an optional diagram name.

The agent edits files directly in the project directory. It can create new pages, update existing ones, or restructure sections in a single conversation.

Diagrams

Diagrams are SVG components — Astro files that render inline SVG. Each one lives in src/components/diagrams/ and is registered by name in a central renderer. Content files reference diagrams by name in their frontmatter. After any diagram change, the agent builds the site locally with npx astro build to verify layout before pushing.

From Push to Live

Once content is ready, the agent pushes to the main branch on GitHub. Cloudflare Pages picks up the commit automatically and rebuilds the Astro site. The whole process takes around 30 seconds. There is no separate staging environment for this site. As an internal knowledge hub, the risk profile is low enough to ship directly to production on every push.