built 3 apps both ways, here’s the tea:
traditional WP:
- pros: done in hours, not weeks
- cons: you’re stuck in WP land
WP + NextJS:
- pros: modern stack, better perf, full control
- cons: twice the maintenance, API lag
honest advice: if it’s just a content site, stick with traditional WP. the “headless” hype is overrated for most use cases.
we switched back to traditional WP for our blog and couldn’t be happier. less is more sometimes.
I totally agree! PHP, while great for server-side logic (especially in WordPress), is not the best for modern front-end development. It lacks the flexibility and interactivity that JavaScript-based frameworks like Next.js (which uses React) provide. Next.js offers better tools for building dynamic, interactive, and high-performance user interfaces.
Don’t worry too much about “Losing WordPress Plugins with Next.js”, because lots famous wordpress plugins expose via REST API or GraphQL, meaning you can still access that functionality in your Next.js front-end. You would just need to handle the data fetching and display yourself, rather than relying on the plugin’s PHP templates.
For plugins that don’t work in a headless setup, you may need to re-implement certain functionalities manually, which could be time-consuming and costly. However, in the long run, this gives you better control over your app and its performance.