The update process consists of:
- Updating Wowchemy
- Migrating your content front matter and configuration by applying any relevant breaking changes
Before updating Wowchemy, it is strongly recommended to make a full backup of your website folder.
Then, record your current version, so that after you update Wowchemy, you can apply any relevant breaking changes to the TOML/YAML site configuration and front matter in your
To find your current version, look in
themes/academic/data/academic.toml if it exists. Otherwise, you can get the version from
go.mod where it’ll either be an exact version like
v5.0.0 or it’ll be a build in the form
v<dummy-version-number>-<date>-<build-number>. The first 7 characters of the build number can be cross-referenced in the commit log to check what development updates are available.
Note that if you installed a build in the master version rather than a specific release, then extra care should be taken (such as by checking the git log if you installed with git) as you may be in-between versions and some actions in the relevant release notes may have already been applied.
Install a compatible version of Hugo Extended and its dependencies.
If your site does not have a
go.mod file, follow the Migrate Content guide below and then update your theme to version 5 to convert your site to use Hugo’s Module system. From Version 5 onward, you can update using the command in the Update section below.
Open a Terminal (Command Prompt) and navigate to your site’s folder using the
Update to get the very latest developments:
hugo mod get -u ./...
Alternatively, update to the latest official release:
hugo mod get -u
Migrate your content front matter and configuration if necessary by applying any relevant breaking changes.
When you update Wowchemy itself, you can jump straight to the latest and greatest version. However, content migration requires consecutively applying any relevant steps from each release.
To migrate your TOML/YAML front matter and configuration, apply any relevant steps from the Breaking Changes section of each consecutive release note since the version you were originally on. If a release has no Breaking Changes section, then no changes are required.
For example, if you are updating from v2.4.0 to v3.1.0, then apply the breaking changes for the relevant consecutive releases. In this case, that would require first applying the breaking changes from v3.0.0 and then applying the breaking changes from v3.1.0.
To help migrate content to be compatible with new versions of Hugo and Wowchemy, there are some scripts available in the Hugo Scripts repository which you might find useful.
Check out the release notes for the consecutive version that you are updating to, paying attention to the Breaking Changes section. You can check which version you currently have, refer to the Preparation section above.
If there are any issues after updating, you may wish to compare your site with one of the latest templates, such as the Academic Template to check if the file structure changed, any TOML/YAML settings changed in the configuration files (i.e. all files in the
config/_default/ folder), or any options changed in the front matter of content files (i.e. files in the
If you overrided any Wowchemy/Academic theme files by using Hugo’s inheritance principle then these may cause conflicts after updating. For example, if you have modified theme files in a
layouts folder, your modifications may have become out of sync with the theme they were copied from. Consider temporarily removing your overrides and checking if the original file(s) that you are overriding have changed in any way and require syncing with your custom version of the file(s).
Solve common issues with the Troubleshooting Guide. If the issue is unresolved, feel free to reach out to the community on Discord or the Forum with your GitHub project link.