goatboat notes
The content database and CMS behind my personal website, with built in API and MCP server
Roadmap
- MVP slices
The order of work: one usable feature at a time.
Ideas
- Dev sync: new pages appear while I work
- Ideas, problems and thoughts
How ideas, problems and thoughts are filed as ordinary pages under three parent pages, optionally labelled with a project, and shown on each project's homepage.
Decisions
- Page identity: an ID on the first line
Why code pages carry a goatboat ID on their first line, and the alternatives weighed for following pages across folder moves.
- Proposing complete, published pages
Agents can now propose a new page with its description, tags, project and section, published on approval. What changed, and the security questions that come with it.
- Routes as data
Proposal: give every page, including TSX ones, a row in the content database.
- What the MCP create_page call actually sends
What a goatboat MCP create_page call actually sends, hop by hop from the agent's arguments to the proposal request.
Tests
- Content feed
Every published item from the database, newest first, filterable by type.
- Content tree
Every node nested under its parent. Paths, and so URLs, come from this tree.
- Link render
- MCP read report: pages without a description
An agent's report from one filtered list_pages call: which /docs pages lack a description, and what that proves.
- Projects
Every project and experiment, any status, with kind and status shown.
- Tags
Every tag with its count. Each links to the feed filtered by that tag.
- Write API test run
Every write route exercised on a scratch post: each request and the response it got, recorded.