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

51–60 of 60 posts

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

#51

Post by kentonv »

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

Hey, sorry this has been a confusing transition.

You can actually still create new Pages projects, but it is de-emphasized in the UI in favor of Workers.

We've done a lot of work to make static sites on Workers just as easy to configure as Pages was. Have you tried it lately? Would love to hear what aspects you feel are still more complicated than Pages.

Just to be clear, we will not break existing sites using Pages. We will either auto-migrate them to Workers once we have all the tools in place to do so, or we'll keep supporting Pages forever.

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

#52

Post by link0ff »

kentonv wrote: post #51
link0ff wrote: post #46

Earlier quoted context omitted.

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.

Hey, sorry this has been a confusing transition. You can actually still create new Pages projects, but it is de-emphasized in the UI in favor of Workers. We've done a lot of work to make static sites on Workers just as easy to configure as Pages was. Have you tried it lately? Would love to hear what aspects you feel are still more complicated than Pages. Just to be clear, we will not break existing sites using Pages.…

Nice to hear! I haven’t tried it since last summer. What I tried to do was to deploy Jekyll from GitHub to Pages, and the only option I see was to deploy to Workers, but I couldn't find the documentation for doing this on Workers. Maybe this was improved since last summer. I'll try again.

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

#53

Post by QuiDortDine »

noeltock wrote: post #39
QuiDortDine wrote: post #30

Earlier quoted context omitted.

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.

The nonprofit world is dominated by WordPress, not sure that'll change in the near future.

I'm not vouching against WordPress per se, just wish people would use the best tool for the job at hand rather than the one tool they know. Sometimes that's Jekyll and sometimes you need comments.

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

#54

Post by shlewis »

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

Hugo is not Wordpress alternative, really. It's an static site generator. Wordpress is not static. Trying to do things what only Wordpress can do will introduce a lot of complexity and often will just not work.

If all you need is a, well, static website without forms or such, Hugo is an easy winner.

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

#55

Post by mc007 »

unixhero wrote: post #45
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

Widgets as gallery, filebrowser, Mardkown, images, hero-banner ... are useful in many ways, easier authoring but also rendering a page as email, PDF. You can give LLMs skills on how to use those, eg: "create amazon product layout for all my products" (requires of course extra tools for content introspection and manipulation), seems to work pretty good.

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

#57

Post by jbverschoor »

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 ?

Or just run BeOS

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

#58

Post by iLoveOncall »

shlewis wrote: post #54
iLoveOncall wrote: post #44

Earlier quoted context omitted.

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.

Hugo is not Wordpress alternative, really. It's an static site generator. Wordpress is not static. Trying to do things what only Wordpress can do will introduce a lot of complexity and often will just not work. If all you need is a, well, static website without forms or such, Hugo is an easy winner.

That's exactly what I tried to use it for: a simple website with blog posts and a timeline, everything read-only.

It's a pain in the ass to use.

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

#59

Post by shlewis »

iLoveOncall wrote: post #58
shlewis wrote: post #54

Earlier quoted context omitted.

Hugo is not Wordpress alternative, really. It's an static site generator. Wordpress is not static. Trying to do things what only Wordpress can do will introduce a lot of complexity and often will just not work. If all you need is a, well, static website without forms or such, Hugo is an easy winner.

That's exactly what I tried to use it for: a simple website with blog posts and a timeline, everything read-only. It's a pain in the ass to use.

I get the complex part: it's not as easy as Wp, but what makes it _limited_ when all you needed was a static website?

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

#60

Post by alwillis »

lachlanj wrote: post #25
alwillis wrote: post #8

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

Have you ever been tempted to look at others like Hugo? Or do you get what you need from Jekyll?

> Have you ever been tempted to look at others like Hugo?

Not really; I didn't see any must-have features that I couldn't live without.

Post reply on HN