Quiet luxury on the wire — MDX without Contentlayer

## Why filesystem first Contentlayer is excellent until it is not — upgrades, codegen drift, and opaque caches can steal time from the work clients pay for. A thin layer of Node `fs`, `gray-matter`, and `next-mdx-remote` keeps ownership in the repo and the mental model small. ## What we validate Frontmatter becomes a contract: title, SEO fields, taxonomy, and reading time all pass through a schema before they touch the UI. That means the blog index never renders half-empty cards because a field went missing in one post. ## How RSC fits Rendering MDX on the server matches how we treat marketing sites generally — send HTML, keep client islands for interaction only. The article shell, TOC, and typography stay on the server; motion and sharing stay surgical. ## Closing note If your editorial team wants previews, webhooks, and roles later, this structure maps cleanly to a headless CMS without rewriting components — the MDX body remains the portable center.