WordPress, but Decoupled скачать в хорошем качестве

WordPress, but Decoupled

Topic: WordPress, but Decoupled Speaker Name & Bio: Prem is an open source enthusiast working in WordPress domain since last 6+ years & runs his own microblogging freewebmentor.com. He holds great experience when it comes to scaled WordPress projects which caters the need for big enterprise clients on WordPress VIP-GO platform. Follow Me: Twitter:   / thepremtiwari   Facebook:   / thepremtiwari   Instagram:   / thepremtiwari   Topic Description: Decoupled CMS is like a traditional CMS but without a frontend. What remains is a backend delivering content via a RESTful API. Content is managed via the WordPress editorial interface. It’s then delivered via REST API to your separate frontend application which can be built with whatever technology you like. Decoupled/ Headless WordPress Traditional (Monolithic) Model Content creation & mgmt. WordPress serves HTML pages Front End DeliveryContent Management Content DB API. Common Headless Models ● All-in-one ● External front end ● Content Hub All-in-one & Content creation & mgmt. Content Management Content DB API WordPress serves a Single Page JS app (React, Angular, Vue, etc.) Front End Delivery Example: Quartz Standard WordPress templates serve a Backbone JS app and initial page content The Backbone app calls the WordPress API on subsequent requests for content External Front End with & Content creation & mgmt. Content Management Content DB API Node serves a JS app (React, Angular, Vue, etc.) Front End Delivery Example: Gretchen Rubin A Node app serves an isomorphic React app and initial page content The React app calls the WordPress API on subsequent requests for content Loading content client Content Hub Front End Delivery Other content destination Mobile App Content creation and/or mgmt. Content Management Content DB API Other content source Content creation and/or mgmt. Considerations ● Why decouple? ○ What’s driving the decision? ○ Do the benefits outweigh the additional complexity? ● Content Previews ● Caching (minimizing requests and round trips) ● Handling failures (e.g. what if the API is down?) REST API (Docs) Thanks! Q&A