@deining et all, let's use this issue to track tasks that are needed to support use of Docsy as a Hugo module.

• Enable to pull in docsy as hugo module #871
  • test with git as submodule (smooth transition for existing users) - Ensure a smooth transition for existing docsy-as-submodule users #848
  • test with docsy as hugo module
• config.toml: change order of language settings and theme/module declaration docsy-example#162
• User guide: adding instructions on how to use and update docsy as hugo module #802
• Updating docsy theme submodule docsy-example#164
• docsy as module: refer to current HEAD of repo docsy-example#169
• Update README.md of docsy repo - NPM package: change version to 0.2.0 #961
• Release v0.2.0
  • Prepare docu and repo for release v0.2.0 #958, this will
    • update go.mod: docsy/dependencies need to point to v.0.2.0
    • update documentation: all links to 0.2.0-pre need to be changed to v.0.2.0
  • create tags v.0.2.0 and dependencies/v0.2.0
• docsy-example:
  • Update README to reflect use of docsy as a Hugo module docsy-example#168
  • Update example site to docsy theme v0.2.0 docsy-example#171
• Make release announcements --> move to Announce release 0.2.0 #966
  • Via discussions (done at the same time as the release)
  • Anywhere else?

References:

• Docsy as a Go module? #535
• Use NPM packages for Bootstrap and Font Awesome #870 - might this have an impact on / interfere with Hugo modules?