-
Notifications
You must be signed in to change notification settings - Fork 820
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
Upgrade Hugo + Docsy to latest versions #1819
Comments
Code synatx highlighting might be a nice new feature: |
https://www.docsy.dev/docs/adding-content/lookandfeel/#diagrams-with-mermaid This could replace some of our dot and plantuml image generation, making the site simpler to update. |
Mark updated Hugo already: #2085 I'm going to look at upgrading docsy. |
Since I couldn't find any instructions on how to update docsy for the agones website, I'm going to add some notes about what I do here. Looking at https://www.docsy.dev/docs/updating/#update-your-docsy-clone there are two ways to update docsy depending on how it's installed. @markmandel said that in our case we do "a straight clone locally and vendor operation" and that "we may also have some local hacks in there (I think most I changed I submitted back to upstream, but good to keep an eye out just in case)" |
First try:
Next try:
Now I can diff the two directories and decide what to keep. |
Not quite sure if I was clear when we chatted -- but I would clone Docsy to a completely different directory, not try and do it in the Agones working folder. Sounds like you ended up in the same place 👍🏻 |
Once Hugo and/or Docsy can handle [email protected], let's upgrade both Docsy and Hugo to the latest versions.
Also just nice to be on the latest.
Context:
Originally posted by @markmandel in #1818 (comment)
The text was updated successfully, but these errors were encountered: