As the WordPress API matures, this is an important moment to take stock and consider the best use-cases. We’ll briefly take a bird-eye view of the API, before deep-diving into different ways the API has been deployed.
We’ll see examples of the API as an integration tool for running dual CMSs, as a public-facing queryable dataset, as a big data visualisation tool and as a way to share large sets of data.
Along the way, I’ll share ways to make your API implementation more efficient, and share some of the pitfalls and mistakes we’ve made.
We’ll take a look at decoupling both the front end and back end of WordPress, and answer the obvious question: why continuing using WordPress?
Key takeaways:
- The API liberates data outside of WordPress and projects like Gutenberg – breaking content into modular content blocks – will change the way WordPress considers data relationships.
- The API is driving a new Enterprise Stack – with each element the industry leader in its field – including WordPress as the fast moving publishing solution.
- Decoupling the front – using technologies like React – & decoupling the back – using technologies like Elasticsearch – begs the question: Why continue using WordPress? The answer is that clients, content teams, editors & authors all over the world have built a passion for WordPress for its ease of use and friendly interface. This strength should never be underestimated.
A couple of years ago Joe Hoyle introduced us all to the API – then last year we had a lot of HowTo talks across different WordCamps. Now is the perfect time to look at when to use the API & looking at some real-world examples.