ENATIV Logo
ENATIV
Back
© 2026 ENATIV
ProjectsServicesKnowledge hubContact
contact@enativ.pl
  1. Knowledge hub
  2. ›
  3. CMS & content
  4. ›
  5. WordPress

WordPress

An open-source PHP CMS with themes and plugins; a small editorial site can still run on it.

CMS & contentUsed 2014–2019 · Featured project: Woobiboo

Category
CMS & content
Used
2014–2019
Featured project
Woobiboo

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.

  1. 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.

  2. 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.

  3. 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.

WordPress and Next.js compared
CriterionWordPressNext.js
Editing contentEditor panel ready out of the boxNeeds a separate CMS, such as Payload
Language and runtimePHP with a MySQL or MariaDB databaseReact on a Node.js server
Extending itPlugins and themes from a directoryYour own code and npm libraries
Access to contentBuilt-in REST API with JSONData from any source, on the server
DeploymentHosting with PHP and a databaseNode.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

For an existing site that only needs a visual refresh, yes. A new site, and an application with accounts, bookings or its own logic, I start today with Next.js and Payload CMS. That is my opinion, not a ranking of tools, so on a real project I count what actually hurts: speed or plugin limits.
No, if it works and does not hold back sales. Woobiboo is a WooCommerce store that keeps running after a visual redesign. I propose a replacement only when speed or custom features really hold the store back, not because WordPress went out of fashion.
There is no guarantee, but the risk can be reduced. Before a migration I list the URLs and plan redirects from old to new, and I carry the content over with its headings. After launch I check in Google Search Console that the old URLs work.
Plugins do not carry over by themselves, because they work only inside WordPress. So I start from a list of the features the site really uses and pick code or an outside service for each. Only that list shows the scope of the work.

On this page

  • In practice
  • What is WordPress?
  • How I work with WordPress
  • When it fits, and when it doesn't
  • Why I choose something else today
  • Frequently asked questions

Related topics

  • WordPress
  • Next.js
  • Payload CMS
  • Strapi
  • Core Web Vitals
  • Shopify

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.

Describe your projectSee Woobiboo