 So the next step we have is to have a machine that uses a UI design in front of the desktop. It's based in the end of the year. So now it's also going to be about using WordPress as a background program. So that's what we're going to do at this point. Hey guys, thanks for coming in. And thanks for coming in. I'm working out. It's all about React Projects. It's a great way to end up in React. We're doing a lot of custom work on Strip On. And now a days I do a lot more than LPS6, which is really solid. Use them lightweight of each piece of work as well. And I'm allowing Quest to use React to make my site into a single page. It's going to be just a swap static website. And it's based in Jekyll, which is the static site down here. And I kind of hit a hurdle there. I have a few blog posts on there and I have a few case links. But I do work early. And I realize that when Quest is really built from the ground up for blogging, I'm really going to have it done better. So I'm going to kind of strip back into using WordPress for blogging. I wanted all of the benefits of having a single page work up. Yes or no? Yes. Since I'm currently using Jekyll, it requires blogging and art analysis to be really fun. But it also requires that you build your site again. So I was really looking for the purpose of this party. So that's what we're going to talk about. So in this talk, I'm going to show you exactly how to do that. And just a briefcase, you don't have to use React for what you're going to be learning in this talk. You can use a review or you can build your arguments, learn how to decouple the data that WordPress sets up. We have environments that we're going to be integrating about WordPress and its rest. And a little bit more about React. And I'm going to show you guys how to create your first React. Pull in the data. So the point of having a headless CMS. A headless CMS is where you're using a CMS and all the data you've been separating it from a headless from how you design it. In this game, you can have completely custom run and develop. You don't need to kind of follow the rules and guidelines of what WordPress is. But you're really freeing yourself on the constraints of that. You don't have like that did-suit kind of thing you have to do with a lot of if-then logic. You're really designers UI that do an designer. And another huge, it moves all the display logic to the client side like it should be. And it's streamlined to back-end. So you can, your back-end is solely focused on logic and spitting out that data. And your client can focus on presenting that data. You have enhanced interactivity on your website. Your back-end becomes this kind of state machine. So whatever changes you make, or users make on your back-end, you can store them in your back-end kind of additive database. So who's like red articles on medium? Who's used Twitter? So you know how the recent Twitter updates, you'll see a lot to the Twitter live count. That's kind of, that's exactly what React reflects. That's exactly what React lets you do. It lets you make these live changes and reflect these live changes. Browser reload. So you can have a more secure server or you can separate your data and your logic from how. And that's really where the biggest benefit happens as well. This is a traditional CMS, you have a server or database. You have a server or database. And in our case, we have a WordPress in-depth that uses PHP and handles all the logic. And that spits out data. And then we can use that data. They're using the same data set that they're using across on their sites as well. Let's talk about setting up our dev environments. So, who has a local development? Sorry, I can't hear that. You know how we're putting it all out. Which is making changes on the fly in my QV app. It lets you have the different get-off and off the races right away. Spotbox is also awesome. It's a vagrant setup. And it gives you much more control. And it's precisely control on the environment so you can match exactly what your host is as well. This is screenshot local. It's a nice UI. And it lets you do some control as well. Let's use PHP versions. Let's use MySQL, set the MySQL version. Even access to the database as well. Very basic. It's a simple WordPress install. And it's in the app folder. It's pretty simple as well. The folks that created RAP, the folks over at Facebook, also created create RAP app. And that's a kind of a building box for RAP. It lets you up and running. It lets you connect that up and running with React. It's a source holder with component where you're selecting the right theme or anything. The REST API. But there's also a plugin that lets you use graph QL on the REST API. And we just need to make sure that types and advanced protocols show up in this API. Showpanser uses ACF for their products. REST API, that's an asset. Now this lets you read, like, surely raw data that your site sits on. And you don't really need to. You're going to need 4.7 and up higher. And I believe we're at 4.0. So you'll definitely have it if you get the latest install of the WordPress. They have really amazing documentation that's available to that link. Or if you're a phishing, you can just Google REST API and that kind of stuff. You mentioned ACF integration earlier. Now that's not native. So there's a plugin that lets you handle that very easily. It's ACF through REST API. And you turn that on and you'll have the custom fields show up to wherever you have to set. You also have their own endpoints if you need to. Now this is how you access instance. You have your domain. And then you do dash wp slash wp dash json slash wp. And then on version 2 of the access, you just put that at the end of that. So if you want an access post, just throw a post at the end and pages will do the same. Now let's check out the post. I have a local, and this is what happened. It's pretty messy. And the cool thing is that's just raw off data. But have only 3.0. Only 3.0 is a bunch of words. So reading data can be messy, but if you kind of do it well, it's pretty easy. Use curl on your terminal. Or you can use postman, which is a GUI app that you can download. And it lets you handle data very well. It lets you not only read the data, but you can also check the headers and make sure there are no errors. And if you have any authentication that needs to happen, you can set that up. So that is a lot easier to read. And the WordPress post has an ID. You can see that in the first author there's an ID of 34. And then the title. WordPress's API is a little weird. We have the rendered title. So you can't just say giving the title. You have to say giving the title that is rendered, and then you give the title. Then underneath that we have the content, which is HTML. Now I actually created a blank theme that I use for endless projects. And this just helps me kind of develop a little bit easier. It's just pure index.php file. There are some links on there. So those links go to whatever your site's APIs are. And yeah, let's talk about a couple of differences between how to get it to run or even develop locally. Do you ever kind of open a page?