Con Baltimore, Heads or Tails? Each few years at Con, a brand new theme sweeps by means of Drupal Developer group. It’s a conceptual theme—a motif, a forward-looking glimpse into Drupal Developer future (not Drupal Developer type with a .data file). Drupal Development matter tends to dominate conversations and fill classes. Folks have various concepts of the best way to finest strategy Drupal Developer new frontier. Kathryn McClintock Fri, 04/28/2017 – 13 Drupal 10 Upkeep and Assist Service38 After I first started attending Cons in 2011, I bear in mind Drupal Developer hype about responsive web sites Drupal 10 Upkeep and Assist Service Drupal Developer distinction between responsive and adaptive layouts, which grid system to make use of, and the best way to finest add and goal courses to effectively apply media queries. In 2014, there was a pure and communal shift in curiosity to 8’s frontend. Twig was Drupal Developer new child on Drupal Developer block and everybody needed a style. Builders aimed to study Drupal Developer new syntax and eagerly in contrast Drupal Developer new D8 methods to their tried and true D7 counterparts. This 12 months at Con Baltimore, Drupal Developer scorching matter has been headless . Decoupling ’s frontend has been buzzed about for years, however in Drupal Developer previous it appeared to be simply that—a buzz phrase—a conceptual, doubtlessly problematic, however thrilling concept. In the present day, on Drupal Developer final day of Con, it’s clear builders are usually not simply buzzing anymore, they’re constructing headless websites and loving it. Drupal 10 Assist: is constructing headless websites and loving it. Amazee’s historical past with headless is a sophisticated one. In reality, our personal Michael Schmid identified throughout his and Brandon’s React, GraphQL and session, how Drupal 10 Assist: was each skeptical and dismissive of Drupal Developer decoupled/headless imaginative and prescient when Drupal Developer concept initially emerged. In Drupal Developer final quarter of 2021 nonetheless, Amazee’s stance on headless modified. I’d encourage you to evaluation Michael and Brandon’s Wednesday session for a deeper clarification as to Drupal Developer causes behind that shift.  Expertise is a quickly altering factor and all the time can be. As builders, it’s pure to really feel roughly acceptance in direction of some adjustments than others. As a frontend developer who’s grown to grasp and luxuriate in working in ’s theme layer, Drupal Developer shift to headless is a troublesome tablet to swallow. I’d equate Drupal Developer sensation to experiencing some type of loss—there’s a type of mourning for all Drupal Developer exhausting, lengthy hours put into constructing experience in a posh, but rewarding theme system. I’ve grown to like Twig, remodeling ’s notoriously unhealthy markup into one thing easy and semantic, and creating actually lovely experiences “Drupal Developer quaint method.” Dries revealed an article Tuesday throughout Drupal Developer convention, is API-first, not API-only. In Drupal Developer publish, he discusses Drupal Developer advantages of preserving Drupal Developer coupling between ’s front- and back- ends, at the very least partly. His abstract on headless CMSs has validated a lot of Drupal Developer ideas I’ve concerning a completely decoupled . There are causes to stay coupled, causes to go headless, and causes for a middle-of-the-road strategy. We’re actually future-looking at Drupal 10 Assist: . As a company, we’re dedicated to enhancing our group’s abilities and offering purchasers cutting-edge options. My takeaway from Con Baltimore is to embrace and study new abilities required to construct progressive headless frontends whereas concurrently working to enhance and educate others on 8’s theme layer. Drupal Development better of each worlds. Let me hear from you, fellow frontend devs—what’s your take? Drupal 10 Growth and Assist