Is There a CMS or Static Site Generator Built Around Modular, Predictable Templates?

Most established CMSs can support something similar through custom templates, plugins, or content types. Drupal and Joomla have structured content features, while many static generators offer reusable layouts and components. The important distinction is that content modeling and page rendering are separate concerns: the CMS stores relationships and data, and the template system determines how those pieces are assembled.

Headless CMS platforms are a good fit if you want predictable content models. You can define types such as Document, Site, Section, and Post, then create relationships between them. A singleton could hold site-wide information, while other entries represent sections and posts. The front end can then render those models using whatever component hierarchy you prefer.

You may want to look at systems such as Strapi or Directus, paired with a component-oriented front end or a static-site tool that supports content collections. The CMS handles structured data, while the front end controls the exact nesting and layout. That separation often provides more consistency than trying to force a traditional theme system to represent every level.

What you’re describing is primarily a component and template architecture rather than a formal CMS standard. You can build it in WordPress or in a static-site generator by organizing the interface into self-contained partials or components. The main limitation is usually the theme or implementation you choose, not the CMS itself.

WordPress can produce this structure if you create a custom theme. The main template can include the document-level elements, while reusable template parts handle site headers, section layouts, post headers, and footers. It may require more custom work than the default setup, but WordPress does not restrict you to its standard markup or template arrangement.