ProcessWire VS Gatsby

Processwire is exactly what you want

I use ProcessWire for this kind of site; clients have always been super happy with it. If anything it's more intuitive than WordPress for the client -- all content is laid out in a tree view for them.

ProcessWire

For the ProcessWire project. I created this simple Inertia adapter. And also a sample ProcessWire + Svelte + Laravel Mix + Inertia project.

Build a technical framework (i use Processwire with some manual adjustments) on which I base my freelance projects on. this saves a lot of time during the development because I don´t have to start from scratch

This post could have been me, for when discovering ProcessWire (https://processwire.com/) after 10-ish years of Drupal (also trying out Joomla, Wordpress, Typo3... (well tried installing it at least) and perhaps a few others).

The main differences would be that in Processwire, you don't even need to install plugins, as all different types of displays are so easily created from scratch in the pure-PHP templates, using PW's extremely awesome jquery-like API for getting content (see the cheatsheet for an idea: https://cheatsheet.processwire.com/).

Repository: Gatsby

You can learn more about Gatsby from its official documentation

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.