Anydocs Documents
Theme Configuration

blueprint-review Theme

Understand the blueprint-review theme, its review-focused layout, and its configuration boundaries.

`blueprint-review` is the built-in review-oriented reader theme. It is designed for PRDs, technical specs, review notes, and internal knowledge bases. Instead of acting like a portal shell, it prioritizes long-form reading, metadata scanning, and review context.

Layout and best fit

This theme still uses a sidebar-plus-article structure, but the article area is wider and long pages get a dedicated TOC rail. It fits internal docs with deeper trees, longer pages, and frequent movement between sections.

Review-oriented reading behavior

When the theme is active, the reader upgrades the page header based on metadata and review signals. If a page includes fields such as `doc-type`, `review-state`, `owner`, `reviewer`, `due-date`, `decision-summary`, or `open-questions`, the theme can surface them as context, review, and decision panels instead of only showing a plain title and body.

What you can configure today

At runtime it supports reader branding fields such as `siteTitle`, `logoSrc`, and `logoAlt`, plus `site.theme.chrome.showSearch` and `site.theme.codeTheme`. For color overrides, the main entry point this theme actually consumes today is `site.theme.colors.primary`. Other shared color fields can still live in the project contract, but they do not drive a fully themed multi-slot palette the way `classic-docs` does.

What Studio currently exposes

Studio does not yet have a dedicated Blueprint Review settings card. You can switch `Docs Theme` and `Code Theme` directly, but if you want to fine-tune fields such as logo settings or the search toggle, you still need to write them through project config or MCP / API flows.

Capabilities it does not use

`blueprint-review` does not use `site.navigation.topNav`, and it does not currently support dark mode. Its focus is the left-hand docs tree, a wider reading surface, and review-aware metadata panels rather than switching between major areas in a top header.

When to choose blueprint-review: If your site mainly serves PRDs, review packages, or internal knowledge reading and pages often depend on metadata, decision summaries, and open questions for context, this theme is usually a better fit than classic-docs.
The review enhancements depend on structured fields: A page with only body content still renders correctly, but without review signals such as `doc-type` or `review-state`, the theme falls back to a more overview-like presentation instead of generating full review panels automatically.