Ananke moved!

[davidsneighbour]

Ananke moved to its own organisation on April 23, 2026. Please update your references from github.com/theNewDynamic/gohugo-theme-ananke to github.com/gohugo-ananke/theme. Bear with us as we update all documentation and links to reflect this change. Until then, both URLs will continue to work as links as well as in the git operations for cloning and submodules.

The following steps should suffice to update your references if you have not changed the setup:

For Hugo Modules:

search and replace all instances of github.com/theNewDynamic/gohugo-theme-ananke/v2 with github.com/gohugo-ananke/theme/v2 in your site's configuration and run hugo mod tidy to update the module dependencies.

For Git Submodules:

To change the remote URL for your existing submodule, run:

cd path/to/your/repo/themes/ananke # <-- adjust path as needed, keep the 'themes/ananke' part
git remote set-url origin https://github.com/gohugo-ananke/theme.git

Then find .gitmodules in the root of your repository and replace all instances of theNewDynamic/gohugo-theme-ananke with gohugo-ananke/theme in that file as well.

Finally, run git submodule sync to update the submodule configuration.

Issues?

Answer below.

[giopad]

Hi,
I'm using the new version of Ananke 2.13.0 without any problems.
I'd like to ask for your help with a question: when I started using the Ananke theme, I copied it to my computer to test and develop a website for my association. What should I do now if I want to switch to managing the theme via Hugo modules? Do I also need to re-configure page deployment on GitHub?

[davidsneighbour]

If you followed the instructions on the documentation site of how to add the module and overrode the theme ONLY in your own layouts folder (/layouts vs /themes/ananke/layouts) then nothing should break. You basically create the site locally in public and then deploy that to GH pages. At that point the Module has done its things and does not interfere anymore. If the site works locally it should keep working with either way. The submodules way is not going anywhere, so don't feel forced to switch to Hugo Modules.

[guerda]

Thanks for the information and the updates. For me the simple change did not work yet.
I replaced all occurrences of the old organization with the new one and added a hugo mod tidy but it shows me an error message that the module specify it's source as the old organization:

2026-05-03T18:55:14Z INFO Waiting for automatic snapd restart...
dart-sass 1.99.0 from Joe Mooring (jmooring) installed
go: github.com/gohugo-ananke/theme/v2@v2.12.1: parsing go.mod:
	module declares its path as: github.com/theNewDynamic/gohugo-theme-ananke/v2
	        but was required as: github.com/gohugo-ananke/theme/v2
hugo: collected modules in 1480 msERROR failed to load modules: failed to download modules: failed to execute 'go [mod download]': failed to execute binary "go" with args [mod download]: go: github.com/gohugo-ananke/theme/v2@v2.12.1: parsing go.mod:
	module declares its path as: github.com/theNewDynamic/gohugo-theme-ananke/v2
	        but was required as: github.com/gohugo-ananke/theme/v2
 *errors.errorString

Here's the comparison to main, where the old organzation is still there: guerda/guerda.github.io@main...feat_new_ananke_organization

Thanks for any help!

[davidsneighbour]

Two points:

• I had to rename the module to gohugo-ananke/ananke because the Hugo maintainer didn't like the name theme for the repo. This is not the main problem because those paths are redirected at Github, but better having it right.
• My own deploy of the documentation works with Github Pages, but that might be, because I didn't use the old path before. I think what is going on here is that you still somehow have the old reference in there and the hugo mod tidy in your workflow is not at the right place or useful at all.

Try this (not in a workflow, but locally with hugo installed, if possible:

• fix the path to github.com/gohugo-ananke/ananke/v2 (check the documentation repo above
• hugo mod get -u ./... inside of the website repository
• add and commit go.(mod|sum)
• try your workflow again

If that still doesn't work take out the shotgun:

• delete go.sum
• remove everything except the first line starting module and the line starting go with a version from go.mod - (should look something like this with your own module name)
• run hugo mod tidy
• run hugo mod get -u ./...
• add and commit go.(mod|sum)

If all that fails let me know here and I'll try to load your site and see what is going on.

[guerda]

Thank you for looking into this! I will try the steps above.

[guerda]

My mistake was that I still had theme in the module, this threw me off. I replaced all occurences and fixed it, bumped the hugo version and now it works.
Thanks for your help