Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

demandsphere.com

Post reply on HN
Print view View original

41–50 of 60 posts

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

#41

Post by pdyc »

jillesvangurp wrote: post #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 mainte…

wow that looks beautiful. I want to migrate my hugo site to astro because astro is easier to manage and more friendly to local llm's than hugo but postponing it.

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

#42

Post by mickael-kerjean »

yoz-y wrote: post #40
mickael-kerjean wrote: post #32

Earlier quoted context omitted.

> This is hugely empowering and completely obsoletes most CMS systems. I went the other direction: instead of replacing the CMS, I open sourced a FUSE like layer [1] that mounts any backoffice system as a filesystem while the source of truth is in WordPress, Mysql, Postgres, .... Most backoffice systems map naturally to a file tree, so you mount them locally and let your agent read and write through that. In the POC…

Literally yesterday I was thinking of writing a FUSE layer to expose email as a folder structure, in Go. From a glance at you documentation I take it that I could just write a plugin for filestash ?

Exactly, just implement this interface: https://github.com/mickael-kerjean/filestash/blob/master/ser...

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

#43

Post by ThisNameIsTaken »

yoz-y wrote: post #40
mickael-kerjean wrote: post #32

Earlier quoted context omitted.

> This is hugely empowering and completely obsoletes most CMS systems. I went the other direction: instead of replacing the CMS, I open sourced a FUSE like layer [1] that mounts any backoffice system as a filesystem while the source of truth is in WordPress, Mysql, Postgres, .... Most backoffice systems map naturally to a file tree, so you mount them locally and let your agent read and write through that. In the POC…

Literally yesterday I was thinking of writing a FUSE layer to expose email as a folder structure, in Go. From a glance at you documentation I take it that I could just write a plugin for filestash ?

Like Maildir? Many mail clients support that format already.

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

#44

Post by iLoveOncall »

donohoe wrote: post #2

I don’t get it. Their setup is so much more complicated and limiting than what they had on Wordpress. I won’t argue with their reasons to move (which don’t stack up for me either but agree to disagree).

Yeah I tried using Hugo instead of WordPress for a brand new website, and the setup was incredibly more complicated and yet limited.

I was all for them until trying one, now I don't understand.

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

#45

Post by unixhero »

mc007 wrote: post #6

interesting, we went from classic CMS to Jekyll, then Hugo, then Astro and finally built our own CMS - for larger sets of content and sites. Fiddling with custom DSLs, templates, weird builds and tricks ... was just way too time consuming - unthinkable my wife would ever touch it or write an article in there :) Have a look at https://service.polymech.info/user/cgo/pages/poolypress-cms , agentic CMS, translates, creat…

What do you mean widget aware

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

#46

Post by link0ff »

gmays wrote: post #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.

Unfortunately, Cloudflare Pages are deprecated. While the existing pages will be supported for some time, for new projects the only option is Workers that is much more complicated to configure.

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

#47

Post by yoz-y »

ThisNameIsTaken wrote: post #43
yoz-y wrote: post #40

Earlier quoted context omitted.

Literally yesterday I was thinking of writing a FUSE layer to expose email as a folder structure, in Go. From a glance at you documentation I take it that I could just write a plugin for filestash ?

Like Maildir? Many mail clients support that format already.

Yes. From experience productivity tools are never good because either:

1. They are simplistic 2. They are too complex

If I want to get anything done I want to build my own system where nobody else has a say in how the thing should behave.

I’ve build my own workout app and journaling system because after trying a trillion none of them fit me.

Today it’s easy to build tailor made programs quickly so I’d rather use something I control end to end.

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

#48

Post by yoz-y »

mickael-kerjean wrote: post #42
yoz-y wrote: post #40

Earlier quoted context omitted.

Literally yesterday I was thinking of writing a FUSE layer to expose email as a folder structure, in Go. From a glance at you documentation I take it that I could just write a plugin for filestash ?

Exactly, just implement this interface: https://github.com/mickael-kerjean/filestash/blob/master/ser...

Perfect. I’ll have fun with this.

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

#49

Post by oliwarner »

I can't imagine picking Jekyll today.

I moved to Hugo after years of suffering long builds. Jekyll's stack complexity meant CI/CD was hard to implement and it just wasn't that fast. Hugo wasn't just fast, it had everything baked in. The only problem (back then) was the lack of useful feedback. It'd just build omitting half the site.

Now I use Astro. Simple to understand, none of the dark magicks that Hugo relies on to work, and Quick Enough™. It's well supported and it integrates with all the frontend/design tools I was already using.

Pagefind is stupidly easy to integrate. And it's what you probably ought to be using whatever your SSG. https://github.com/shishkin/astro-pagefind

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

#50

Post by jiggunjer »

jillesvangurp wrote: post #36
ribice wrote: post #33

Earlier quoted context omitted.

Could you use an open source CMS for non technical folks, i.e. Decap?

Probably; if it has an API you can probably get coding tools to use it. But the point of using agentic coding tools is that they are really good at working with code and files. And it tends to be a lot faster and easier. And you can build tests and browser tests around that as well. In my view, a CMS is intended for people doing stuff. If you transition that stuff to AI Agents, why keep the CMS around? And if AI does…

Because re-arranging pictures in a gallery using words is less efficient than dragging them around on a screen. CMS still wins for some stuff.

There's also a security aspect, e.g. interactive editing lets you input secrets you don't want an agent to have.

Post reply on HN