One of the the things that was most memorable from both case studies was how Mike and Brandon talked about how pursuing the decoupled architecture renewed their appreciation and enjoyment of using the chosen CMS. “Falling in Love with CMS All Over Again” In the case of Four Kitchen’s work on, this even includes a customer community eager to develop their own “apps” that leverage site content. Multiple frontends can operate independently. Decoupling the architecture means decoupling not only the development work of back and frontend, but also the timetable and effort-level for upgrades and refreshes.įurthermore, by implementing the CMS as a client-agnostic JSON REST API, the open the door other channels for innovation. Similarly, for Pixo and Four Kitchen’s clients part of the attraction to investing in a decoupled infrastructure is lowering the complexity (and cost) of a future re-design. In this way, the frontend can be truly agile, adapting to both client requests, and technology innovation. We’ve enormous innovation in tools and techniques over the past few years for modern design, but integrating these fast-evolving display with a CMS in a tightly coupled or “monolithic” way can be complex and kludgy.īy separating out the UX layer of the site, Pixo and Four Kitchens were not only able to leverage their chosen tools, they gained the ability to iterate with them independently of the backend CMS. The primary motivation for both projects was to deliver a stellar user experience on web, tablet and mobile form factors. Using the Best Tools to Deliver the Best Experiences The latter approach was what we discussed in the Mike and Brandon’s case studies. There are many ways that people are looking at decoupling, from fronting their CMS with a native mobile app, to in-browser interactive experiences leveraging the latest JavaScript frameworks, to using static site generators instead of an integrated “theme”. Linux aficionados may recognize it as the historical echo of The Cathedral and the Bazaar. Both architectures have been around for ages, and both have their pros and cons. It’s important to recognize that this debate isn’t a question of right and wrong, or even new vs old. This is often referred to as Monoliths vs Microservices.
#History headless cms drupal software
The whole discussion of decoupled (or “headless”) CMS implementations is really part of a larger zeitgeist in software and internet services: a general trend towards a world with more specialized components integrated via the network, vs holistic software deployments. Monoliths and Microservices (Everything Old Is New Again) Here are the high points from our webinar. The webinar followed my presentation with Amitai Burstein from Gizra on Decoupled Drupal at DrupalCon Los Angeles in May, where I simply could not contain my enthusiasm for the topic.Ĭlever memes aside, the excitement is real, and for good reason.
0 kommentar(er)
