Skip to content
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

Move from Jekyll to Hugo #148

Open
mauvehed opened this issue Feb 9, 2023 · 5 comments
Open

Move from Jekyll to Hugo #148

mauvehed opened this issue Feb 9, 2023 · 5 comments

Comments

@mauvehed
Copy link
Member

mauvehed commented Feb 9, 2023

Let's get off Jekyll as an opportunity to update and rebuild a bunch of stuff (and find a less suck theme), using Hugo.

@todb
Copy link
Contributor

todb commented Jun 3, 2023

Related, just ran a fresh install of Jekyll and got a couple post-install messages from the gem bundle:

Post-install message from sass:

Ruby Sass has reached end-of-life and should no longer be used.

* If you use Sass as a command-line tool, we recommend using Dart Sass, the new
  primary implementation: https://sass-lang.com/install

* If you use Sass as a plug-in for a Ruby web framework, we recommend using the
  sassc gem: https://github.com/sass/sassc-ruby#readme

* For more details, please refer to the Sass blog:
  https://sass-lang.com/blog/posts/7828841

Post-install message from html-pipeline:
-------------------------------------------------
Thank you for installing html-pipeline!
You must bundle Filter gem dependencies.
See html-pipeline README.md for more details.
https://github.com/jch/html-pipeline#dependencies
-------------------------------------------------
Post-install message from rubyzip:
RubyZip 3.0 is coming!
**********************

The public API of some Rubyzip classes has been modernized to use named
parameters for optional arguments. Please check your usage of the
following classes:
  * `Zip::File`
  * `Zip::Entry`
  * `Zip::InputStream`
  * `Zip::OutputStream`

Please ensure that your Gemfiles and .gemspecs are suitably restrictive
to avoid an unexpected breakage when 3.0 is released (e.g. ~> 2.3.0).
See https://github.com/rubyzip/rubyzip for details. The Changelog also
lists other enhancements and bugfixes that have been implemented since
version 2.3.0.

So yeah. This Sass dep is good enough reason by itself to move. No idea if there are security implications, but the blog post mentioned, https://sass-lang.com/blog/posts/7828841, is 404'ed now. Maybe it's abandonware?

@todb todb mentioned this issue Jun 3, 2023
@mauvehed
Copy link
Member Author

mauvehed commented Jun 3, 2023

Is that a general warning for anyone using the old "ruby sass" or do we have a dependency somewhere that actually uses it?

@todb
Copy link
Contributor

todb commented Jun 4, 2023

Got me -- it comes in with the Jekyll bundle. Maybe it's just for local deploy/testing?

@todb
Copy link
Contributor

todb commented Feb 3, 2024

Still want to explore this. Someday.

@todb
Copy link
Contributor

todb commented Jun 2, 2024

There's like a million billion themes for Jekyll these days, but I'll be derped if I can figure out how to easily migrate from one to the other.

There's still plenty of reason to move off of Jekyll, but the layout seems significantly less sucky now, especially once #182 lands that fixes up some minor annoyances.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants