Migrate to Hugo #818
Migrate to Hugo #818
Conversation
| 3. Install the necessary dependencies: `bundle install`. | ||
| 4. Build the site: `bundle exec jekyll build`. |
There was a problem hiding this comment.
I guess the readme needs to be updated as well
There was a problem hiding this comment.
Yes, I'll leave it as the last step
assets/css/anchor-link.css
Outdated
| max-width: 24px; | ||
| max-height: 24px; | ||
|
|
||
| & .anchored-link:hover { |
There was a problem hiding this comment.
CSS nesting is still not supported by all browsers. Do we have a preprocessor in place until that happens?
There was a problem hiding this comment.
It's supported by all major browsers, what other browsers should I look for?
There was a problem hiding this comment.
17% of browsers are still not supporting it, we can't really make the jump yet: https://caniuse.com/css-nesting
There was a problem hiding this comment.
Yeah somehow I thought it has 93% +
I've added postcss-preset-env with postcss to generate css compatible with all browsers :D
There was a problem hiding this comment.
Unfortunately that requires for us to use npm, and one of the reasons why we kept everything in jekyll/scss was to not add more dependencies. So if Hugo doesn't have anything native I thing you should revert the css nesting and leave it as is.
There was a problem hiding this comment.
I've reverted it :(
I really like using it, it's so much cleaner
Btw the archive generator and mirrorlist generator use javascript and currently it has 1 dependency to parse yaml, is that an issue? If so we could use json instead
Calinou
added
enhancement
topic:backend
|
@MichaelJRM is there a way we can chat? maybe discord (emi_cpl) or send me an email at [email protected] |
|
Is there something I can help with regarding this migration to Hugo? Is the migration to Hugo merely a suggestion or something with consensus?
Is that necessary for the migration? I would try to keep the scope small of this PR, and not do any translations yet. If the URLs and content are retained it's not necessary, right?
What does the Jekyll website provide? What changes?
What do you intend to change? Looking at the diff, wow, that's a lot of changes… |
|
I've been away for a while but I'll get back to this next week. |
|
@MichaelJRM sounds good! lets sync first, so we don't duplicate work or make it harder for you |
|
@MichaelJRM I've started testing things out and doing a Hugo build inside the current Jekyll site so we can slowly transition page by page. The main goal of this will be to bring i18n into the site, but instead of replacing all at once, I'll be focusing on individual pages first. Just wanted to loop you in just in case you are interested in helping out with this task. |
akien-mga
force-pushed
the
master
branch
2 times, most recently
from
e99f9b8 to
7bc695b
Compare
Migrated from Jekyll to Hugo, everything is 1:1 except for some creative liberties :D
There is still some stuff to finish, I would appreciate any feedback.
Major features include
To test make sure you have the latest version of Hugo
Run
make update-download-archiveto generate the Godot archive cache,make serveto serve the website andmake index-articlesto index all the articles.You can also just run
make buildandmake serve.Todo: