Skip to content

Customization

Site-level configuration — brand, navigation, layout, search, languages, versions, print and agent output.

This section covers site-level configuration: the parameters in hugo.yml, the data files under data/, and the style entry points under assets/. Writing an individual page and its front matter is in Authoring.

Find it by what you want to change

What you want to change Page
Site name, logo, favicon Brand and appearance
Colours, light and dark mode, fonts Brand and appearance
The navbar menu and its dropdowns Navigation and menus
Sidebar width, icon density, outline depth Layouts and page types
The home page and landing pages Home and landing pages
Full-text search and its index scope Search
What appears in the command palette Command palette
Keyboard shortcuts Keyboard navigation
Adding a language Languages
Multi-version sites and the archive banner Versions
Tags and categories Taxonomies
Edit this page, last modified, contributors Repository links and page info
Print and whole-chapter export Print
llms.txt and the per-page .md output AI-agent support
A parameter’s type and default Configuration

Comments, analytics and deployment need an external service; they are in Operations.

The one place site parameters are defined — every key the theme reads, with its type, default and the guide that covers it.

Replace the site name, logo, favicon, accent colour, light and dark palettes and fonts, using configuration and two SCSS entry points.

Assemble a home page from one local YAML file — hero, cards, capability panels, timeline, pricing, case studies, downloads. Any page can become a landing page with the same sections.

Configure the navbar menu and its dropdowns, the section switcher, breadcrumbs, page actions, the pager and the footer links.

Let type decide which shell a page uses, then adjust sidebar width and icons, outline depth, section index style and page width.

Turn on local search, control index size and result ranking, and make CJK queries land.

One dialog carrying page search, page actions and site commands — how to open it, what it groups, and how to add commands of your own.

Every single-key shortcut, when each stands down for typing, and how to turn them off per site or per page.

Add a language, keep translations side by side, configure menus and interface strings per language, and align heading anchors across languages.

Configure the version switcher and the archive banner, and choose how several versions are laid out across domains.

Give pages a second index that cuts across the directory tree with tags and categories — term pages, filter chips, the rail cloud and the navbar panel are all automatic.

Wire “edit this page”, “open an issue” and “view history” to your repository, and show the last-modified line, contributors and the feedback widget at the page end.

A single page goes to the browser’s Cmd/Ctrl+P; a whole section becomes one continuous document through the print output format.

Give every page a .md twin, the site root an llms.txt, and the reader a way to hand the current page to ChatGPT or Claude.