Convert site to Hugo #112
Convert site to Hugo #112
Conversation
As part of nottinghamdigital#98, we decided that we wanted to replace the single HTML file with a static site generator. This allows for easier adding/changing of content and theme, as currently the setup of the site will make it a little difficult to change the structure of the site in the future, and it also makes it easier for folks to contribute changes to the events on the site. We've decided to use Hugo, as a lightweight solution that only requires a single download to get it working. To make this work and automagically deploy on merges, we need to use GitHub Actions. We no longer need anything Gulp/Node related, as Hugo can minify our source for us, so we can remove those references. Closes nottinghamdigital#98.
It appears that this link has been broken for some time - we should fix it so clients respecting the value can use it.
|
A quick note I forgot to mention - we'll need to tweak the way that GitHub pages is set up for this project before this is merged. Please see https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-first-deployment-with-github_token |
|
what's the process for local development ? do we need to updte readme and contributing guides? |
|
Sorry yes that's a very good point! Regarding local dev, unless folks are making more involved changes, don't necessarily need Hugo, as they can just contribute a new event, but I'll add the details in. In terms of contributing, I'd had a look at |
|
Hi @sdh100shaun sorry, I'm away at the moment, and not getting much time to try this out - happy to go ahead with it if it runs OK for you, but a couple of questions - is it obvious how to add new events, and are there dev instructions for build and deploy (git tokens etc)? |
|
I have pulled down will look at this @jamietanna is there to be instructions for updating? |
|
What do you mean sorry? |
Have applied hacktoberfest accepted as this is the direction we want to go - need to sort some merge conflicts then good to go |
As part of #98, we decided that we wanted to replace the single HTML
file with a static site generator.
This allows for easier adding/changing of content and theme, as
currently the setup of the site will make it a little difficult to
change the structure of the site in the future, and it also makes it
easier for folks to contribute changes to the events on the site.
We've decided to use Hugo, as a lightweight solution that only requires
a single download to get it working.
To make this work and automagically deploy on merges, we need to use
GitHub Actions.
We no longer need anything Gulp/Node related, as Hugo can minify our
source for us, so we can remove those references.
Closes #98.