Hugo VS Jekyll

I have migrated from Jekyll to Hugo for my own website, but the whole Hugo project is just weird. It took me like a year to migrate my simple website because of all the different paper cuts that drained my will to work on it.

You are only able to only use partials in HTML pages and shortcodes in Markdown pages. Why? They use 2 different syntax, so the best you can do is awkwardly wrap a partial in a shortcode. What's the point? They serve basically the same purpose.

Want to set up RSS? Oh yeah, for some reason by default it will not show full content in your feed reader, instead only a small extract with the only way to fix it is by making your own template[1]. But wait, why are we using RSS instead of Atom? Who knows, but if you want to use Atom, you have to use your template and insert some stuff to your config.

Also don't look at the bug tracker, that thing is frustrates me to no end.

You of course have the everyone's favourite Stalebot that you might have noticed in my previous link, but if you look at older issues, you will see the maintainer self-botting as a Stalebot[2][3] for some reason.

You will also see the maintainer moving issues between milestones for years with no end in sight[4].

Changelogs can sometimes feel a bit, odd too:

> but also a big shoutout to @dependabot[bot], […] for their ongoing contributions.

And commit messages sometimes are just… a bit too long[5] (it is truncated by GitHub, you can append .patch to see the full message).

Their documentation is awful to read too[6]. Oh and the templating engine? Yeah, not documented at all. Also the quick start guide will tell you to git clone some random theme, but I don't want my website to look like someone's, I want to write my own styles and have my own structure, but they don't really tell you anywhere how you should go about it. Because of it, I would search GitHub to sometimes find answers on how to do some stuff, but you would quickly find that most people had no idea how to actually use it. For example you can find a lot of people making opening and ending partials to have a common page layout instead of actually using the built-in Hugo layouts.

So why have I bothered switching? i18n support, so far out of all SSG I tried, Hugo does it in the least painful way.

[1]: https://github.com/gohugoio/hugo/issues/4071

[2]: https://github.com/gohugoio/hugo/issues/385#issuecomment-283...

[3]: https://github.com/gohugoio/hugo/issues/1035#issuecomment-28...

[4]: https://github.com/gohugoio/hugo/issues/448

[5]: https://github.com/gohugoio/hugo/commit/6dbde8d731f221b027c0...

[6]: https://news.ycombinator.com/item?id=30527884

That issue should have been closed. This was resolved in Hugo 112. https://github.com/gohugoio/hugo/releases/tag/v0.112.0

The fact that Hugo still doesn't play nicely with Tailwind 3 (2 years after T3 was released) is a real pain point.

I gave up on this ever being fixed quite a while back, but still check on the issue [1] every now and then. Seems like the only activity these days is bep bumping the milestone every month.

[1]: https://github.com/gohugoio/hugo/issues/8343

For creating a static site I recommend Hugo. In short this is because it is popular, well-supported, fast, and allows you to get up and running quickly with premade templates.

I use Hugo. Creating templates was admittedly not easy at first. But as soon as you understand it, you can implement a lot with it.

Export content written in Notion to markdown, compatible for [Hugo](https://gohugo.io/) blog.

You can use Notion as a CMS in order to author, edit, and manage all your content while leverage the power of Hugo in order to serve the content statically on your blog site. This lets you leverage the best of both worlds - powerful and expressive UX of Notion for authoring along with speed and pre-built feature rich themes from Hugo for personal blog site.

The package ships with a script in order to export content from Notion in a compatible format.

```

After using Hugo on an Arch-based Linux machine for a while, I realized that a clean, up-to-date, and well-maintained Hugo package is missing. I found/used the following existing packages:

Something like Hugo might be of interest to you.

I do the same thing, via hugo - I can choose to use markdown, HTML, make use of the templates, or ignore the template and just output raw text or HTML.

Yes, it's Markdown and I use https://jekyllrb.com with the theme "jekyll-theme-hacker" to generate the site. I quite like how simple it is.

Context is everything. In the context of Jekyll, all of this is certainly a useful feature: this is not code that needs to be re-used or maintained in the same way as your Rails project has to be.

As always, engage your brain before doing anything and you don't need to use these features, but it gives you the tools to do "smart things" that Go simply can't. This, among other things, means that Jekyll will scale reasonably well with your website as your needs grow, without having to add features to Jekyll core, using your own fork of Jekyll, or switching to something completely different.

For example, I have a little plugin[1] to work around a bug[2] and to skip the hard-coded requirement to have a date in the filename.[3] Is this ugly? Yes. Is this fine to generate a relatively simple personal website? Also yes.

[1]: https://github.com/arp242/arp242.net/blob/master/_plugins/no...

[2]: https://github.com/jekyll/jekyll/issues/8707

[3]: https://stackoverflow.com/a/68287682/660921

Jekyll is a static site generator. It takes text written in your favorite markup language and uses layouts to create a static website. You can tweak the site’s look and feel, URLs, the data displayed on the page, and more.

I'm using bridgetown because I like sitting on the bleeding edge, its basically a newer Jekyll which I would recommend checking out too. Bridgetown has a great modern dev experience but its missing some of the ecosystem from Jekyll. Not a problem for me because I'm really comfortable with Ruby.

Takodje, ako nisi cuo za Jekyll, baci pogled. Ima vec brda Themes tako da mozes da customizujes nesto za svoje potrebe. Generalno se to koristi za GitHub pages.

If you want to have a different UI or your blog to look in a very specific way I recommend using Jekyll or Bridgetown.

I use Jekyll to build HTML from Asciidoc. To generate links, Jekyll uses two configuration parameters:

If I wanted to post a simple website today I would look into Jekyll. There are a ton of articles and answers to common questions etc. It itself is written in Ruby but using it will not likely help you to learn Ruby. One-step in the direction of learning Ruby and getting a simple website could be Bridgetown. This will start you down a path of learning Ruby and not Rails. We use Bridgetown for our company site at Flagrant.

The other option is to have your own custom website either by hosting your own blogging platform such as WordPress, Ghost or by setting up a static website with Hugo, Gatsby or Jekyll.