-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Porting from docdock to hugo-theme-learn #348
Comments
(Apologies if there's a better place for this.) I was able to make some progress by upgrading my version of Hugo from 0.40 to 0.59. That got rid of the "function hugo not defined" error. Is there a minimum version number for Hugo that crept in along the way? |
Unfortunately Hugo has a little bit of a track-record of introducing backwards breaking changes in new versions. Thus, depending on the current development state of your Hugo project, your project might not work with either the newest version of Hugo - or a version that is too old. Also the author of this theme seems to have been inactive for a while now. May they are on a hiatus currently. |
I'm helping with maintenance but I've a habit of dropping by only every 2 or 3 months to blitz through the issues & merge requests and ship a release all in one go. As for versions of hugo supported... I don't keep close enough track of changes (breaking or not) to be able to offer a guarantee of supported versions with the theme. The community that use this theme have been very good at sending MRs which address hugo deprecations and errors. Generally speaking I would recommend using latest hugo at all times & ignore whatever your package manger is shipping you. Set up a test site where you can build against latest hugo and preview the changes before shipping your production site. p.s. we do that on this repo with netlify, all MRs have a full copy of the examplesite rendered and pushed to a staging URL |
Thanks for clarifying :). And I agree, that only ever the newest version should be considered. |
I have a site that's written and configure for the
docdock
theme, which I know is related rather closely to this theme. I'd like to switch over to this theme from it to try out some new features etc.Suggestions on any high level approaches to take? In reading things I see a new "chapter" structure which isn't in
docdock
.The text was updated successfully, but these errors were encountered: