Configuration
Choose the intended site identity, host path and public assets before building. The installation’s file configuration and selected private runtime overrides are different layers; both are separate from a reader’s browser theme preference. Saving a setting changes input for a later build, not an already deployed reader.
Choose the input
| Input | Guide |
|---|---|
| Branding and root/subpath | Site settings |
| Template and visual changes | Templates and styling |
| Bundled/public assets | Local assets |
| Process/data selectors | Environment variables |
Site settings documents defaults, exact types/limits, precedence, revision conflicts and malformed files. Templates and styling documents actual placeholders and reader script expectations. Local assets documents bundling, public-byte review and notices. Read the adjacent input contract before treating one accepted value as proof the entire site configuration is correct.
Understand the layers
| Layer | Boundary |
|---|---|
| File configuration | Installed beside builder |
| Runtime branding | Selected safe keys override base |
| Raw HTML/prefix policy | File-only, not Admin branding |
| Templates/static assets | Installed project inputs |
| Browser theme | Per-origin profile preference |
A custom content tree does not supply its own config, templates or static folder automatically. The builder’s data selectors and the editor’s users-file-based runtime location must align deliberately. A hidden folder setting changes sidebar display, not output privacy.
Base/default title fallback is not a promise that changing only site title will update every header/title label. Inspect effective values, runtime overrides and actual generated output. Keep root/subpath address and prefix paired, then review authored links because Markdown URLs are not automatically rewritten.
Change and verify
Preserve current settings and identify the checkout, selected data and expendable output first. Save valid values, start a fresh build process and inspect home/deep metadata, labels, hero choice and intended URLs. Watch does not monitor every configuration/runtime path and loads file configuration at process start.
Check fonts, CSS, scripts, search, images and downloads through HTTP at the intended path. Test both themes and narrow tables/header links. Review every copied static byte for the reader audience; a file ignored by Git is not automatically excluded from publication.
Publish or deploy only the reviewed output, then verify the actual host separately. Custom HTML/template decisions require security review. The unchanged-engine public showcase uses content-level layout corrections; this guide does not authorize changing its pinned implementation.