WordPress as a Headless CMS - Bronson Quick
2 likes5,251 views
The document provides an overview of WordPress as a headless CMS, highlighting its role in data capture and delivery while allowing flexibility in frontend technology use. It outlines the benefits of using WordPress, including admin interface, user management, and the ability to serve content across different devices. Additionally, it discusses new workflows and the ability to hire specialized developers while listing examples of companies utilizing this approach.
WordPress as a Headless CMS - Bronson Quick
- 1. WordPress As A Headless CMS @bronsonquick
- 2. Overview @bronsonquick ● Who Am I? ● What Is A Headless CMS? ● How Does It Work? ● Why? ● Who Is Using It? ● Questions ● Thanks
- 3. Who Am I? @bronsonquick ● Senior WordPress Developer ● Core Contributor ● Maintainer Of Chassis ● Occasional WordCamp Organiser - WordCamp Gold Coast & WordCamp Brisbane ● Massive Smashing Pumpkins Fan ● Vinyl Addict ● Guitar Fan
- 4. What Is A Headless CMS? @bronsonquick ● A headless CMS is used only for data capture, storage, and delivery, making it frontend agnostic. Its data can be displayed using any frontend technology, whether in a browser, mobile application, syndication, or elsewhere.
- 6. Decoupling content management @bronsonquick ● Developers are not locked into the templating engine provided by the CMS. The CMS might be written in PHP, but developers working in languages like JavaScript, Java, Ruby, and Swift can use an API to retrieve, store and display data
- 7. Why WordPress? @bronsonquick ● Without WordPress you’d have to create all this from scratch: ● Admin interface. ● User management and capabilities. ● DB structure. ● Server setup - WordPress will run on most web hosts! ● The existing content might already be in WordPress! ● Custom post types, taxonomies and custom meta. ● REST API
- 8. New Ways To Work @bronsonquick ● An internal dev team might want to use React, Angular or Ember for the frontend. ● Content creators can still get to use a familiar UI to enter data. ● Extend the REST API Infrastructure with custom endpoints. ● Serve different content to different devices and platforms. ● You’ll still be writing WordPress code to serve the content in different views.
- 10. How? @bronsonquick ● Extend the REST API Infrastructure with custom endpoints. ● Install the WP REST API plugin. ● Add Authentication - Cookie based, OAuth or OAuth2. ● Write frontend or app code in your preferred language of choice.
- 14. Change Your Workflow @bronsonquick ● Work alongside companies with existing in-house developers ● Your JavaScript developer no longer needs to learn PHP ● Your PHP developer no longer needs to learn JavaScript ● You can hire highly skilled and focused frontend and backend developers ● Hire more sys ops people for scaling and new infrastructure
- 15. Who Is Using It? @bronsonquick
- 16. ustwo.com
- 19. www.npmjs.com