/Docs
Search docs or ask a question⌘K
DocsAgent
Changelog

Presets

The eight doc engine v2 presets — what each one looks like, how to try one, and how existing sites stay unchanged.

6 min read

Doc engine v2 renders your site from one of eight presets. A preset is a complete starting look — fonts, accent, shell, header, navigation, table of contents and the style of every component. Pick one with theme, then change any single choice with appearance.

v2 is opt-in. Nothing changes on your site until you choose a preset.

Try a preset

Set theme to a preset name in syntext.json and build:

json
{
"theme": "workbench"
}

The build log confirms it: Appearance: workbench preset (doc engine v2). Preview it before it goes live with a preview deploy or stx deploy --preview.

To switch presets, change the name — "theme": "paper", "theme": "console" and so on. Your appearance settings carry over, because they apply on top of whichever preset you pick.

To go back to v1, set theme back to your previous value (or remove it) and remove the appearance block.

The presets

PresetthemeFontsAccentModeSizeRadius
WorkbenchworkbenchGeist, Geist Mono#E4512Blight15medium
PaperpaperFigtree, IBM Plex Mono#0E7A63light16large
ConsoleconsoleIBM Plex Sans, JetBrains Mono#3DDC97dark15small
AtlasatlasPublic Sans, Roboto Mono#2457D6light16small
PlainplainHanken Grotesk, Fira Code#6D28D9light16small
OrbitorbitManrope, DM Mono#4F46E5light16large
GridgridInter Tight, IBM Plex Mono#E11D48light16none
MarginmarginInstrument Sans, Red Hat Mono#0E7490light17medium

Each preset is a set of switch values:

Presetshellheadernavtoccalloutstepscodecardstabsapi
Workbenchborderedcommandtreeprogresslabelcolraildarkborderedunderlinespec
Papersheetpillpillspillstagcardslighttilepillcard
Consoleborderedtabsmonodotsstrippromptinsetoutlinemonoterm
Atlasenterprisemegachevronsruleboxprocedurenavyaccentboxedboxed
Plainminimalsimpleplainplainsoftlistplainplaintextplain
Orbitfloatingislandsectionsfloatfloatstackfloatbentosegmentsplit
Gridgridindexchaptersrulercellcellscellcellcellsgrid
Marginfocuspathoverlaytickssidenotemarginbleedrowstextstacked

Every preset starts with foldable sidebar groups (layout.groups: "collapsible"), and draws its home components in the home style of its own header (the header column above): <SectionCards /> looks like Workbench's section grid on Workbench and like Paper's pill cards on Paper.

Workbench

The default v2 preset. A bordered shell with a command-style header, a tree sidebar and a reading-progress table of contents. Callouts carry their label in a side column, steps run down a rail, and code sits in dark blocks. API pages use the spec layout.

Paper

A soft, rounded sheet on a canvas tinted with the accent. Pill-shaped header, sidebar and table of contents, tag callouts, steps as cards, light code blocks and tiled cards.

Console

The only preset that starts in dark mode. A terminal feel: header tabs, a monospace sidebar, dot markers in the table of contents, prompt-style steps, inset code and term-style API pages.

Atlas

Built for large, enterprise documentation. A mega header with a company bar (filled from topbarLinks and status), a chevron tree sidebar, boxed callouts, procedure-style steps and navy code blocks.

Plain

The quietest preset. A minimal shell with a simple header and plain navigation, soft callouts, steps as a list and unstyled code, cards and API pages.

Orbit

Floating panels: an island header, one floating navigation column, a floating table of contents and floating code. The navigation column lists every section of your site with its icon; the section you're in opens in place to show its groups and pages, each page with its own icon. On phones and tablets the menu shows the same column. Cards are a bento grid, tabs are segmented controls, and API pages use the split layout. The page scrolls behind the island header, which floats over the content (headerBackground transparent); every other preset keeps a solid band behind its header.

The earlier Orbit sidebar — an icon rail beside a separate section list — is still available: set appearance.layout.nav to dock.

Grid

Square corners and visible structure. An index header, the sidebar as chapters, a ruler table of contents, and callouts, steps, code, cards and tabs drawn as cells of one grid.

Margin

A focused reading layout at 17px. A path header, navigation in an overlay you open from the menu, tick marks for the table of contents, callouts and steps set in the margin, and full-bleed code (code inside endpoint columns, lists, steps, tabs, callouts, accordions, expandables and cards stays inside its box).

Change one thing

Keep a preset and override single choices with appearance:

json
{
"theme": "atlas",
"appearance": {
"accent": "#0F766E",
"layout": { "nav": "tree" },
"components": { "code": "dark" }
}
}

Each switch changes only its own region: layout.header swaps the header bar and leaves the preset's home, search, menus, chat and buttons alone. The layout.home switch, which changed the home separately, is deprecated and ignored with a warning since 16 November 2026.

Every allowed value is listed in the appearance reference. A misspelt value is reported in the build log with a suggestion, and never fails the build.

Every appearance field changes v2 pages — accent (one colour, or one per mode), mode, fonts (any Google Fonts family), text size, corners, density, page width, the light/dark toggle and illustrations. Your themeOverrides apply on top. See Theming.

You don't have to edit JSON: Settings › Appearance in the dashboard has a preset gallery and theme editor with a live preview, and opens a pull request with the change. To reuse one look across projects, save it as an organization theme and set "theme": "@your-org/brand".

Existing sites are unaffected

A site renders with v2 only when it opts in — a v2 preset in theme, an organization theme in theme, or an appearance block. Every other site keeps the v1 renderer, and its output is exactly what it was before v2 existed. "theme": "default" and "theme": "gravv" are v1 themes and don't opt in.

Your other syntext.json settings work on v2 without changes:

KeyWhere it shows on v2
logoThe brand in the header (the light logo)
tabsThe header's section tabs — or, without tabs, the sections found in your pages
topbarCtaThe header's call-to-action button, when it has both label and url
topbarLinks, statusThe company bar above the mega header (Atlas)
githubThe header's GitHub link
footerFooter columns and links, with a copyright line. When the footer has columns, it also shows GitHub (github), X and LinkedIn icons from socialLinks
bannerThe announcement bar

The assistant's title and starter questions come from your AI assistant settings (aiPersona.name and aiPersona.suggestedQuestions), as on v1.

Note

On a v2 site, API reference pages generated from your OpenAPI spec are built with the rest of the site, in the v2 endpoint layout: the method and path bar under the title, parameters on the left, request and response examples on the right, then the response and an errors table.

•
Custom CSS — style a v2 site beyond the preset with --stx-* variables and data-stx hooks
Was this page helpful? Yes No
Product
Resources
Company
© 2026 SyntextBuilt with Syntext