• Where configuration lives
• How Hugo merges configuration
• How theme defaults work
• What belongs in your site, not the theme
• Installing the theme: Hugo Module
• Installing the theme: Git submodule
• How to override defaults safely
• Where each example goes

This page is the central reference for configuring an Ananke site. It explains where configuration files live, how Hugo combines them, and how the theme’s defaults interact with your own settings. Individual options are documented on their own pages (for example General Configuration, Social Media Networks, and SEO); this page explains the structure those options sit inside.

• Google Analytics
• Production-only loading
• Disabling analytics in development
• Verifying the output
• Privacy

Ananke loads analytics through Hugo’s embedded Google Analytics template. There is no theme-specific analytics parameter — you configure Hugo’s standard service and the theme renders it.

Google Analytics #

Set your measurement ID under Hugo’s services.googleAnalytics configuration:

# config/_default/hugo.toml

[services.googleAnalytics]
ID = "G-XXXXXXXXXX"

With an ID set, the theme includes Hugo’s analytics snippet in the page head.

• The two kinds of header
• Set a featured image
• How the featured image is found
• Image paths and static assets
• Show or hide the header text
• Fallback when there is no image
• Accessibility

The header (or “hero”) is the large area at the top of every page. It shows the page title and, optionally, a background image. This page explains how the header behaves and which front matter and configuration values control it. For fine styling — image fitting, dimming overlay, header height, transparent images — see Hero Section.

• The homepage content file
• Recent posts
• How many posts appear
• Which section recent posts come from
• A homepage without blog posts
• Content alignment
• The homepage hero image

The homepage is built from two parts: the body copy you write in your homepage content file, and an optional list of recent posts that Ananke adds below it.

The homepage content file #

The text at the top of the homepage comes from content/_index.md. Whatever you write in the body of that file is rendered as the homepage introduction:

• The main menu
• Adding entries
• External links
• Controlling the order
• Adding a page from its front matter
• What the theme does and does not render

Ananke shows a navigation menu in the header, next to the site title (or logo) and the social follow links. It is built from Hugo’s main menu.

The main menu #

Define the menu in your site configuration. Each entry needs a name and a target — either a pageRef (a reference to a page in your site) or a url:

• Configure languages
• Translated content files
• Translation fallback
• Translating menus
• Overriding theme interface strings

Ananke is fully multilingual. It ships interface translations for many languages and works with Hugo’s standard multilingual features.

Configure languages #

Declare your languages in the configuration. Each language has a name, a code, a weight (controls order), and its own title:

# config/_default/languages.toml

[en]
languageName = "English"
languageCode = "en-gb"
weight = 1
title = "Example site"

[de]
languageName = "Deutsch"
languageCode = "de-de"
weight = 2
title = "Beispielseite"

The language with the lowest weight is the default. Per-language params can override site parameters — for example a translated read_more_copy (see General content features).

• Enable robots.txt
• How the environment changes the output
• Deploy previews
• Testing the generated file
• Overriding the template

Ananke ships a robots.txt template that changes its output depending on the build environment, so production sites are crawlable while previews and local builds are not.

Enable robots.txt #

Tell Hugo to generate robots.txt by enabling it in your configuration:

# config/_default/hugo.toml

enableRobotsTXT = true

With this on, Hugo renders the theme’s template to public/robots.txt on every build.

• Activate the contact form
• Logo
• Main navigation menu
• Localize date format
• Show taxonomies on pages
• Show or hide dates on pages
• Show images on list page cards

[!IMPORTANT] Please note that Hugo is extensible configurable with more generic or more specific configuration. Please read the documentation about configuration files and configuration directories to learn more about this topic. Whenever Ananke’s documentation refers to the configuration file it refers to any of these possible locations.

• How the page title is built
• Description
• Social previews: Open Graph and Twitter cards
• Canonical URLs
• Content indexing
• Author
• Which front matter affects SEO
• Validating your metadata

Ananke sets sensible SEO and social-sharing defaults using Hugo’s embedded metadata templates (Open Graph, Twitter cards, and schema.org). This page explains what those defaults do and which front matter controls them.

How the page title is built #

The HTML <title> is built from the page title and the site title:

• Configuration
  • Configure social media follow links
    • Set up global options
    • Set your profile or user name
    • Override the profile link
    • Override the label of the social network
    • rel attributes on follow links
  • Configure social media share links
    • Set up sharing networks
    • Disable sharing partially or globally
  • Setup individual new networks
• Available networks
• Icons
  • Adding new icons
  • Further Reading
• Migrate from versions before v2.11
  • Development changes
• Notes
  • Font Awesome
  • Customize Icons
  • Configuring networks with multiple hosts

Ananke automatically adds “follow” link icons to the header and footer and “Share” link icons to pages unless the disable_share parameter is set to true either on the site level (site params) or page level (front matter). Each services can show a label, an icon, and be formatted in a custom color.