Use Wordpress as a Headless CMS for Next JS 

Awesome glad you liked it!

Thanks! What do you mean by inserting. This tutorial is about using data from Wordpress as headless data. Do you mean posting into Wordpress?

@@thedigitalceoyes

Very, very late and hope you found your answer! But for future dev's, add a redirect script to the correct site in WordPress' index.php file

If you have a server where you can run NextJS in root and create sites then yes absolutely. I know you can do that with say an Ubuntu server from digital ocean. I have a video on that But I’ve never personally setup NextJS on a “shared” hosting server but if you can and create multiple subdomains on the same plan I’m sure you can then

@@thedigitalceo first of all thanks for the reply.Helps me a lot . I’m currently going to build a page for a friend-client which includes a blog so I need a way of CMS for him to write blog posts. What other alternatives do you suggest in terms of hosting that ecosystem ? Maybe Wordpress on a web server and netlify free plan for nextjs? The only thing I’m “afraid” of from this approach Is the possible risk for reaching any free plan limits on netlify. Are the free plan limits easily reachable ?The blog is for a person who’s audience is approximately at 50k followers . Also I think paying 2 subscriptions (netlify and web server ) would be quite expensive wouldn’t it ? Thanks in advance :)

@@phyrax1380 This is a good question. There are 2 main ways. But before getting to it. I would start by saying a few points: my experience I would just avoid any free and hobby plans for a client. Secondly in terms of cost for hosting this should be up front: Hosting sites costs a monthly fee and that needs to be clear to clients - even a friend client. So either express the costs and the. put the hosting cost right on the clients credit card or pay for it and charge them an additional fee for hosting. With that out of the way. You can host the front end on vercel and then use a headless cms pay per use like contently or put Wordpress on any other server and use that. There’s also a nice headless cms I use called getcockpit which can be put on any server that supports php. The second way is to host both NextJS and your backend on one server like Ubuntu on Digital Ocean. That way you can put front and backend on one server. I have a video on how to deploy NextJS on Ubuntu. It doesn’t cover setting up Wordpress on the same server though but it would be the same as how to install Wordpress on Ubuntu. I’m sure there are many videos on that.

Thank you

Awesome man!!

It should be fine. In this example it’s public json Wordpress spits out. And the images you add directly in the Wordpress backend and the urls show in the json

You don’t necessarily need an endpoint in the api directory if you use getServerSideProps. You can pull direct from any external endpoint there

I have a solution for you if you are interested let me know i will send you wordpress as a headless and front end as a next js with SEO on the same domain with same url

@@SameerKhan-gu2gc sure..

I think they both work fine. Whatever works. I like strapi and try to do away with Wordpress but it’s important to mention strapi is more complicated to deploy than setting up Wordpress on almost any host. So I would try both and see which you like

It the woocommerce plug-in provides json endpoints it could be but I’m not familiar with the woocommerce plug-in

Did you figure this out? I'm in the same situation, looking for a woocommerce integration with a nextjs/react frontend

@@arman3400 If I am not mistaken I did get it to work but the person I did it for didn't like the complexity/ amount more money they had to dish out.

WooCommerce can make REST API endpoints so I think it is possible

I believe with Wordpress there’s a plugin that would enable that feature on the json Api endpoint

@@thedigitalceo I didn't understand what the endpoints api has to do with it

What was the cors issue? I’ve been able to make Api requests from external domains. However I suppose you can also create a sub domain from the main domain. Put the Wordpress on any server and point it to the subdomain. This way the requests come from the same domain.

Sure you can show any data from the rest Api! I was just keeping it short for the tutorial.

I just wanted to skip some of the things like the full wordpress setup and such.

Hey there. Here is ok. What’s up?