theProject.
ServicesBlogContact
Get Started
Documentation

Architecture

Content Architecture Split

How project-redefine, Studio by theProject., local MDX, and editorial content fit together.

Rendering documentation...
Contents
Current route ownershipFuture blog contentWhy public chrome stays here
Back to Docs
theProject.

Building exceptional digital experiences for everyone.

610-639-1290·contact@bytheproject.com

Mon–Fri, 8:00 AM–6:30 PM ET · Sat–Sun, 9:00 AM–5:00 PM ET

Hellertown, PA 18055

GitHubinLinkedInX (Twitter)

Services

  • Web Development
  • UI/UX Design
  • Application Development

Company

  • Focuses
  • Documentation
  • Field Notes
  • Blog
  • Contact

© 2026 theProject. All rights reserved.

Privacy·Copyright

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.

Current route ownership

  • /developer/documentation is local MDX documentation.
  • /developer/field-notes is local MDX technical writing.
  • /blog is the public home for Studio-powered editorial and local SEO content.

Future blog content

The public blog reads published content from Studio by theProject. through a stable server-side API layer. Publish events trigger revalidation for affected routes.

MCP can help development and agent workflows, but it is not the production content delivery mechanism.

Why public chrome stays here

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.