Project Settings
Map Studio settings to the project contract and site-wide behavior.
Project Settings manages the site-wide contract. It controls project identity, languages, reader theme, top navigation, output location, and API Sources rather than per-page body content.
General: project identity and languages
`Project Name` is the project identity field used by Studio, init output, and default reader branding fallback. `Default Language` determines the reader root language, and `Enabled Languages` determines which languages must be maintained together with matching `pages/<lang>/` and `navigation/<lang>.json` files.
Reader: theme, branding, and search
`Docs Theme` selects `classic-docs`, `atlas-docs`, or `blueprint-review`. Among them, `blueprint-review` is aimed more at PRD and technical review reading flows. `Site Title`, `Logo Src`, `Logo Alt`, `Show Search`, and `Code Theme` all belong to reader shell configuration. `Home Label` is still persisted, but the current built-in themes do not treat it as a primary visible branding slot.
Theme-specific capabilities
Only themes with top-navigation support show a `Top Navigation` section in Studio. Among the current built-in themes, `atlas-docs` supports `site.navigation.topNav`; `classic-docs` and `blueprint-review` do not use it. Current top-nav items support `nav-group` and `external`, and each `nav-group` must point at a top-level `section` or `folder` id in each language navigation file.
Output directory, API Sources, and the public boundary
`Output Directory` maps to `build.outputDir` and controls where static artifacts are written by default. `API Sources` are a project-level publishing feature that generates published API references and related machine-readable indexes. Theme, branding, and top navigation become part of the public site shell, while page-level metadata only enters public machine-readable outputs when its visibility is `public`.