Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


This repo contains the source code used to generate, including themes.

It is powered by Hugo, has a responsive design, supports translations, and automatically updates when new releases are made.

How to Edit Content

Generally, you should familiarize yourself with the basics of how Hugo works.

  • Content files are stored under: content/en
  • The base language is English, and all new content should be created in English.
  • Although Hugo supports multiple formats, please author new content files as Markdown (.md) files. (Learn Markdown)

You can manually create content files (for example as content/<CATEGORY>/<FILE>.<FORMAT>) and provide metadata in them, however you can use the new command to do few things for you (like add title and date):

hugo new news/

Will generate a new file (replace the ## with the desired number), using the archetypes/ template.

Special-Case: FAQ Entries

FAQ entries are only displayed on the homepage, but are pulled from folders in the content directory. Specifically, content/en/faq/*/.

Each faq subfolder must contain an containing the front-matter:

headless: true # no-translate

to mark it as a "Headless Bundle".

The homepage pulls the list of faq subfolders ("categories") that it will display from: data/homepage_faq_categories.json. Each "category" string in this .json file should exist as a translated string in the themes/wz2100net/i18n/en.json strings file.

How to Edit the Theme

See Hugo's documentation on themes.

Some tips:

  • The home page template is located in themes/wz2100net/layouts/index.html. This contains the bulk of the home page's body.
  • The navbar on all pages is generated by: themes/wz2100net/layouts/partials/navbar.html
    • This uses a combination of fixed links, and drop-downs generated by processing Hugo menus and available translations.
    • The main menu is generated from front-matter in the content. See, for example,
    • Other menus are declared in the config.yaml.
  • You'll also find head.html and footer.html templates in the partials folder.

Translatable Strings

Adding new translatable strings into theme partials / templates is accomplished in two steps:

  1. Wrap the string in {{ i18n "..." }} inside the partial / template.
  2. Add a new entry for the string (if it does not already exist) in themes/wz2100net/i18n/en.json

How to Build / Preview Locally

Hugo makes it very easy to build / preview the full website locally.

  1. Download & install Hugo.
  2. Clone this repo.
  3. Inside the repo folder, run hugo server. Example:
hugo server --minify --i18n-warnings --gc --path-warnings

Hugo will output a localhost url you can simply open in your local web browser.

Automatically Updated Data

Certain data is updated automatically / on a schedule:

Building for Production

Production builds are handled automatically by the GitHub Actions workflow(s). For reference:

To properly build for production, the HUGO_ENV environment variable must be set to "production". This configures various important options - such as a robots.txt file that actually allows search engines.


HUGO_ENV="production" hugo --gc --minify --i18n-warnings

For more, see the ci_hugo_build.yml workflow.