Defaults over configuration

A fresh CTXR site works before it is configured. The engine serves defaults — the AI index, the sitemap, the app manifest, the install guide, the explainer at /admin, a generic page layout — and a site overrides only what it wants different.

The choice

Configuration is where systems go to rot. A settings file that copies the defaults falls silently behind when they improve; a required setting can be done wrong; an option “just in case” is a code path to test forever. An earlier engine we built found a fleet of sites whose identical configuration files had drifted from the platform.

CTXR’s rule: a configuration file exists only as a deliberate deviation. The site’s config holds site knowledge — owner, languages — and nothing about the engine. Everything else has an override rung:

Rung What serves
Do nothing the engine’s version
Put a file of the right name in the theme yours
Name a route explicitly that, over both

What it buys

A site that renders on day one. One organisation entity, a home page and a floor template make a working site with a sitemap, an AI index and an install page. See How a page finds its shell.

Updates that carry improvements. When a default improves, every site that did not override it gets the improvement with the next engine update.

Nothing to get wrong. There is no setting for the caching strategy, the slug format or the machine views; the engine gives the one right answer.

Honest overrides. An override is a theme file with a known name, so a listing of the theme shows where this site differs.

What it costs

Opinion. CTXR decides where icons live, what the offline page is called, how assets are versioned. Yours are the templates, the sections and the data.

The same shape elsewhere

An absent plan file means no limits. An empty keys folder means the site is closed. A language missing from a slug map means the page does not exist there. Absence is always safe; presence is always a choice someone made.