wp2static VS Gatsby

Download and Install WP2Static Plugin

> It is not actually that hard to run Wordpress securely. Stick to supported plugins and themes, and install security patches quickly when they are released.

Depending on your site's functionality, it may also be possible to run a static WP site:

* https://wordpress.org/plugins/simply-static/

* https://wp2static.com

You do all your regular updates via the CMS, but, instead of putting the dynamic site on the public Internet, you generate static files and point your public web server's HTML rootdir at those.

Also, for a bit more complex although richer in features workflow, you might try Wordpress with the Block Editor (or any page builder like Elementor) and the [WP2Static](https://github.com/WP2Static/wp2static) plugin, which allows you to turn a Wordpress site into a static one!

The closest "free" option I can think of is Oracle Cloud, but /r/oraclecloud shows plenty of horror stories in registration and maintaining an instance. If you don't actually need interactive features, WP2Static on your local instance to be deployed to Cloudflare Pages might work.

> Most WP sites should be static sites.

https://wordpress.org/plugins/simply-static/

https://wp2static.com

Depending on the site, ask yourself "How dynamic does it actually have to be?". Perhaps using the GUI to update the content, and then creating static files and serving those may be an option:

* https://wp2static.com

You could also use WordPress as a SSG with the WP2Static plugin — https://github.com/WP2Static/wp2static/

What is wrong with using Wordpress? I believe now one can get Wordpress to have 'static site' capabilities these days [0]

[0] https://wp2static.com/

The first time I started building static websites is when I discovered Gatsby. I built several projects using Gatsby and hosted it on Netlify free tier. It felt like a really robust architecture and I loved that it was free.

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.

While Next.js is a powerful framework for building server-rendered React applications, it's not the only option for developers looking to create high-performance websites. One notable alternative is Gatsby, a static site generator that leverages React and GraphQL.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

GatsbyjsCMS - Gatsby is the fast and flexible framework that makes building websites with any CMS, API, or database fun again. Build and deploy headless websites that drive more traffic, convert better, and earn more revenue!

GatsbyJS

Babel plugins are everywhere. From being used to remove unwanted exports from files in Gatsby to being used to disallow users from doing re-exports in Nextjs.

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

Flexibility : Developers have complete control over the frontend so they can use their preferred tools and frameworks like React, Next.js, Gatsby, or Remix.