Follow the Hugo Quickstart’s instructions on how to add a theme; the URL you’ll want to use is
There’s a sample config.toml file in the root of the indigo theme directory (config.toml.example); copy it to the root of your Hugo site, and rename it to config.tomlafter you’ve made a backup of your current config.toml file (if any).
Set up the parameters in the config file, especially those in the social and params.indieWeb section. Social identifiers that you leave out will not be added to the footer of the site. If you prefer to use a content type other than post, be sure to change the mainSections parameter in the config file as well. For example, if you want content of type posts and updates to show up in lists:
mainSections = ["posts", "updates"]
You can configure the theme to show info about the author; by default, this information is shown; if you’d prefer to leave it out, set ShowBio to false.
Indigo will look for custom CSS in <YOUR_HUGO_SITE>/static/css/custom.css. This will let you add/override styling to your heart’s content, while making it easy to keep Indigo up-to-date. See it in action on angelostavrow.com.
You can add a line to your config.toml file to set this theme as the default:
theme = "indigo"
Or, if you use config.yaml:
Support and Maintenance
Support is provided for the latest stable release of the theme on the latest stable release of Hugo. If something doesn’t seem to be working right, please make sure you’re using the latest version of both.
You can check what version of Hugo you’re using by running the hugo version command; visit the Hugo website for upgrade instructions.
To ensure you’re building the latest version of Indigo, do the following from the command line:
# Go to the /themes/indigo folder
# Make sure you're on the 'master' branch, then pull in any changes
git checkout master
If everything is up to date and things still don’t seem to be working correctly, please open an issue and describe what’s not working as expected.
Going forward, this support committment will be enforced by the minVersion property in theme.toml.
Authors whose themes are included in the Hugo showcase gallery will be required to keep their theme working with the latest version of Hugo. To prepare for this, the following process will be instituted:
With every new release of Hugo, once thebrew_/_chocolatey _package is available_, the development system will be updated, and the demo site and the theme gallery will be built locally.
If everything looks good, a short update will be posted to the demo site to confirm compatibility, with links to the release announcements for those versions Indigo and Hugo, as well as a link to this maintenance process documentation.
If either site doesn’t build successfully, the problem will be fixed.
There are a few definitions and open questions that need to be considered here.
New releases of Hugo are announced and can be subscribed to via RSS. The release date may be estimated by the due date of Hugo milestones.
“Build successfully” means that the demo site renders as intended, and that the theme works as expected in the theme gallery. The gallery builds a standard site that shows off some common features of Hugo, and the demo site is meant to test and showcase features of Indigo.
Indigo IndieWeb Features
A thorough writeup of the theme has been graciously written by @infominer33.