Your documentation should feel like an extension of your product, not a generic template. Doxbrix gives you control over colors, typography, logos, and site chro...
Your documentation should feel like an extension of your product, not a generic template. Doxbrix gives you control over colors, typography, logos, and site chro...
Your documentation should feel like an extension of your product, not a generic template. Doxbrix gives you control over colors, typography, logos, and site chrome so your published site matches your brand — with accessible defaults so it looks polished before you customize anything.
Most of these controls live in Settings → Project → Branding (/settings/project).
Branding settings
| Setting | What it controls |
|---|---|
| **Primary color** | The six-digit hex used by project theming — links, buttons, active nav, accents. |
| **Font family** | Project-scoped typography. |
| **Theme mode** | The default theme: **Light**, **Dark**, or **System**. |
| **Light logo** | The logo shown on lighter surfaces. |
| **Dark logo** | The logo shown on darker surfaces. |
| **Support email** | The reader and author support address for the project. |
| **Footer identity** | The footer copyright or identity string. |
Theme mode
Every site supports light and dark appearances. Theme mode sets the default readers see — Light, Dark, or System (which follows the reader's device preference). Provide both a Light logo and a Dark logo so your mark looks right in either mode.
Footer builder
The Footer builder (its own settings section) lets you create a footer for your knowledge base: choose a layout, add links, preview it, and publish. The Footer identity string from Branding appears here as your copyright/identity line.
Reader-experience chrome
The Reader Experience section controls the navigation and chrome around your content:
| Setting | Options / purpose |
|---|---|
| **Top-nav branding** | **Project branding**, **Workspace branding**, or **Minimal**. |
| **Language switch placement** | Where the [language switcher](/reader/language-switcher) appears — **Header**, **Footer**, or **Both**. |
| **Prev/next navigation** | Show or hide the previous/next links at the bottom of each page. |
| **Support CTA label** / **Support CTA URL** | A call-to-action in the chrome (e.g. *"Contact support"*) and where it links. |
Site layout
Beyond visual style, you can choose how the whole site is structured — a classic docs sidebar or a category-driven help center landing page — in Site Layout. See SEO & site layout.
Spaces become top-nav sections
Your spaces appear automatically as the top-bar sections of the published site (Documentation, Guides, API Reference, Changelog), so the navigation you build in the content tree is the navigation readers get.