Bilingual MDX pipeline

This is the most important internal infrastructure project in the site so far, because it determines whether future content additions remain easy or become a structural burden.

What it needed to solve

The real questions were practical:

• will the fifth article still be easy to add
• can Chinese and English be maintained without fighting each other
• where do images, diagrams, and attachments live
• do list pages and detail pages need to be redesigned each time

The adopted model

The content layout is now explicit:

content/blog/<locale>/<slug>/index.mdx
content/projects/<locale>/<slug>/index.mdx

Page templates read resolved entries from a content registry, and list pages only render sorted metadata.

Why this is a good fit for a personal site

A personal site usually does not need a full CMS from day one. But it also should not keep pretending that scattered flat files are enough forever.

Folder-based MDX is a useful middle ground:

• lightweight enough to stay simple
• explicit enough to stay maintainable
• flexible enough for assets and supporting materials
• easy to evolve incrementally

Current state

The pipeline is already in place and powering the current public site. The next valuable step is not another rewrite. It is continued use.