when and when not to use headless wordpress

With WP Engine launching their Atlas hosting and more and more developers preferring Javascript frameworks to power the frontend of their sites, WordPress seems to offer the best of both worlds familiar editorial experience on the backend with the flexibility to pick tech stack on the frontend..   WordPress is term used to describe when the frontend and the backend that makes up WordPress site are separated..   By the platform that consumes the, With WordPress setup, you are locked into the output that's controlled by the theme, and with headless, you can output the same content and have it presented to your end users in many different ways because the presentation is controlled API endpoints..   WordPress-specific work can then be outsourced and connected with the in-house frontend via API, potentially saving on cost to develop the site and allowing all the brand and knowledge that's in-house to come through on the frontend of the site where there might be something lost translation otherwise..   API endpoints that output your content to the web can also mobile applications, interface with another CMS that powers publication, be the provider for application with Alexa or Google Home and much more..   And they would not show up on the frontend of the site unless the frontend was built to look for that output and display the buttons.   Even from development process perspective, headless setup sometimes requires in how version control is used, how automated deployments and hosting are set up and handled, and increases the need for communication, especially if two different developers or teams working on the frontend and backend pieces of the site.   Especially debugging WordPress setup is more difficult and involves more communication that more WordPress site.   this just means that more communication and organization is necessary to keep the two codebases sync and providing the best experience for both the content creators using the backend, and also the end users experiencing the frontend of the site..   then it might make sense for them to focus on the frontend of the site while team works on WordPress piece..   Read more