Anydocs Documents
Theme Configuration

Branding

Understand the real scope and visibility of reader branding fields.

Reader branding lives under `site.theme.branding`. It affects the site shell identity, not the page body content model.

Primary fields

The fields that matter most today are `siteTitle`, `logoSrc`, and `logoAlt`. They control whether the reader shell shows a brand title, a brand image, and accessible alternative text for that image.

Optional compatibility field

`homeLabel` is still a supported field and is persisted through Studio, but the current built-in themes do not treat it as a primary visible branding slot. It is more accurate to treat it as a compatibility field than as a core presentation surface.

If you only want to customize the site title, set `siteTitle`. If you only want a graphical brand, set `logoSrc` and `logoAlt`. If you set both, the reader can show the image and title together.

Boundary with page content

Branding fields are project-level reader shell configuration. They become part of the published site shell and related machine-readable metadata, but they are not page-body blocks and should not be repeated inside every page.

Branding cannot be an empty shell: Once you declare `site.theme.branding`, you must provide at least one of `siteTitle` or `logoSrc`; otherwise project validation fails.
Always fill logoAlt: If you use `logoSrc`, add `logoAlt` as well so the reader shell keeps usable accessibility text.