Configuration

The generator changes product configuration, not application architecture. This keeps template output understandable after the first feature ships.

content/site.yaml exposes a small set of booleans under options:

• displayDocs creates the public documentation routes and adds the Docs link.
• displayLlms exposes llms.txt and llms-full.txt only when documentation is enabled.

Do not add a generic bag of flags. Each option must have a named product purpose, a safe default, and a direct implementation path.

Landing copy, legal identity, docs navigation, and SEO descriptions are all YAML data. Full documentation lives in content/docs/*.md, so authors can edit prose without touching React components.

Authentication, database schema, route handlers, migrations, and release controls remain TypeScript or SQL. Keeping operational logic out of content files avoids hidden behavior and makes code review meaningful.