I sometimes wonder how much energy (and security problems) could be saved when many switch from WordPress to static site generators.

@jwildeboer I've thought about it. What's your favorite static site generator?

@Joshholden but don’t ask me how I migrated my 10 years of WordPress over. I don’t remember how :) But it’s all there. Using the old URLs too :)

@jwildeboer I’m a little intimidated by the GitHub side of Jekyll, but will research it a bit more.

@jwildeboer @Joshholden I'm currently plodding through my 15 years of blogger content over to Jekyll and this project is taking a LONG time.

@jwildeboer I am in the midst of converting my drupal blog to pelican. It is taking so much time and effort but I think it will be worth it in terms of hosting costs and maintenance. I took a strange route; drupal -> wordpress -> pelican. It wasn't as smooth as I hoped unfortunately.

@jwildeboer recently switched my own site from wordpress to static html with pelican :D

@jwildeboer I have 22 years of personal blog posts I want to move to a static site generator. I have a lot of work ahead of me to accomplish this.

@jwildeboer To alien for many users (content creators).

Let's be honest, the content creation interface is the unique selling feature of WordPress, not what it presents to the readers.

With static content generators, the workflow needs to be understood, and if you have multiple editors you again need say git and a pipeline runner that pushes it to the external site. Again, exposing something to the big net. Even if it is only a project on github/gitlab/bitbucket.

Sign in to participate in the conversation

Mastodon instance for people with Wildeboer as their last name