Replies: 3 comments 14 replies
-
|
I must admit that there are no clear advises just the hint to https://mcshelby.github.io/hugo-theme-relearn/configuration/customization/designs/index.html in the release notes. I've taken a peak in your repo and I think (haven't tested it) you have to change as follows:
|
Beta Was this translation helpful? Give feedback.
-
|
ah. i tested the first part ( |
Beta Was this translation helpful? Give feedback.
-
|
hmmm. there seems to be more. did also the second point, and now hugo is yelling at me. it searches just in the relearn-theme location, but not also in my "theme" where the archetypes are defined (as it did before). seems, my config needs some changes, too. |
Beta Was this translation helpful? Give feedback.
-
|
@McShelby so i copied all my archetypes into the main theme folder (i.e. the folder where relearn is 'installed'). now hugo does find my archetypes, and i get a lot of errors of this kind: something in the format of the archetypes seems to have changed, too? |
Beta Was this translation helpful? Give feedback.
-
|
I'll take a look into it, this evening Also, there may be some outcome for the docs. |
Beta Was this translation helpful? Give feedback.
-
|
No rush! I'm in the middle of term, and this might need some major adjustments on my side - I won't be able to address that for a few months. |
Beta Was this translation helpful? Give feedback.
-
|
I just gave up upgrading at all at some point, i guess it was 5.23.2. |
Beta Was this translation helpful? Give feedback.
-
|
Personally I also prefer incremental upgrades. In case you are far behind, it can be helpful to not upgrade to the latest version in one swoop but step by step to versions in between. This may end in a bit more work but can be easily be partioned in more digestable chunks. The overall idea for many theme changes is to make everything configurable. So ideally you as a user would be in no need to touch any partials but solve any customization by configuration. If you can not achieve your goals by configuration, feel free to post an issue. |
Beta Was this translation helpful? Give feedback.
-
|
But still, I tend to agree with @zeitgen. Particularly in the Hugo ecosystem, I've spent a frustrating amount of time over the years just to make the jump from one version to the next. There are simply too many variables in the game and both Hugo and the themes of course develop according to the ideas of the respective maintainers, and then my own customisations also enter the picture - it quickly takes a lot of time for me as a user to get my own project up and running again. To be honest, I'm pondering whether and how I can remove some of the variables from the equation. At the moment, I need to keep four juggling balls in the air at the same time: Hugo, the theme, my customisations and, of course, my content together with the configuration. I am looking for a tool where I only have to maintain my content and where I don't have to worry about the rest. Docsify and LiaScript seem to be strong contenders, but they have serious shortcomings compared to the Relearn theme (given my use case). So, for now I'm stuck with Hugo+Relearn+customisations and need to check from version to version to discover which things stopped working this time. |
Beta Was this translation helpful? Give feedback.
-
|
On the upside: I don't expect the themes structure to change that drastically in the future as with the past releases. It is now in a pretty good shape and complies to Hugo's best practices. I agree, I have had my fair share adding to the upgrade pain with some clumsy implementation descisions in the first year of the fork. Those were finally removed with version 7.x. We all learn as we move along. And for Docsify, LiaScript or any other solution: The gras is always greener on the other side. 😄 From 25+ years experience in software development I doubt that there are fewer hassle when upgrading those projects. They may only occur fewer times due to slower release cycles (which can be pretty fast paced with Hugo and the theme) But don't get me wrong, I don't want to sound self-convinced. I hear you! |
Beta Was this translation helpful? Give feedback.
-
|
Don't get me wrong - your theme is awesome and you're doing a great job! For me it's mainly Hugo with a combination of being somewhat poorly documented and moving at great pace and me having lots of documents to maintain. Things tend to break too often in the release cycle. |
Beta Was this translation helpful? Give feedback.
-
|
I can only second @cagix: the theme is a lifesaver and literally gives me a job now =) and i'm happy we share some common ground here. |
Beta Was this translation helpful? Give feedback.
-
|
In #980 I have greatly expanded the documentation for output formats and page designs (formerly known as archetypes) and included migration notes. The migration instructions are linked from the releasenotes of 7.0.0. Give it a try! Feedback welcome! @cagix I still haven't tested those instructions with your repo. So there might be coming some additions after I gained insights about your installation. |
Beta Was this translation helpful? Give feedback.
-
|
@McShelby thx a lot! after the exams end of january i'll have a look and give it a try. happy new year 🥳 |
Beta Was this translation helpful? Give feedback.
-
|
Once you are working on this again, could you create a reproducible example? I am struggling with the (at least for me) rather complex setup of your installation. |
Beta Was this translation helpful? Give feedback.
-
Thank you very much for your great work on this theme. I've been using 6.4.1 up to now and after upgrading to 7.0.0 my previous archetypes no longer work, probably some other things are not working either. I see the indication of breaking changes in the release notes, but I can't really figure out what I need to adjust. Can you please provide guidance on what needs to be changed for the new version?
Beta Was this translation helpful? Give feedback.
All reactions