Docsy as a Hugo module

[chalin]

@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?

[chalin]

@deining, you mention that this feature is ready on the feature-hugo-module branch. I'd like for our users (myself included) to test use of docsy from that branch. I'll test it out for projects using submodules, can someone else test it out via Hugo Modules?

[chalin]

Ok, I've tested the feature-hugo-module branch on a project using docsy via submodules and I'm glad to confirm that nothing broke! 🎉

[chalin]

Update: we should be wrapping up the docs this week, and getting the next release out soon after that.

[chalin]

@deining - could you do the docsy-example updates (see the opening comment)?

[deining]

@deining - could you do the docsy-example updates

For these updates, we have to merge #170, #172 and #171, with ideally PR 171 being the last one merged. All 3 PRs were authored by me, and merging his own PRs has a smell. @chalin, can you please review and merge these PRs? Thanks.
Afterwards, we have to decide whether we want to apply tags to the example site as well. I would tend to say yes, and would chose identical tag v0.2.0 in both for docsy theme and for the example site.

[chalin]

@deining - all three PRs have been merged (though not strictly in the order you suggested, sorry -- due to a hick up on my side).

Afterwards, we have to decide whether we want to apply tags to the example site as well. I would tend to say yes, and would chose identical tag v0.2.0 in both for docsy theme and for the example site.

That seems reasonable to me.

[chalin]

@deining - just to be clear: I'm ok if you ahead and setup the tags on the example repo. If you'd prefer that I do it, let me know.

[chalin]

Last, not directly related item was moved to #966. All done here 🎉, so closing.

[deining]

@deining - just to be clear: I'm ok if you ahead and setup the tags on the example repo.

Done. Added tag v0.2.0 to the docsy-example repo and created a release from that tag. Added archive files for go-less installation and for the _vendor directory itself to the release. Wondering if we should add these _vendor archives to the 0.2.0 release of docsy itself (I see added value from this).