Documentation
Architecture
Content Architecture Split
How project-redefine, Studio Vanilla, local MDX, and future Payload editorial content fit together.
Rendering documentation...
Architecture
How project-redefine, Studio Vanilla, local MDX, and future Payload editorial content fit together.
project-redefine owns the public site experience: routes, header, footer, metadata, SEO, layout, MDX developer content, and visual design.
nidhogg-protocol owns the future Studio Vanilla publishing workflow: editorial posts, media, authors, categories, and review/publish operations.
/developer/documentation is local MDX documentation./developer/field-notes is local MDX technical writing./blog is reserved for future Payload-powered editorial and local SEO content.The public blog should eventually read published content from Studio/Payload through a stable server-side API layer. Publish events should trigger revalidation for affected routes.
MCP can help development and agent workflows, but it is not the production content delivery mechanism.
The public website chrome belongs with the rendering layer so bytheproject.com keeps one consistent user experience across marketing pages, developer docs, future editorial content, metadata, analytics, navigation, and layout.