Good afternoon everyone, I’m writing in particular to those using the **Next.js – WordPress headless** stack.
I do WordPress / Laravel development from designer layouts but have worked on React – Next.js projects in the past. I have a small agency with about 100 or so WordPress projects under maintenance and about 10 new projects a year.
Recently I’ve been very annoyed with the update and maintenance part for “showcase” site projects that are almost never changed by clients and I was thinking of switching to a Next.js – WordPress headless solution in order to increase performance and security.
At the moment I have been taking courses to refresh React and Next.js and have developed some tutorials and am working on a first complete personal project to actually realize the difference.
I have a few questions for you and I would also like to know your opinions on the above:
1. In order not to reinvent the wheel I would like to start with a starter with at least all the basic Gutenberg blocks already in place, which one would you recommend?
2. How do you handle any starter updates? Does it always have to be done by hand or do you have some solution to easily separate your code from the starter code? I can imagine updates on the WordPress side that then need changes in the starter’s components.
3. I’ve tried Vercel several times and it’s great but unfortunately it doesn’t have a static ip… I’d like to make the backend accessible only from the client’s ip ( mine in this case ) and the frontend so I can be sure it doesn’t receive attacks… are there any solutions to “armor” the backend ( from the infrastructure point of view ) or keep it up only in the building phase ( in case of static sites )?
Thank you very much to anyone who will answer and I’m open to any comments even against this stack.
[ad_2]