Building a Content Architecture with MDX

MDX is useful when content and components need to coexist. For a personal site, it often gives the right balance between flexibility and control.

Keep collections explicit

Separate long-form articles from lighter notes. They can share infrastructure while keeping different listing strategies and different page density.

Treat content as data

The route layer should not know how to parse files directly. It should ask a content module for structured entries.

Generate supporting systems from source

A table of contents, reading time, tag pages, and metadata should all be derived from the MDX source instead of duplicated.