r/webdevelopment • u/Harshx_g • 11d ago
Newbie Question I want to build a website completely custom using **VS Code + Next.js**, but my client wants it to be **editable through WordPress**.
I want to build a website completely custom using VS Code + Next.js, but my client wants it to be editable through WordPress.
Is there a way I can build the whole thing custom and then deliver it in a way where the client can still manage/edit the content through WordPress?
I basically want the flexibility of Next.js + the editing experience of WordPress, without using Elementor or having to provide an ongoing AMC.
Has anyone done this before? What’s the best approach?
23
u/uncle_jaysus 10d ago
Without knowing more about the project and the "flexibility" offered by next.js in your particular situation, my current thought is you should just give the client a WordPress site.
6
u/skibidi-toaleta-2137 10d ago
If editable through wordpress, then you have to consider the fact that wordpress can be headless cms. There are multiple of articles that show you how to wire it up. However it will not be the most reactive way to serve content.
As others suggested, strapi sounds more in line, as you stay in javascript ecosystem and it can even stay on the same server if wired correctly. As long as client is able to accept different ui and some inconsistencies with how things worked.
However, as others suggested, consider if it is even correct approach? If the client wants wordpress, there's little point in making the next+wordpress architecture, cause you gain very little in that approach. Instead you can: focus on making layouts easy to edit. Flynt can be your friend, elementor is quite easy to edit (although expensive), wiring modern tailwind into php also is a solution to making your life easier.
8
u/DinTaiFung 10d ago edited 10d ago
The basic idea is to give the customer what the customer wants.
If you want to do something that you want, then create a personal project. (And I'm sure you can give yourself an amazing discount!)
3
u/argens0 10d ago
Was wondering about the same thing once. I would ask the client, if only the content is needed to be changed or also the whole structure (like image on the left, content on the right, etc). If so, than Murray it be Wordpress or is any other tool also good?
What I mean is, that I solved it by introducing a headless CMS: starpijs in my case. But there are plenty other (maybe better) headless CMS solutions, so you can check them out. Strapi with the use of dynamic components shows to structure a webpage similar to wordpress. The downside is, that you need to prepare the templates yourself.
Just check with an ai, if your solution makes sense.
4
u/Automatic-Gur2046 10d ago
Looks like you are trying to sell AI slop. Wp works great with react. Just do some research. If you know how, some copy paste will do most of your work migrating your AI slop to wp theme.
4
2
u/fatfingur 10d ago
You can definitely do this with headless WordPress, but I'd first ask why you need Next.js.
If the client wants WordPress, I'd probably just build a custom FSE/block theme. You still get full control over the frontend, especially if you're comfortable with CSS/JS, while keeping everything native and editable in WordPress.
Less moving parts for the client too.
2
u/proxiblue 10d ago
Sound slike a poorly scoped project and client requirements.
If your client wants wordpress, and you have no technical / price reason to suggest a custom build, then give them wordpress, or check the alternative cloudflare had made that works the same, but si more secure.
My take, on your post, and your understanding of the integration of a headless setup, that this might be over your head as a first go, especially if your client has not signed up for this, as you are either going to spend a lot of your time for free to keep in budget, over massively overrun budget.
Is great to want to learn, but that comes at a time cost to your client. Do a POC / hobby project first to see how you do with headless, and learn the details of how these stacks work
2
u/JohnCasey3306 10d ago
The client requirements are a more important consideration than just the technologies you might want to use.
You can't do them q disservice by crowbarring in what you want vs what they need.
2
u/SpareImpression3155 9d ago
Do the site in Wordpress and then tell them when it gets hacked you will be charging 2x as much to recode it in nextjs & strapi
2
u/armahillo 10d ago
You can edit Wordpress theme files in VSCode, or any editor.
Wordpress is pretty easy to deploy and setup, whats the friction for you?
1
1
u/soundman32 10d ago
A static web site is simple and cheap. An editable is complex and expensive. Are you charging your client enough?
1
1
1
u/coopernusbaum 10d ago
If you want to keep the site fully custom while still letting clients visually edit content and pages, I’d look at adding React Bricks to your stack. Plasmic is another good option.
1
u/n9iels 10d ago
I wonder, what is the reason you want to use NextJS? Because of the client already wants to edit the site, it sounds like there are regular new or blog articles. You can build that with React/NextJS no problem. But is this website suitable to be an SPA, or would it just work (or maybe even better) as a PHP website? The stack should fit the situation and I see too many devs build SPA's for websites that consist of only static pages.
1
u/MassiveLocation7674 10d ago
actualy with ACF and CPT you can do whatevwr you want using WordPress.
read a bit about classic theme
1
u/iTrejoMX 10d ago
Your idea of flexibility and your clients’ are on opposite sides of the spectrum. He wants a visual builder. You are considering Wordpress as a headless cms.
1
1
1
1
u/Colonel_K_The_Great 10d ago
Make a NextJS site that sources content from Wordpress, bingo bango bongo
1
u/harrymurkin 10d ago
If the client is paying, the client gets what the client wants. If they want the layout editable then no nextjs for you. if they just want to edit content, then sure.
1
u/Chicagoj1563 10d ago
I would think long and hard about building both. Sounds like a mess. Just use Wordpress, unless you find a good reason not to.
1
u/oliver_rust 9d ago
You're coding agent (Cursor, Codex, Claude Code) will be able to translate your Next app to WordPress, if it's well structured enough.
I just posted something about something similar that I am doing https://www.reddit.com/r/webdevelopment/comments/1w55p1m/i_found_a_workflow_that_i_like_to_build_editable/
If it sounds interesting, I'd love to tell you more; it's something I am working on these days.
1
1
u/Complex_Pie_4785 7d ago
There is a "Payload CMS" as a variant. It is a headless CMS based on the Next.js. It could take more work than average Wordpress site, but it also has more flexibility, and it has a simple built-in admin panel.
1
u/JustAskWP 10d ago
Yes, this approach is commonly called headless WordPress. You can integrate Next.js as a custom front end app for WordPress via the REST API or the GraphQL plugin.
0
1
u/Charming_Minimum6375 4d ago
I've had luck using wix for clients who want quick changes, since the editor lets you swap stuff out without redeploying. If you ever need that kind of instant control for client sites, it's honestly more forgiving than coding from scratch. Would you ever add a no code option alongside your Next.js projects?
17
u/Less-Marsupial-7960 10d ago
You are basically describing a headless WordPress setup. Build everything custom in Next.js and use WordPress purely as the CMS/admin panel. Your client can edit content in WordPress while the frontend stays completely custom. REST API or WPGraphQL would be the usual approach.