Using WordPress as an API

Wait, what’s an API and why would I use WordPress as an API?

What the heck is a BYOFE, and what does it have to do with WP?

Why are there so many acronyms?!?! 😉

And why is there a picture of the Headless Horseman holding a WordPress logo? Isn’t Halloween over?

WordPress is an incredibly flexible platform on which to build websites and web apps. Traditionally, WP has been used for blogs, publishing platforms, business websites and more. It offers an all-in-one package.

But what if you want to use a framework like Gatsby (or Gridsome), NextJS (or NuxtJS), 11ty, MERN, Laravel, Ruby on Rails, RedwoodJS, etc. to build an application, but long for the WordPress editing experience?

Or, what if you have a client that already has a web application running, and would like to incorporate a blog using WordPress to that application?

There are many ways to “couple” other technologies with a “decoupled” WordPress publishing experience.

In this talk, we’ll explore:

  • What an API is and to use WordPress as an API
  • Look at other BYOFEs (bring your own front-end), and how WordPress offers the same or more out of the box
  • How we can easily create custom post types and custom fields to manage our data in WordPress for API consumption
  • How we can use other frameworks to read and publish WordPress data (I’ll be using examples from Create React App and Gatbsy mostly, but this will apply to any framework that can consume an API
  • Some caveats and how to address those.

This will be a jam-packed, Jam-stacky talk, so BYO-lunch and BYO-curiosity as we discover how we can use WP as an API instead of other BYOFE (ok, I’ll stop with the acronyms now!).

Presentation Slides

Go back to the homepage

© 2021, A labor of ❤️, built on Gatsby by Nate Finch