Customize your site
Start with native configuration and data. Use small site partial/asset overrides only when the supported settings cannot express your choice; do not copy the whole theme. Menus and regions select content; named icons select UI artwork. The parameter reference owns the defaults.
Identity and appearance
[params]
color_mode = 'auto'
page_reveal = false
[params.identity]
title = 'My notebook'
subtitle = 'Ideas worth keeping | A little more every day'
image = 'images/sidera-parallax-circle.svg'Identity title falls back to the native site title. The first pipe separates the
resting/hover subtitle; labels remain plain escaped text. Identity image is empty
by default. It is distinct from collection params.logo, an author’s avatar,
a list card’s cover and an inline menu icon. Safe local images resolve from
native resources/assets/static; identity never downloads an image at build time.
Color mode is auto/light/dark; a saved visitor choice wins. Auto follows the OS.
The optional social-menu action cycles dark → light → auto. With no JavaScript,
CSS follows the owner default/OS and ordinary navigation stays usable. Default-on
page-entry motion respects reduced motion, focus, history and hash navigation;
site/language page_reveal: false omits it.
Original Parallax brand images
The optional assets are images/sidera-parallax-circle.svg,
images/sidera-parallax-square.svg and images/sidera-parallax-32.png. Circle and
square use fixed slate #73868c and bronze #9a805f, not currentColor. Native site
assets can override the same virtual paths. Fine tips soften at 16px; similar
midtone backgrounds are unsuitable. These are not all-engine favicon guarantees.
Favicons are site policy. In layouts/_partials/sidera/head-extra.html:
{{ with resources.Get "images/sidera-parallax-square.svg" }}
<link rel="icon" type="image/svg+xml" sizes="any" href="{{ .RelPermalink }}">
{{ end }}
{{ with resources.Get "images/sidera-parallax-32.png" }}
<link rel="icon" type="image/png" sizes="32x32" href="{{ .RelPermalink }}">
{{ end }}Fonts and CSS
Use the same head hook to load a site-owned CSS resource after theme CSS.
Override --ui, --reading, --inline-code and --code separately when needed.
The baseline UI/prose stack starts with LXGW WenKai and falls back through system
fonts; fenced code starts with Source Code Pro and monospace alternatives. Naming
those fonts does not download them. Loading or licensing additional fonts is the
site’s choice. Bundled conditional KaTeX math fonts are separate. Giscus matches
the baseline stack, not arbitrary site CSS overrides automatically.
Interface color roles
The interface shares the content palette: cyan for interaction accents, blue for links, red for pinned labels and errors, and yellow for search matches. Disclosure labels use blue, green and orange text variants. Existing neutral canvas, panels and elevated surfaces retain their own hierarchy.
Override semantic CSS tokens after theme CSS when a site needs different styling:
| Token | Purpose |
|---|---|
--secondary-text | Readable secondary labels, counts and link destinations |
--quiet | Low-emphasis decorative details |
--control-border | Native form-control boundaries, separate from decorative --line separators |
--card-hover-shadow | Shared neutral elevation for interactive cards and the pinned collection bar |
--accent / --accent-soft | Interaction foreground/focus and subtle background |
--link | Link foreground, including prose links |
--accent-fill / --accent-on-fill / --accent-fill-hover | Filled interaction background, its foreground and hover background |
--pin | Pinned-content label |
--danger | Error text and invalid JSX control borders |
--code-keyword / --code-literal | Syntax keyword and string/number foregrounds |
--decorative-spectrum | Shared comma-separated color stops for the avatar ring and search underline |
These roles are independent even when their default family is the same. Set a
filled background and its foreground together and check normal, hover, focus and
light/dark states. In particular, changing --pin does not change errors or syntax
highlighting. Palette family overrides belong at :root; use adaptive values such
as light-dark(light-value,dark-value) where appropriate.
The built-in Giscus stylesheet mirrors Sidera’s default text, link, accent and
filled-control colors. It does not automatically inherit arbitrary site CSS
customizations; a site can override assets/css/giscus.css separately. Artwork,
authored menu accents, renderer palettes and decorative rainbow effects retain
their separate color policies. The two rainbow effects share a light/dark-aware
spectrum with even lightness; their animation, dimensions and reduced-motion
behavior are independent of that color list.
Article titles use a root-relative size above ordinary body H2 headings. Readable
secondary labels use --secondary-text without additional opacity. Interactive
cards share a neutral hover shadow; pinned collection navigation uses a single
translucent blurred surface with no text glow. Social controls use the same flat
interaction treatment in sidebars and compact headers.
English and Chinese UI
For Chinese controls around unsuffixed content:
defaultContentLanguage = 'zh'
locale = 'zh-CN'For shared-directory filename translations:
defaultContentLanguage = 'en'
defaultContentLanguageInSubdir = true
[languages.en]
locale = 'en-US'
weight = 1
[languages.zh]
locale = 'zh-CN'
weight = 2Author _index.zh.md / index.zh.md for real Chinese counterparts, including their
own root policies/cascades. Unsuffixed pages belong to the default language; no
body is auto-translated and no links to absent translations are invented.
The default build credit links to Hugo and
Sidera in both languages.
For custom wording, override only desired messages in site i18n/en.toml or
i18n/zh-CN.toml:
[built_with]
other = 'Powered by [Hugo](https://gohugo.io/) and [Sidera](https://github.com/calfzhou/hugo-theme-sidera).'built_with and the neutral content license_default are Markdown; other catalogs
are plain escaped text. Hugo falls back to the configured default language, not
always English. Use strict builds with --printI18nWarnings to catch missing keys.