So how could that be done? The answer was obvious enough: decoupled Drupal.Īmazee Labs revisited decoupled Drupal. One of the solutions was to create 12 different Drupal themes, but the client also wanted to work with multiple independent development teams. These sites needed to look and function differently, but use a single content data source. Case study – October 2016Ī client wanted to implement 12 different sites powered by the same backend. However, things changed for Amazee Labs in October 2016, when decoupled Drupal became the solution for one of their clients. In fact, they thought the blog: Black Post – Headless Drupal – The Cake is a Lie External Link captured it well. In the past, they’d stayed away from it because of several concerns: Michael talked about the fact that when the idea of decoupled Drupal was first introduced between 20, Amazee Labs wasn’t a big fan. Apart from Drupal, the company tries to explore other innovative technologies and more recently started using React applications with Drupal as a backend. Michael Schmid (CTO) kicked off the presentation, talking about Amazee Labs and some of its history with Drupal. You can also view the full presentation on YouTube External Link. Below is a summary of their talk - with some updates to ensure the blog’s relevance directly from Michael Schmid. And while that’s nearly a year ago (time flies!) Michael and Brandon’s presentation on the future of Drupal is thought-provoking and extremely relevant today. DrupalCon Baltimore was a five-day Drupal extravaganza in April 2017.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |