We need to talk about the REST API

We need to talk about the REST API

A non-developer guide to the opportunities, challenges and changes for WordPress coming with the REST API.

10 April 2016, WordCamp London.

B5223ebc4690c47d881722e5adb3a177?s=128

Petya Raykovska

April 10, 2016
Tweet

Transcript

  1. 38.

    A react native iOS app that reuses code from the

    browser app is used for create overlays on the map. uses APIs to gather geodata from Facebook, Swarm, Twitter, Instagram, and Tripit Wordpress provided stable central platform where data can be aggregated and delivered to the frontend nomad base Content platform & API LEAFLET React iOS app @petyeah #wcldn
  2. 40.

    Node.js server enables server-side rendering React was used because it

    allows for isomorphic rendering wordpress at the backend + react fronted us two website react frontend single page app Node.JS @petyeah #wcldn
  3. 42.

    A bunch of complicated technologies are used to render data

    to handle processes that happen on save the fronted is served by wordpress for seo reasons but data is received from web socket and rendered via react The Admin interface is a backbone app that uses the WordPress REST API. Constantly updated filterable stream ny Times live coverage platform wp frontend for seo Backbone + REST custom endpoints data rendered via react @petyeah #wcldn
  4. 43.

    React updates the content react Updates are added on the

    backend or via SLACK ;) React wraps the posts area Request is served by WordPress, PHP generates markup JavaScript listens to Web Socket nytimes.com/live/{event} wp + php react Javascript wordpress @petyeah #wcldn Source: http://www.slideshare.net/ScottTaylor1/rest-in-action-the-live-coverage-platform-at-the-new-york-times
  5. 45.

    Custom WordPress rest api endpoint makes the content available to

    the fronted text and images are rapidly posted via a third party mobile platform, polled and saved to WordPress post meta the data is displayed via a custom React.js front end where the user can easily and quickly read though the content or site back and watch new posts pop into view Data is delivered from wordpress WIRED live blog REact frontend wordpress data third party mobile platform Custom REST API End points @petyeah #wcldn
  6. 50.
  7. 51.

    opportunities Create context-specific solutions Reusable, portable content Separation of concerns

    Integrate WordPress as one part of a content-authoring workflow Familiar backend for authors and publishers @petyeah #wcldn
  8. 62.

    a few setbacks couldn’t edit menus couldn’t use previews couldn’t

    impact the front end in any way each small change on the website apart from the content needed a developer @petyeah #wcldn
  9. 66.

    Loss of wordpress core functionality Disempowers wordpress site builders The

    necessity for structured, portable data CHALLENGES @petyeah #wcldn
  10. 67.

    @petyeah #wcldn Data needs to be structured in a modular

    manner, separate to the CSS and HTML
  11. 68.

    @petyeah #wcldn REST API driven sites will not rely on

    WYSIWYG in TinyMCE for page layouts
  12. 69.

    Loss of wordpress core functionality Disempowers wordpress site builders The

    necessity for structured, portable data Progressive enhancement CHALLENGES @petyeah #wcldn
  13. 70.

    Loss of wordpress core functionality Disempowers wordpress site builders The

    necessity for structured, portable data Progressive enhancement CHALLENGES knowledge deficits @petyeah #wcldn
  14. 71.

    With the REST API, WordPress stops being a web development

    tool used in isolation. WordPress becomes just one module that is available in a web developer’s toolkit WHAT WILL CHANGE? @petyeah #wcldn
  15. 73.

    WordPress as part of a larger stack a new (old?)

    Approach to project management what will change? @petyeah #wcldn
  16. 74.

    WordPress as part of a larger stack what will change?

    WordPress developer will become backend specialists a new (old?) Approach to project management @petyeah #wcldn
  17. 75.

    WordPress as part of a larger stack what will change?

    WordPress will be adopted outside of PHP communities WordPress developer will become backend specialists a new (old?) Approach to project management @petyeah #wcldn
  18. 76.

    WordPress as part of a larger stack WordPress developer will

    become backend specialists WordPress will be adopted outside of PHP communities what will change? The emergence of funnelled, role-based admin interfaces a new (old?) Approach to project management @petyeah #wcldn
  19. 78.

    WordPress as part of a larger stack The WordPress developer

    as a backend specialist what will change? The emergence of funnelled, role-based admins The enhancement of built-in WordPress functionality a new (old?) Approach to project management WordPress will be adopted outside of PHP communities @petyeah #wcldn
  20. 79.

    themes are here to stay. blogs and small sites are

    not going anywhere wordpress will keep democratising publishing WHAT WILL not CHANGE? @petyeah #wcldn
  21. 80.

    themes and theme shops will continue to function as before

    what will not change? @petyeah #wcldn
  22. 81.

    themes and theme shops will continue to function as before

    wordpress will still be used for blogging, small sites and DYI sites what will not change? @petyeah #wcldn
  23. 82.

    themes and theme shops will continue to function as before

    wordpress will still be used for blogging, small sites and DYI sites backwards compatibility will not suffer what will not change? @petyeah #wcldn
  24. 83.

    themes and theme shops will continue to function as before

    wordpress will still be used for blogging, small sites and DYI sites backwards compatibility will not suffer what will not change? wordpress’ mission will remain the same: to democratise publishing @petyeah #wcldn
  25. 85.

    you might be asking yourselves right about now. is the

    rest api getting merged? @petyeah #wcldn
  26. 86.

    and there is a bit of a glitch around how

    feedback is given to the team from the leadership it is. but it still needs work @petyeah #wcldn
  27. 87.

    you might be asking yourselves right about now. how do

    you use it if it’s not merged? @petyeah #wcldn
  28. 88.

    and has its own awesome team working on it that

    has no intention of abandoning it it’s available as a plugin @petyeah #wcldn
  29. 89.

    is it safe to use in production? you might be

    asking yourselves right about now. @petyeah #wcldn
  30. 90.

    the development teams at ny times and wided use it.

    how much more proof do you need? yes. we saw that a few slides back @petyeah #wcldn
  31. 91.

    you might be asking yourselves right about now. will i

    be able to use the rest api? @petyeah #wcldn
  32. 93.

    you might be asking yourselves right about now. why do

    i need to know about it then? @petyeah #wcldn
  33. 94.

    it’s important you understand it when you write proposals or

    read rfps . if you ever want to do kick ass wordpress work it’s the future of wordpress @petyeah #wcldn
  34. 96.

    This is a non developer talk but here are some

    resources you can use to further educate yourself: @petyeah #wcldn