Runtime Configuration

What belongs in runtime config and how feature toggles are wired.

What belongs here

src/config/runtime.js is the place for serializable runtime decisions such as:

Keep it data-only so it stays safe to read in routing, metadata, and server code.

Prefer booleans, strings, numbers, arrays, and plain objects.
Keep secrets in environment variables, not in committed config.
Add only the smallest setting needed for the feature you are enabling.
If behavior lives in a component or route, keep the behavior there and only reference config from it.

Do not turn config into application logic

src/config/runtime.js should not become a registry of React nodes, route handlers, or compatibility wrappers. Keep it declarative.

If you are changing homepage copy or section structure, update src/config/landing-page.js, src/config/foundation.js, or src/docs/content/*.

If you are changing navigation, update src/config/navigation.js or src/config/docs-nav.js.

If you are changing how something renders, edit the relevant shared component instead of pushing UI concerns into runtime config.