Welcome to the Post Status Draft podcast, which you can find on iTunes and via RSS for your favorite podcatcher. Brian and his co-host, Joe Hoyle, a co-founder and the CTO of Human Made, discuss some of today’s hottest, current WordPress news.
This week, Joe and Brian go into depth discussing all aspects of the WordPress REST API, and the state of the API today.
With the recent merge proposal, there is a good chance it will be included in WordPress core via a two stage process in the WordPress 4.4 and 4.5 releases. The first release would be the core infrastructure and the second release would include the endpoints. This is our longest podcast, but we go in depth on one of WordPress’s most anticipated features in years.
Topics:
- Brief overview: what is the REST API?
- Why is the REST API important, and why are people excited about it?
- REST API proposal
- Reviews from the core team
- New REST API core component
- Trac Ticket
- Comparison’s to Drupal’s REST API
- Customizer roadmap in regards to the API
- Authentication and future REST API projects
Links:
- REST API Version 2 site and docs
- REST API merge proposal
- Committer review requests for the REST API
- Introduction to the WordPres REST API
- How StoryCorp uses the REST API for mobile audio uploads
- WordPress on OpenHub
- The core ticket for merging the REST API infrastructure (Stage 1)
- Lessons for WordPress from Drupalcon (members only)
- Matt Mullenweg’s excitement for the API on a Product Hunt AMA
- Ryan McCue’s “A Future API” post on possibilities, including centralized auth
- Possible roadmap for the Customizer (including REST API integrations, perhaps)
- The new REST API core Trac component
- OAuth1 for the WordPress REST API
- The API on Github
- A Day of REST conference all about the API
