In practice
I have known WordPress for a long time: from my own earlier sites, which are no longer online, and from Woobiboo, a WooCommerce store that is still running. I no longer start new projects on it, because for speed, flexibility and SEO I prefer Next.js with Payload CMS. What remains is an existing site that only needs a visual refresh.
What is WordPress?
WordPress is an open-source content management system under the GPL licence. It runs on PHP and a MySQL or MariaDB database. You change the look with themes and add features with plugins.
WooCommerce adds a shop to it and is open source as well. WordPress has a built-in REST API, so its content can feed a separate application while editors keep the panel.
- Licence
- GPL version 2 or later
- Environment
- PHP with a MySQL or MariaDB database
- Extensions
- Themes and plugins
- API
- Built-in REST API
How I work with WordPress
With an existing WordPress site I start with a review, not with a decision to rewrite. I usually ask for the WordPress and PHP versions, the theme, the page builder and the plugins, because they decide what can stay. That step can be skipped when the site is being replaced, as I no longer prefer new WordPress sites.
State review
I list the plugins and check which ones really do something. Not every site needs replacing: the Woobiboo WooCommerce store is still running.
Keep, redesign or move
If the site works, it stays. When only the look changes, a new design is enough, as with Woobiboo. I propose a move to another tool, such as Payload CMS, when speed or custom logic limit me.
URLs and content
For a move to Next.js with Payload CMS I first list the URLs and content, and only then plan the redirects. Old URLs have to lead to the right places, because search position depends on it.
When it fits, and when it doesn't
When WordPress is enough, I say so plainly: I do not rewrite an existing site that only needs a visual refresh; a new one I start with Next.js and Payload CMS.
A good fit when
- An existing WordPress site that only needs a visual refresh.
- A working WooCommerce store that needs no new features.
- A small editorial site already on WordPress, edited by someone who knows the panel.
Not a fit when
- An application with its own logic: bookings, user accounts, a client panel.
- A site where Core Web Vitals should depend only on your own code.
- A project where nobody will keep the plugins and the theme updated.
When those limits apply to your site, I propose Next.js with Payload CMS, and Strapi as a second option for editors.
Why I choose something else today
Today I choose Next.js with Payload CMS, mainly for performance and SEO, with flexibility on top. Those are my reasons, not a rule for every site.
| Criterion | WordPress | Next.js |
|---|---|---|
| Editing content | Editor panel ready out of the box | Needs a separate CMS, such as Payload |
| Language and runtime | PHP with a MySQL or MariaDB database | React on a Node.js server |
| Extending it | Plugins and themes from a directory | Your own code and npm libraries |
| Access to content | Built-in REST API with JSON | Data from any source, on the server |
| Deployment | Hosting with PHP and a database | Node.js server, Docker or static export |
Stay on WordPress when
the site already runs on WordPress and you mostly need a visual refresh. Rewriting it in Next.js then costs more than it gives.
Choose Next.js with Payload CMS when
Next.js with Payload CMS should give a faster site, your own logic and full control over URLs and data. You pay with a developer writing new features instead of someone installing a plugin.
The Woobiboo store on WordPress and WooCommerce is still running, and another designer has since redone its look, so I do not rewrite a working site on principle.
Frequently asked questions
Is your WordPress site not doing what it should?
Tell me what the site does today and what gets in the way. I will say whether a fix, a new design or a move to another tool is enough.