 So, brief background. So one day my boss comes to me and he asked me to create a blog for our website. He says, let's use WordPress and I can just buy a team and we can install some plugins. So for me, I didn't have the luxury of time to figure out how to do it the WordPress way. Also, I was also a bit concerned about the security of the plugins. So for me, the fastest way for me to implement this was to use Laravel on top of WordPress. So a bit of research. I researched a bit before I proposed a solution. So for me, I learned about WordPress and Q-styles and about how to hook into the WordPress loop. So basically WordPress, there's a bunch of posts, it will loop through it and you can actually plug in your CSSM styles while it's looping through all the posts. So you could actually style your posts. And in general, WordPress development is, you use this thing called advanced custom fields. So you create custom fields like in the database and you add different types of database tables. So if you want, let's say, events, you could add some information about the event like a start and an end time to your posts. So another thing that I researched was that there are different plugins that do the same thing. So for example, if there's a team that makes it responsive, there's another company also offering the same plugin and then you have to compare and then see which one works best for your user. So it's not for me. So I was thinking, how do I use the MVC pattern in WordPress and how do I make sure that my plugins and teams are updated to the latest standards? So I had these issues as well as the security issue with the third-party plugins. I had to check if they were working, did someone insert a script into it like presented a while ago. So I was like, no, I don't want to do this. The solution is to keep WordPress in a separate server. So you could install it like in a separate server where you point a different subdomain to it and you don't reveal it to the public. So this allows you some security through obscurity. So some people would say that this is actually not security, but for me, I lose one more attack vector, which is the WordPress website. So Carcel to the rescue. So here's Carcel GitHub repo. So it has 2,000 stars already, 2,000 plus. And the issue queue is pretty updated and it's fairly active community. It's built by Jake Rossi, who basically allows to simply call WordPress content using Laravel's eloquence impacts. So how to get started. So in your Laravel app, you just generate the Carcel service provider. So using this command here. And after you generate the service provider, you have to configure it. So you configure the database connection. So you just set up the different fields here and you set it to connect to your WordPress database, basically. So this is how you use it. There's a core set. You just reference or use the Carcel model post and you reference it in your model. And you just have to call the same model. And in this case, post publish get that gets all the published posts. And or you could also use the alternative, which is status publish, and get all the post that I have the status publish. And if you want to find a specific post, you just use post find, which is very eloquent, and then you get the post title. So there's other ways you could get the post by slug. So if you prefer to put slugs and then call them into your frontend app, and you could use custom fields. Basically WordPress has the ability to allow authors to assign custom fields to a post, which I was explaining earlier. And it turns posts into some other content type. So for example, for events, you have event start, event end. And this is how you call and get the posts with the custom fields. So in this case, if your post has a link or a phone, so if you're creating a e-commerce site and you want to add the publisher, the author's phone and his links, you could add it in. Provided that you created the custom field for that. And this is how you could save the new post if you have a new one, new data to add to the meta content. Other than this, you could also get the nav menu for your WordPress site. So if your boss creates his own menu system inside the WordPress, you still call it. So you see here, you call it by slug. Here, we're getting the primary menu, and we're looping through all of the menu items. So you could get the title, the name, or the link text. So this is the WordPress way, and for me it's kind of, the code doesn't explain fully well what's happening behind the scenes. But basically what's happening here is you create a hook, and then you register it to the WordPress loop. And it triggers on init, it will trigger the action, and call your menu. For other features, you could reference or read me in the Corsal website. To get started easily, just look for a Corsal example online. There's a lot of them. So I won't bother with showing you how it's done. So some thoughts about this, pros and cons. So the pro is security, you don't need to maintain your WordPress. And the con is you have two systems to deploy now. So basically every time you deploy, you need to make sure both are running correctly, otherwise one will fail. So you get to enjoy the best of both worlds. Laravel and the eloquent syntax and the WordPress. Your users can use the WordPress site, let's say your boss. And they can manage the content with a wizarding editor. So yeah, that's basically it. So about me, I'm Joe, currently head the Laravel Philippines group in the Philippines, and I volunteer for I volunteer. We basically create a website portal for volunteers to contribute their time. It's built on Laravel. So you can follow me on Twitter. Thank you very much.