Drupal 7 still has a long life ahead of it, and with the right contrib modules it is usable for anyone looking to build headless websites today. Even though there's excitement about the upcoming Drupal 8 release - and I'll detail the action below - you don't need to wait to get started with these techniques. Headless Drupal Now!įor those looking to develop Headless Drupal websites right now, you can totally do it with version 7. If you're curious why this is exciting people, see my previous blog post on the topic: what's the big deal with headless websites? In this blog post I will dig into the technologies at your disposal for exploring Headless Drupal today. Headless Drupal is officially now "a thing". I also spoke with Jesus Olivias who recently did a great Spanish-language podcast with Omar Aguierre on the topic, and he was kind enough to give me his two cents. In a world where user experience is critical for long-term success, decoupling CMS and front-end, which is what Headless Drupal achieves, is no longer an option, but a necessity.A couple of weeks ago at Drupal Costa Rica, I had a nice conversation with Todd Ross Neinkerk of Four Kitchens, who was there presenting on the notion of de-coupling content management and content display ( here's video of a similar talk he did in Austin). However in certain scenarios, its benefits far outweigh its drawbacks. Headless Drupal is not without its share of adversaries or criticism. You do not require front-end for staging environment where content is created and reviewed only. And after final approval, content is published to another publishing system. Or sometimes you want to create two different application where one is used to create content like we do in staging environment.CMS is secondary function of the larger application. You are building an application where managing content is just one part.Static HTML files are easier to handle anyway from scaling perspective. And it makes more sense as having no heavy CMS in the delivery architecture means less of server processing. You want to rely more on front-end architecture for scalability.You can event have one common editorial system for multiple publishing system. Headless Drupal will allows you to have different architecture for editorial system and the publishing system. If you are building your website where content can be consumed by different applications and repurposed based on context.So when should we go for Headless Drupal? We do not use default Drupal templating layer to display the data or content. And front end specific application framework like Angular, Backbone, Ember or Knockout delivers the API output onto the front-end template layer. In a Headless Drupal website or web-app, the content for the site/app is accessed using an API through formats such as JSON or REST.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |