In this release
- Header rework and navigation
- Responsive hero images
- Documentation improvements
- Upgrading and requirements
- Full changelog
- Theme development and maintenance
- Shared development server
- Production builds and release previews
- Maintenance and contributor tooling
Header rework and navigation
The header now supports configurable groups of components. Arrange the logo, languages, menu, social links, title, and description, or add your own components through hooks. Navigation classes can be set per page, through a cascade, or site-wide, with page settings taking priority. See Header layout, hooks, and styling.
Main navigation now displays nested menu entries. Choose how desktop submenus behave with ananke.navigation.submenu_mode:
split(default): the parent links to its page, and a separate arrow opens its submenu.hover: hovering opens the submenu, and clicking the parent follows its link.click: clicking the parent opens the submenu. Its page appears first as Overview, or with its explicitlinkTitle.toplevel: display only the first level, without submenus.
The setting supports page, cascade, and site configuration, plus an override when calling the reusable menu partial. Separate menu instances receive unique control IDs. See Menu modes and configuration.
Below 60em, every mode uses a hamburger menu. Opening it shows one list with all included child levels expanded and indented. Parents remain links where available; there are no individual submenu toggles or hover actions. toplevel still omits children. Keyboard controls support Escape, and focus moves to a visible control when the layout changes. Without JavaScript, navigation remains available.
Responsive hero images
Home, list, and individual-page headers can now use images from page bundles and assets/. Ananke resolves a matching page resource first, then an asset, and otherwise uses the configured URL. Existing image fallbacks remain available, and summary cards also support asset images.
For supported local raster images, Hugo generates smaller versions, and CSS selects a suitable size without JavaScript. Images are never enlarged. The optional ananke.responsive_image_widths setting defaults to [480, 960, 1440, 1920], with page settings taking priority over cascades and site configuration. Static images, external URLs, and SVGs retain their original files. Existing crop, overlay, and spacing settings still apply.
This also fixes an inline style that prevented responsive backgrounds on individual pages. See Responsive header images and Page headers.
Documentation improvements
The documentation is organised into six topic sections, with overview pages and redirects from previous URLs. Header customisation, hooks, migration, image handling, summaries, and reading time have updated guidance.
Option references use compact, labelled entries that stack on narrow screens. Other tables scroll within their own containers, with smaller text and wrapping for long names. Header photographs, quieter table-of-contents styling, heading links in the gutter, and a more visible edit-page button improve the reading experience. Browse the documentation.
Upgrading and requirements
Existing overrides of site-header.html, page-header.html, and site-navigation.html still render, but now emit deprecation warnings. Builds using --panicOnWarning must migrate or temporarily suppress the relevant warnings. These override extension points are scheduled for removal in Ananke v3. Review custom header markup, styles, and scripts against the header migration guide.
Existing menu entries with a parent now appear as children. Choose submenu_mode = "toplevel" to retain first-level-only output. Existing static and external header image settings remain supported.
- Theme: Hugo v0.160.0 or later.
- Documentation builds: configured and tested with Hugo v0.170.1.
- Shared development scripts: Node.js 22.18 or later, with documentation dependencies installed.
Full changelog
These comparisons cover all changes from the previous main state to the integrated development state:
Theme development and maintenance
Shared development server
Run npm run dev from either repository to preview the documentation with the local theme at http://127.0.0.1:1313/. The repositories must be siblings. The launcher explicitly overrides the pinned module version with the local theme checkout.
It pairs matching local branches, with a development fallback when the companion lacks a feature branch. main and development require matching companion branches. It prints the selected branches, refuses unsafe branch switches, and checks the port before switching. It never stashes, discards, fetches, or pulls work. Restart after changing branches. See Shared development server.
Production builds and release previews
Documentation builds now select the theme explicitly:
npm run buildandnpm run deploy:productionuse the latest stable theme release, clearing inherited local development overrides.npm run build:previewandnpm run deployuse a remote preview revision, defaulting todevelopment. A branch, tag, or commit can be selected for testing; deployment creates a draft site.
Builds run Hugo and search indexing in an isolated source tree, leaving checked-in module files unchanged. Logs show the resolved theme version, and --expect-theme-version can stop a build that resolves an unexpected release.
Publish the theme release before promoting and deploying its documentation. Merging the theme to main alone does not make a stable release available. See Production and preview builds and Release and publication order.
Maintenance and contributor tooling
Development dependencies and editor workspace settings have been updated. Contributor and AI guidance is consolidated into scoped instructions, with clearer verification, configuration priority, testing, and release procedures. The repository also adds Posthaste configuration and excludes generated Playwright reports.