-
Notifications
You must be signed in to change notification settings - Fork 888
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docsy as a Hugo module #849
Comments
@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? |
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! 🎉 |
Update: we should be wrapping up the docs this week, and getting the next release out soon after that. |
@deining - could you do the |
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. |
@deining - all three PRs have been merged (though not strictly in the order you suggested, sorry -- due to a hick up on my side).
That seems reasonable to me. |
@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. |
Last, not directly related item was moved to #966. All done here 🎉, so closing. |
Done. Added tag |
@deining et all, let's use this issue to track tasks that are needed to support use of Docsy as a Hugo module.
README.md
of docsy repo - NPM package: change version to 0.2.0 #961References:
The text was updated successfully, but these errors were encountered: