Live data from Hacker News

Moving from WordPress to Jekyll (and static site generators in general)

demandsphere.com

21–30 of 60 posts

Re: Moving from WordPress to Jekyll (and static site generators in general)

#21

Wordpress is better because it's easy to setup these days, can be fast if you enable caching, and has a comment system, which is a big deal if you want people to interact with your content. Other things like contact forms can easily be added. The CMS is also amazing. With SSGs, you have a few options for comments, like Disqus, but the ad-free version costs money, it's slower because it needs to load JS, and your comm…

SSG are over engineered? If anything it feels the opposite. Everything in a text git repo, templated, and a llm can understand and extend. Git branch to test new builds, merge to main deploys globally on cloudflare. Super fast load times, zero security issues to worry about, zero dependencies. Version control. Zip it up and take it wherever you want.

No server side things to worry about. It's super clean. Jekyll, css, js, GitHub and cloudflare is such a clean and refreshing setup.

Re: Moving from WordPress to Jekyll (and static site generators in general)

#22
I didn't want to hassle with migrating my WordPress blog, so now just deploy it to Github > Cloudflare Pages so it's served statically (fast + secure). It's free too, wrote a blog post on it a couple years back: https://gmays.com/how-to-host-wordpress-sites-free/

But these days any new site I build is on NextJS since coding agents make it a breeze.

Re: Moving from WordPress to Jekyll (and static site generators in general)

#23

Wordpress is better because it's easy to setup these days, can be fast if you enable caching, and has a comment system, which is a big deal if you want people to interact with your content. Other things like contact forms can easily be added. The CMS is also amazing. With SSGs, you have a few options for comments, like Disqus, but the ad-free version costs money, it's slower because it needs to load JS, and your comm…

The comment system bundled with Wordpress is not enough for "serious blogging", you'll need plugins to manage spam, allow users to use social accounts, etc. You'll also need plugins for caching. Oh, and you'll need plugins for SEO as well, because the core Wordpress doesn't handle the bare minimum of SEO and isn't flexible enough to allow you to do it yourself. And each plugin expands the attack surface to a system that's known for the persistent attacks, so you have to be constantly looking for updates and keeping everything update. Oh, but not everything, because there are breaking changes. And there are versions that introduce bugs or regressions.

But yeah, a bunch of html pages is over-engineering.

PS: you don't need to use Disqus if you don't want to, there are a myriad of free open-source alternatives you can self-host that will take a fraction of the maintenance work of self-hosting a Wordpress instance.

Re: Moving from WordPress to Jekyll (and static site generators in general)

#24
I did with mine too in 2021. Mine was 1000+ articles with even more comments. Luckily for me, I’ve already closed the comments. So, had to just throw them away. For the search, I tried Algolia but hit the limit. I’m with https://pagefind.app for now.

I wrote about my journey from WordPress to Jekyll at https://brajeshwar.com/2021/brajeshwar.com-2021/

Re: Moving from WordPress to Jekyll (and static site generators in general)

#26
I've been using ai coding tools in the last few months with static site generators. This is hugely empowering and completely obsoletes most CMS systems. Especially for more complex publication workflows.

I'm using hugo, not jekyll. But I don't think it matters which site generator you pick. The key point is using something that is code driven. And then have AI drive the code changes. Basically all routine site maintenance and updates is now controlled via agentic coding.

We use guard rails and skills to impose structure and process. This includes tone checks (and fixing), making sure audio transcriptions are in sync with articles, ensuring everything is tagged correctly, dealing with translations and approved lists of translations of key phrases, SEO checks and much more. I've been dialing in a lot of this in steps. You can start without most of this. But essentially a lot of manual work melts away when you get a bit structured on this. Like the article, we also use vector search embeddings. Our search actually uses the same model and runs it in the browser via web GPU. I also use it for related articles.

Also we've been experimenting with using reveal.js for presentations. Same principle. Forget things like Keynote, Canva, etc. Reveal.js is meant for programmers. But if you replace those with agents, non technical people can prompt together some really amazing decks. Replacing applications and UIs with code driven systems removes the need for those applications and UIs. And using AI to drive those code based systems removes the need for having developers in the loop. Our non programmer CEO who was a heavy Canva user is now doing decks and huge website updates this way now. Pretty scary actually. I don't think he'll use Canva again. I'm barely involved beyond setting up some basic plumbing. One party trick he likes is adapting decks to customers by integrating their house colors and visuals. Only takes pointing the AI at their website.

https://querylight.tryformation.com/ is a hugo demo site for the search capabilities. It hosts the documentation for the vector (and lexical) search library I use on our websites. The entire documentation site is managed as I describe above.

Re: Moving from WordPress to Jekyll (and static site generators in general)

#27

Wordpress is better because it's easy to setup these days, can be fast if you enable caching, and has a comment system, which is a big deal if you want people to interact with your content. Other things like contact forms can easily be added. The CMS is also amazing. With SSGs, you have a few options for comments, like Disqus, but the ad-free version costs money, it's slower because it needs to load JS, and your comm…

I moved my blog from WordPress to Jekyll a few years ago, and it's anything but an over-engineered system. I used WordPress for years, and it was overkill for a personal blog.

Re: Moving from WordPress to Jekyll (and static site generators in general)

#28
post #8

Been on the Jekyll bandwagon for a long time now; it's my go-to static site generator.

I love the idea and design it's just overwhelming for an idiot like me who isn't a web dev to spool one up on something like Amazon light sail. definitely going to Ai sledgehammer my websites over to this though, been way too long sitting on this project and I don't need to blog nonsense when my articles are markdown anyway.

Re: Moving from WordPress to Jekyll (and static site generators in general)

#29

I've been using ai coding tools in the last few months with static site generators. This is hugely empowering and completely obsoletes most CMS systems. Especially for more complex publication workflows. I'm using hugo, not jekyll. But I don't think it matters which site generator you pick. The key point is using something that is code driven. And then have AI drive the code changes. Basically all routine site mainte…

This is super interesting! Thanks for sharing. I’m wondering myself how to put up a site with usual product stuff, blog and manual.

The blog is running already on hugo on full llm automation but I had though it would not work for documentation (this is for non-techies so want something more product-manual -like and less SDK-docs flavour) or landing page that well.

So this is you company’s site and it’s on Hugo? https://formationxyz.com/

Re: Moving from WordPress to Jekyll (and static site generators in general)

#30

Wordpress is better because it's easy to setup these days, can be fast if you enable caching, and has a comment system, which is a big deal if you want people to interact with your content. Other things like contact forms can easily be added. The CMS is also amazing. With SSGs, you have a few options for comments, like Disqus, but the ad-free version costs money, it's slower because it needs to load JS, and your comm…

Counter-point: static sites are unhackable, require no maintenance and are free to host. Now that I've migrated the website for a local (volunteer) event, they will never have to worry about their site breaking on them again.

Multiply that by every nonprofit without tech knowledge and that's a lot of potential Jekyll fans.

Post reply on HN