CMS structure and Git structure have to agree

One of the easiest things to underestimate in a Git-based CMS project is that the content model actually spans multiple layers at once.

There are the source files themselves: Markdown, YAML frontmatter, and singleton JSON files. There is the CMS configuration, which decides which fields editors see and where they get saved. And then there is the front-end reader, which determines how those fields become pages.

If you change only one layer, the site may still appear to work for a moment, but the inconsistency shows up quickly. Git may already be storing bilingual fields while the CMS is still saving the old shape. Or the CMS may already be split into paired collections while the front-end still reads everything as if it were monolingual.

That is why every directory, field, and hierarchy change in this rebuild had to be checked against the source files, the YAML config, the reading logic, and the route behavior at the same time. A stable content system is not one where a single layer works once. It is one where all layers still match on the second edit.