Why MDX Works for a Static Site
How Markdown plus JSX gives you flexible content without a CMS.
MDX lets our content team publish rich stories without touching the app shell. Writers stay in Markdown, engineers keep the build static, and the site still gets the polish customers expect. With the blog now sharing infrastructure with newsletters, we can preview instantly, reuse components, and ship with the same static-export pipeline that GoDaddy hosting already understands.
What it is
MDX extends Markdown with embedded JSX, so we can mix plain prose with React components inside a single file. Every .mdx entry is compiled at build time into HTML plus the interactive elements we need, which keeps the authoring experience simple while unlocking layout components, data visualisations, and callouts on demand.
Why it matters
Because the site ships as a static export, content needs to be portable, cached, and easy to diff in Git. MDX gives us editorial flexibility without introducing a headless CMS, which keeps the deployment workflow lightweight and preserves full code review for every change.
Use case
This post lives in content/blog, the same place the newsletters loader already watches. Editors can drop in charts, CTA banners, or product snippets with one import, and the /blog route renders everything through PostLayout, so typography, metadata, and navigation stay consistent across knowledge sections.