Documentation topic
MDX & Content Systems
Core guides
Start with the architecture
These guides carry the main argument for this topic. The full library below goes deeper into individual implementation decisions.
The connectrader MDX content standard
How we structure long-form website content so writers can work in readable documents while the application still gets reliable metadata, routing, images, schema, and build-time validation.
Read the guideFrontmatter is an interface contract, not decoration
Why our MDX frontmatter acts like a small API between editorial content and application code, and why that makes large content libraries safer to extend.
Read the guideHow an MDX file becomes a production page
A step-by-step look at the path from a plain MDX file in the repository to a static route with metadata, schema, navigation, sitemap coverage, and a deployable production artifact.
Read the guide11 guides
All MDX & Content Systems documentation
How we structure long-form website content so writers can work in readable documents while the application still gets reliable metadata, routing, images, schema, and build-time validation.
Frontmatter is the structured header at the top of an MDX file. It gives the application information that should not be inferred from the body.
The quality of MDX content depends on more than valid syntax. The document should also read well, scan well, and render consistently.
Images are one of the easiest ways to make a fast site slow. Our MDX standard treats media as a deliberate part of the page, not decoration added at the end.
Internal links help readers move through a site and help search engines understand how pages relate to each other.
Content should have a lifecycle from creation through maintenance. Publishing a file is only the first step.
Why our MDX frontmatter acts like a small API between editorial content and application code, and why that makes large content libraries safer to extend.
How image registries and resolver functions let content stay readable while the application keeps control over imports, fallbacks, responsive image behavior, and broken references.
How we structure location content so a shared route can scale while each page still has enough local substance, imagery, services, FAQs, and context to deserve its own URL.
A step-by-step look at the path from a plain MDX file in the repository to a static route with metadata, schema, navigation, sitemap coverage, and a deployable production artifact.
When MDX is a better fit than a database-backed CMS for marketing content, and when an editorial team should choose the CMS instead.
From explanation to proof
Where this connects to the work
These guides show how our publishing architecture supports large indexed libraries without requiring a database-backed page builder.