Hugo Theme Ananke on Ananke Documentation

Configuration Reference

Sat, 06 Jun 2026 08:00:00 +0700

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.

Introduction to Hooks & Filters

Sun, 17 May 2026 08:00:00 +0700

since 2.17.0

Hooks and filters
Difference between hooks and filters
- Hooks
- Filters
Terminology
Simple hook calls
Extended hook calls
Extended hook options
- hook
- context
- cache
Hook partial location
Disabling unused hook messages
Recommended usage pattern

Hooks and filters #

Ananke provides a small hooks system that lets site projects inject or transform markup without changing the theme templates directly.

Installation as a Hugo Module (recommended)

Fri, 16 Jan 2026 08:00:00 +0700

Methods
Requirements
Installation

Hugo Module based installation for the Ananke theme for Hugo.

Methods #

Install Ananke as Hugo Module - this page
Install Ananke as Git Submodule

Requirements #

Install Hugo (extended or extended/deploy edition, 0.128.0 or later)
Install Git
Install Golang

Installation #

To install or create a Hugo website from scratch with the Ananke theme using the Hugo Module method, follow these steps:

Installation as Git Submodule

Fri, 16 Jan 2026 08:00:00 +0700

Methods
Requirements
Installation

Git Submodule based installation for the Ananke theme for Hugo.

Methods #

Install Ananke as Hugo Module
Install Ananke as Git Submodule - this page

Requirements #

Install Hugo (extended or extended/deploy edition, 0.128.0 or later)
Install Git

Installation #

To install or create a Hugo website from scratch with the Ananke theme using the submodule method, follow these steps:

Hook examples

Sun, 17 May 2026 08:00:00 +0700

since 2.17.0

This page collects worked examples for the theme’s hook points. Each one shows the partial you create, where the output lands, and why you would reach for that particular hook.

If you have not read it yet, start with the introduction for the call mechanics, and keep the list of all hooks handy for the available hook names.

Before you start
Add a third-party script in the head
Defer analytics to the end of the body
Add a site-wide announcement bar
Extend the footer (and cache it)
Add secondary navigation using the page context
Add an author bio after the content
Override the article section link
Use a hook as a filter

Before you start #

Every example below is a file you create in your site, never in the theme:

Upgrading from theNewDynamic to gohugo-ananke

Sat, 06 Jun 2026 08:00:00 +0700

What changed
Migrate a Hugo Module install
Migrate a Git submodule install
Confirm the theme is loaded
Common failure cases

Ananke moved to its own organisation in April 2026. The repository changed from: github.com/theNewDynamic/gohugo-theme-ananke to github.com/gohugo-ananke/ananke.

Both URLs still resolve for now, so existing sites will keep building, but you should update your references so future updates come from the new location.

What changed #

Organisation and repository name changed as shown above.
Module path changed from github.com/theNewDynamic/gohugo-theme-ananke/v2 to github.com/gohugo-ananke/ananke/v2. The /v2 suffix is unchanged and still required for the latest theme on the v2 branch.
Installation methods are unchanged. If you are installing fresh rather than migrating, follow Install as Hugo Module or Install as Git Submodule instead of this page.

Migrate a Hugo Module install #

Search your site configuration for the old module path and replace every instance of github.com/theNewDynamic/gohugo-theme-ananke/v2 with github.com/gohugo-ananke/ananke/v2.

All Hooks & Filters

Sun, 17 May 2026 08:00:00 +0700

since 2.17.0

This page lists every hook point the theme wires into its templates. Each entry is the value you pass as the hook key (see the introduction for how to call hooks and filters).

A hook point does nothing until your site provides a matching partial at layouts/_partials/hooks/<name>.html. Until then the hook is “unused” — the theme prints an optional debug notice and renders nothing.

Since

Sun, 07 Jun 2026 08:00:00 +0700

since 2.18.0

Quick summary #

The since shortcode is used to render a small badge marking the release a feature was introduced in (for example “since 2.17.0”). It is intended for documentation and changelog-style pages. Use it when you need to mark, at a glance, which version of a project a feature first shipped in. By default the badge is plain text; configure a release URL to turn it into a link.

Analytics

Sat, 06 Jun 2026 08:00:00 +0700

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.

Contact Form

Sat, 06 Jun 2026 08:00:00 +0700

What it outputs
Required configuration
Form fields
A complete contact page
Using a form backend
Spam protection
Customising labels
Limitations

Ananke includes a form-contact shortcode that renders a ready-styled contact form you can drop into any page.

What it outputs #

The shortcode outputs an accessible HTML <form> with name, email, and message fields and a submit button, styled to match the theme. It submits with POST to the address you give in the action parameter.

Content Types and Archetypes

Sat, 06 Jun 2026 08:00:00 +0700

Pages
Posts
List pages
Taxonomy pages
Archetypes
Front matter

Ananke builds on Hugo’s standard content model. This page explains the kinds of content you will create and the front matter each one needs. For the full list of front matter keys, see Frontmatter.

Pages #

A page is a single standalone document, such as an About or Contact page. Create one as a file directly under content/:

Custom CSS

Sat, 06 Jun 2026 08:00:00 +0700

Where custom CSS goes
Register your CSS
Static files and external stylesheets
Asset pipeline limitations
Troubleshooting checklist

You can add your own CSS on top of the theme’s styles without editing the theme. This page covers the common path; for the full stylesheet pipeline (build order, social hover colours, source maps) see Styles.

Where custom CSS goes #

Put your CSS files in your project’s assets/ananke/css/ directory:

Documentation Style

Sat, 06 Jun 2026 08:00:00 +0700

Principles
Examples
Configuration paths
Parameter names
Defaults before overrides

These rules keep Ananke’s documentation beginner-friendly and consistent. Follow them when adding or editing pages.

Principles #

Use simple language. Write for someone new to Hugo. Avoid jargon, or explain it the first time.
Do not assume Hugo knowledge. Do not rely on the reader knowing Hugo’s template lookup order, configuration merging, or section rules — link to the relevant explanation instead.
Avoid undocumented magic values. If a value matters (a class name, a slug, a path), say where it comes from and what valid values look like.

Examples #

Prefer full examples over fragments. A reader should be able to copy an example and have it work, not assemble it from pieces.
Always say where a file goes. Start every code block that represents a file with a comment naming its path, for example # config/_default/params.toml or a +++ front matter block.
Use TOML first. TOML is the default example format. YAML and JSON are optional follow-up examples, not required.
State the expected result. After an example, briefly describe what the reader should see once they apply it.

Configuration paths #

Say whether an example is site configuration or page front matter.
When installation method matters, say whether the example is for Hugo Modules or Git submodules.
Use the current module path github.com/gohugo-ananke/ananke/v2 in installation examples.

Parameter names #

Use the current [ananke] parameter namespace (for example ananke.show_recent_posts). Document any legacy flat parameter only as a deprecation note, never as the recommended form.
Verify a parameter against the theme before documenting it, rather than copying it from an older page.

Defaults before overrides #

Explain a feature’s default behaviour first, then how to override it.
Make clear when a setting is optional and what happens if it is omitted.
Keep guidance consistent across pages — if two pages mention the same setting, they should agree and, where useful, link to one canonical explanation.

Header and Hero

Sat, 06 Jun 2026 08:00:00 +0700

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.

Homepage

Sat, 06 Jun 2026 08:00:00 +0700

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:

Images

Sat, 06 Jun 2026 08:00:00 +0700

Static images
Images in Markdown
Page bundle images
Featured images
Social sharing images
Alt text
Common path mistakes

This page explains the ways to add images to an Ananke site and the paths each one uses.

Static images #

Files in your project’s static/ directory are copied to the site root as-is. A file at static/images/example.jpg is served at /images/example.jpg:

my-site/
└── static/
 └── images/
 └── example.jpg # available at /images/example.jpg

Reference static images with a leading / (note: no static in the URL).

Layout Map

Sat, 06 Jun 2026 08:00:00 +0700

Which template renders which page
The base template
Important partials
Shortcodes
Overriding any of these

This page maps Ananke’s templates to the pages they render. It is aimed at contributors and advanced users who want to find the right file quickly.

Which template renders which page #

Page type	Template	Example URL
Homepage	`layouts/home.html`	`/`
Section list	`layouts/list.html`	`/posts/`
Single page or post	`layouts/single.html`	`/about/`, `/posts/my-post/`
Taxonomy list (a term)	`layouts/taxonomy.html`	`/tags/hugo/`
Taxonomy terms index	`layouts/terms.html`	`/tags/`
Not found	`layouts/404.html`	any missing URL

Summaries on list pages and the homepage are rendered by layouts/summary-with-image.html (and layouts/summary.html).

Menus

Sat, 06 Jun 2026 08:00:00 +0700

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.

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:

Minimal Blog

Sat, 06 Jun 2026 08:00:00 +0700

A small blog: a homepage that lists recent posts, an about page, and a posts section.

File tree #

example-site/
├── config/
│ └── _default/
│ ├── hugo.toml
│ ├── module.toml
│ ├── menus.toml
│ └── params.toml
└── content/
 ├── _index.md
 ├── about.md
 └── posts/
 └── first-post.md

Configuration #

# config/_default/hugo.toml

baseURL = "https://example.com/"
languageCode = "en-gb"
title = "My Minimal Blog"
enableRobotsTXT = true

[taxonomies]
tag = "tags"
category = "categories"

# config/_default/module.toml

[[imports]]
path = "github.com/gohugo-ananke/ananke/v2"

# config/_default/menus.toml

[[main]]
name = "Home"
pageRef = "/"
weight = 10

[[main]]
name = "Posts"
pageRef = "/posts/"
weight = 20

[[main]]
name = "About"
pageRef = "/about/"
weight = 30

# config/_default/params.toml

[params]
mainSections = ["posts"]
read_more_copy = "Read more"
show_reading_time = true

[ananke]
show_recent_posts = true

Sample content #

+++
title = "My Minimal Blog"
featured_image = "/images/home.jpg"
+++

Welcome — this is the homepage introduction. Recent posts appear below.

+++
title = "About"
+++

A few words about me and this blog.

+++
title = "First post"
date = 2026-06-06T10:00:00+07:00
description = "The very first post on this blog."
tags = ["hugo", "ananke"]
+++

Hello world — this is my first post.

What it looks like #

The homepage shows the introduction text and a list of recent posts (newest first). The header uses /images/home.jpg as a hero, or a black background if the image is absent. Each post shows its reading time.

Multilingual and i18n

Sat, 06 Jun 2026 08:00:00 +0700

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).

Multilingual Site

Sat, 06 Jun 2026 08:00:00 +0700

A two-language site (English and German) with side-by-side content and translated menus.

File tree #

example-site/
├── config/
│ └── _default/
│ ├── hugo.toml
│ ├── module.toml
│ ├── languages.toml
│ ├── menus.toml
│ └── params.toml
└── content/
 ├── _index.md
 ├── _index.de.md
 ├── about.md
 └── about.de.md

Configuration #

# config/_default/hugo.toml

baseURL = "https://example.com/"
title = "Example site"
enableRobotsTXT = true
defaultContentLanguage = "en"

# config/_default/module.toml

[[imports]]
path = "github.com/gohugo-ananke/ananke/v2"

# 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"

# config/_default/menus.toml

[[en.main]]
name = "About"
pageRef = "/about/"
weight = 10

[[de.main]]
name = "Über uns"
pageRef = "/about/"
weight = 10

# config/_default/params.toml

[ananke]
show_recent_posts = false

Sample content #

+++
title = "Welcome"
+++

This is the English homepage.

+++
title = "Willkommen"
+++

Das ist die deutsche Startseite.

The about page is translated the same way: content/about.md and content/about.de.md.

No-blog Static Site

Sat, 06 Jun 2026 08:00:00 +0700

A simple brochure site with a homepage and a few standalone pages — no blog or post list.

File tree #

example-site/
├── config/
│ └── _default/
│ ├── hugo.toml
│ ├── module.toml
│ ├── menus.toml
│ └── params.toml
└── content/
 ├── _index.md
 ├── about.md
 └── services.md

Configuration #

# config/_default/hugo.toml

baseURL = "https://example.com/"
languageCode = "en-gb"
title = "Example Studio"
enableRobotsTXT = true

# config/_default/module.toml

[[imports]]
path = "github.com/gohugo-ananke/ananke/v2"

# config/_default/menus.toml

[[main]]
name = "Home"
pageRef = "/"
weight = 10

[[main]]
name = "Services"
pageRef = "/services/"
weight = 20

[[main]]
name = "About"
pageRef = "/about/"
weight = 30

# config/_default/params.toml

[ananke]
show_recent_posts = false

Sample content #

+++
title = "Example Studio"
featured_image = "/images/studio.jpg"
+++

We design and build small, fast websites. Get in touch to start a project.

+++
title = "Services"
+++

What we offer and how we work.

+++
title = "About"
+++

Who we are.

What it looks like #

The homepage shows only the introduction and hero image — no post list, because show_recent_posts is false. The menu links the standalone pages.

Overriding Partials

Sat, 06 Jun 2026 08:00:00 +0700

How Hugo lookup order works
The safe override pattern
A full example
Keep overrides small
Update risks

Ananke is built from many small template files called partials. You can change any of them without editing the theme, by placing a file with the same path in your own project.

How Hugo lookup order works #

When Hugo needs a partial, it looks in your project first and the theme second. If a file exists at the same path in both places, your copy wins. This is what makes safe customisation possible: you never touch the theme, you just shadow the file you want to change.

robots.txt and Environments

Sat, 06 Jun 2026 08:00:00 +0700

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.

Summaries and Reading Time

Sat, 06 Jun 2026 08:00:00 +0700

Automatic summaries
The manual summary divider
A custom summary in front matter
The read more link
Reading time and word count
How list pages use summaries

On list pages and the homepage, Ananke shows a short summary of each post rather than its full content. This page explains where that summary comes from and how to control it.

Automatic summaries #

If you do nothing, Hugo generates the summary automatically from the start of the content (by default the first 70 words). This needs no configuration and works for every page.

The manual summary divider #

To choose exactly where the summary ends, add a divider in your content. Hugo uses everything before it as the summary:

This paragraph is the summary shown on list pages.

This and everything after it is only shown on the full page.

A custom summary in front matter #

To write a summary that is independent of the body text, set summary in front matter:

Taxonomies

Sat, 06 Jun 2026 08:00:00 +0700

Default taxonomies
Adding terms to content
Term list and terms pages
Where taxonomy links appear
Changing or adding taxonomies

Taxonomies group your content by shared terms. Ananke supports Hugo’s two default taxonomies — tags and categories — out of the box.

Default taxonomies #

Hugo enables tags and categories by default, so you do not need to configure anything to use them. If you want to declare them explicitly (for example to add or rename taxonomies), set them in your configuration:

Contributors

Wed, 15 Apr 2026 08:00:00 +0700

Contributors

Ananke lives from the work of its contributors.

Contributors #

Total contributors: 1

Contributor	Contributions	Repositories
Patrick Kollitsch	`bug`, `code`, `doc`	`documentation`

Calculate and show reading time

Fri, 16 Jan 2026 08:00:00 +0700

Configuration
Notes

The reading time displayed in layouts/_default/single.html can now be configured via a reading_speed parameter, instead of always using Hugo’s computed .ReadingTime. (GitHub)

The theme still only shows reading time when show_reading_time = true is enabled (page param or section param). (GitHub)
The displayed value is now computed like this:

Colours

Fri, 16 Jan 2026 08:00:00 +0700

How the theme uses classes
Background colour
Body and font classes
Content text colour
Post content typeface
Header and hero classes
Accessibility and contrast

Ananke styles colours and typography with Tachyons utility classes. You choose a class name (for example bg-blue or near-black) and the theme applies it. This page lists the class-based settings.

How the theme uses classes #

Each setting below takes a Tachyons class as its value. Background colours use the bg- prefix (for example bg-navy); text colours use the colour name directly (for example near-white). Browse the available values in the Tachyons skins reference.

Comments

Fri, 16 Jan 2026 08:00:00 +0700

Disqus
Commento.io
Disabling comments
Privacy

Ananke currently supports two commenting systems: Disqus and Commento. Both render below the content on single pages.

Disqus #

Using Disqus as a comment system for your website is an internal feature of Hugo. For more information see the official Hugo documentation.

[services.disqus]
shortname = 'YOURSHORTNAME'

Note that the setup for Disqus is NOT done inside of the params section, but with in the services section of your config file. To turn off Disqus, remove, or comment out the preceding lines.

External Links

Fri, 16 Jan 2026 08:00:00 +0700

a.ananke-social-link[target="_blank"]::after {
 content: "↗" / "Open in new window";
 display: inline-block;
 margin-inline-start: 0.25em;
 font-size: 0.85em;
 line-height: 1;
 vertical-align: 0.1em;
}

.new-window {
 opacity: 0;
 display: inline-block;
 vertical-align: top;
}
.link-transition:hover .new-window{
 opacity: 1;
}

@supports (content: "x" / "y") {
 .new-item::before {
 content: "★" / "Highlighted Text:";
 }
}

@supports not (content: "x" / "y") {
 .new-item::before {
 content: "★";
 alt: "Highlighted Text:";
 }
}

Revealing URLs in print styles sheets #

@media print {
 a[href^="http://"]:after,
 a[href^="https://"]:after
 {
 content: ' (' attr(href) ')';
 }
}

custom counters #

ol {
 list-style-type: none;
 counter-reset: mylist;
}

li {
 counter-increment: mylist;
}

li::before {
 content: '🤤 ' counter(mylist) ': ';
}

Frontmatter

Fri, 16 Jan 2026 08:00:00 +0700

Using a canonical url
Common Options
Example: Disabling Breadcrumbs
Example: Custom Layout
Example: Using linktitle
Defaults & Fallbacks
Notes

Using a canonical url #

If you want to publish content that is already published on a different site you need to reference a canonical URL of the original content. By defining the canonicalUrl in the front matter definition the canonical url is set in the headers.

General

Fri, 16 Jan 2026 08:00:00 +0700

Author
Read more link
Show Reading Time and Word Count

Author #

Add an author to a page by setting the author key in its front matter. The author is shown below the title on single pages and on image summary cards.

---
title: My First Post
author: Jane Doe
---

To set a default author for the whole site, add author to your site parameters. Page front matter overrides the site default.

General Configuration

Fri, 16 Jan 2026 08:00:00 +0700

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.

Getting Started

Fri, 16 Jan 2026 08:00:00 +0700

1) Install the theme
2) Confirm Hugo version compatibility
3) Configure required basics
4) Add content and front matter
5) Customize visual style
6) Run and verify locally

This guide summarizes the first configuration steps after installing Ananke.

1) Install the theme #

Choose one installation method:

2) Confirm Hugo version compatibility #

Check what Hugo version you have installed with hugo version and then compare against the minimum requirement in config/_default/module.toml.

Hero Section

Fri, 16 Jan 2026 08:00:00 +0700

Change the hero background
Use the images front matter array
Featured image as Page Resources
Other hero settings
Set a background color behind transparent hero images

Change the hero background #

For any page or post you can add a featured image by including the local path in front matter (see content in the exampleSite/content/en/_readme file for examples): featured_image = '/images/gohugo-default-sample-hero-image.jpg'

Use the images front matter array #

If featured_image is not set, Ananke will use the first value from the page’s images front matter array as the featured image.

SEO

Fri, 16 Jan 2026 08:00:00 +0700

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:

Social Media Networks

Fri, 16 Jan 2026 08:00:00 +0700

Configuration
Available networks
Icons
- Adding new icons
- Further Reading
Migrate from versions before v2.11
- Development changes
Notes

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.

Styles

Fri, 16 Jan 2026 08:00:00 +0700

Update font or body classes
Stylesheet Generation

Update font or body classes #

The theme is set, by default, to use a near-white background color and the “Avenir” or serif typeface. You can change these in your config file with the body_classes parameter, like this:

[params]
 body_classes = "avenir bg-near-white"

which will give you a body class like this:

Troubleshooting

Fri, 16 Jan 2026 08:00:00 +0700

Diagnostic commands
Common problems
Sorry, but “$FEATURE does not work” doesn’t work for us

Diagnostic commands #

Before digging into a specific problem, these commands tell you most of what you need to know:

Hugo Theme Ananke on Ananke Documentation

Configuration Reference

Introduction to Hooks & Filters

Hooks and filters #

Installation as a Hugo Module (recommended)

Methods #

Requirements #

Installation #

Installation as Git Submodule

Methods #

Requirements #

Installation #

Hook examples

Before you start #

Upgrading from theNewDynamic to gohugo-ananke

What changed #

Migrate a Hugo Module install #

All Hooks & Filters

Since

Quick summary #

Analytics

Google Analytics #

Contact Form

What it outputs #

Content Types and Archetypes

Pages #

Custom CSS

Where custom CSS goes #

Documentation Style

Principles #

Examples #

Configuration paths #

Parameter names #

Defaults before overrides #

Header and Hero

Homepage

The homepage content file #

Images

Static images #

Layout Map

Which template renders which page #

Menus

The main menu #

Minimal Blog

File tree #

Configuration #

Sample content #

What it looks like #

Multilingual and i18n

Configure languages #

Multilingual Site

File tree #

Configuration #

Sample content #

No-blog Static Site

File tree #

Configuration #

Sample content #

What it looks like #

Overriding Partials

How Hugo lookup order works #

robots.txt and Environments

Enable robots.txt #

Summaries and Reading Time

Automatic summaries #

The manual summary divider #

A custom summary in front matter #

Taxonomies

Default taxonomies #

Contributors

Contributors #

Calculate and show reading time

Colours

How the theme uses classes #

Comments

Disqus #

External Links

Revealing URLs in print styles sheets #

custom counters #

Frontmatter