Lit-HTML https://www.tag1consulting.com/ en Declarative components in Drupal: Next steps for components everywhere in Drupal - part 2 https://www.tag1consulting.com/blog/declarative-components-drupal-next-steps-components-everywhere-drupal-part-2 <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"> <p><a href="https://www.tag1consulting.com/blog/how-drupal-can-make-true-shared-components-reality-part-1" title="Part 1">Part 1</a> | Part 2 Emerging approaches to front-end development portend a very different world from the one we live in today with regard to handling and juggling components. After all, new best practices promulgated by the likes of JavaScript technologies like React are overturning our preconceived notions about components and our foregoing definitions. For instance, React now contains both declarative rendering of components through JSX and efficient document object model (DOM) diffing through the concept of Virtual DOMs. Despite all of this progress, however, content management systems (CMS) like Drupal and others have not kept pace with the rapid change in how components are realized in front-end ecosystems. Can they ever catch up? <a href="https://www.drupal.org/u/fabianx">Fabian Franz</a> (Senior Technical Architect and Performance Lead at Tag1) presented <a href="https://www.youtube.com/watch?v=RK4BG3hsN3I">a well-attended session entitled "Components everywhere: Bridging the gap between back end and front end"</a> at DrupalCon Amsterdam 2019 that articulated his dream vision for shared components across back end and front end in Drupal's own native rendering. He recently rejoined <a href="https://www.drupal.org/u/michaelemeyers">Michael Meyers</a> (Managing Director at Tag1), and me (<a href="https://preston.so/">Preston So</a>, Editor in Chief at Tag1; Senior Director, Product Strategy at Oracle; and author of <em><a href="https://www.amazon.com/Decoupled-Drupal-Practice-Architect-Architectures/dp/1484240715">Decoupled Drupal in Practice</a></em>) for [a Tag1 Team...</p> <div class="more-link"><a href="/blog/declarative-components-drupal-next-steps-components-everywhere-drupal-part-2" class="more-link" aria-label="Read more about Declarative components in Drupal: Next steps for components everywhere in Drupal - part 2" hreflang="en">Read more</a></div> </div> <span><a title="View user profile." href="/user/preston-so">preston</a></span> <span><time datetime="2020-07-20T12:11:02-07:00" title="Monday, July 20, 2020 - 12:11">Mon, 07/20/2020 - 12:11</time> </span> Mon, 20 Jul 2020 19:11:02 +0000 preston 185 at https://www.tag1consulting.com Declarative components in Drupal: How Drupal can make true shared components a reality - part 1 https://www.tag1consulting.com/blog/declarative-components-drupal-how-drupal-can-make-true-shared-components-reality-part-1 <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"> <p>Part 1 | <a href="https://www.tag1consulting.com/blog/next-steps-components-everywhere-drupal-part-2" title="Part 2">Part 2</a> Front-end development workflows have seen considerable innovation in recent years, with technologies like React disseminating revolutionary concepts like declarative components in JSX and more efficient document object model (DOM) diffing through Virtual DOMs. Nonetheless, while this front-end development revolution has led to significant change in the developer experiences we see in the JavaScript landscape and to even more momentum in favor of decoupled Drupal architectures in the Drupal community, it seems that many traditional CMSs have remained behind the curve when it comes to enabling true <em>shared</em> component ecosystems through developer experiences that focus on facilitating shared development practices across back and front end. At DrupalCon Amsterdam 2019, <a href="https://www.drupal.org/u/fabianx">Fabian Franz</a> (Senior Technical Architect and Performance Lead at Tag1) delivered <a href="https://www.youtube.com/watch?v=RK4BG3hsN3I">a session entitled "Components everywhere: Bridging the gap between back end and front end"</a> that delved into his ideal vision for enabling such shared components in Drupal's own native rendering layer. Fabian joined <a href="https://www.drupal.org/u/michaelemeyers">Michael Meyers</a> (Managing Director at Tag1), and me (<a href="https://preston.so/">Preston So</a>, Editor in Chief at Tag1; Senior Director, Product Strategy at Oracle; and author of <em><a href="https://www.amazon.com/Decoupled-Drupal-Practice-Architect-Architectures/dp/1484240715">Decoupled Drupal in Practice</a></em>) for <a href="https://www.tag1consulting.com/blog/enabling-declarative-components-everywhere-drupal-web-components-out-box">a Tag1 Team Talks episode</a> highlighting the progress other ecosystems have made...</p> <div class="more-link"><a href="/blog/declarative-components-drupal-how-drupal-can-make-true-shared-components-reality-part-1" class="more-link" aria-label="Read more about Declarative components in Drupal: How Drupal can make true shared components a reality - part 1" hreflang="en">Read more</a></div> </div> <span><a title="View user profile." href="/user/preston-so">preston</a></span> <span><time datetime="2020-07-08T05:59:06-07:00" title="Wednesday, July 8, 2020 - 05:59">Wed, 07/08/2020 - 05:59</time> </span> Wed, 08 Jul 2020 12:59:06 +0000 preston 175 at https://www.tag1consulting.com Enabling Declarative Components Everywhere: Drupal + Web Components Out of the Box - Tag1 TeamTalk #019 https://www.tag1consulting.com/blog/enabling-declarative-components-everywhere-drupal-web-components-out-box <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"> <p>Many front-end technologies, especially React, now consider the notion of declarative components to be table stakes. Why haven't they arrived in environments like the Drupal CMS's own front end? Many native CMS presentation layers tend to obsolesce quickly and present a scattered or suboptimal developer experience, particularly against the backdrop of today's rapidly evolving front-end development workflows. But according to Fabian Franz, there is a solution that allows for that pleasant front-end developer experience within Drupal itself without jettisoning Drupal as a rendering layer. The solution is a combination of Web Components support within Drupal and intelligent handling of immutable state in data that allows for Drupal to become a more JavaScript-like rendering layer. Rather than working with endless render trees and an antiquated Ajax framework, and instead of reinventing Drupal's front-end wheel from scratch, Fabian recommends adopting the best of both worlds by incorporating key aspects of Web Components, the Shadow DOM, and particularly syntactic sugar for declarative components that competes readily not only with wildly popular JavaScript technologies like React and Vue but also matches up to the emerging approaches seen in ecosystems like Laravel. In this <em>Tag1 Team Talks</em> episode, join <a href="https://www.drupal.org/u/fabianx" title="Fabian Franz">Fabian Franz</a> (VP, Software...</p> <div class="more-link"><a href="/blog/enabling-declarative-components-everywhere-drupal-web-components-out-box" class="more-link" aria-label="Read more about Enabling Declarative Components Everywhere: Drupal + Web Components Out of the Box - Tag1 TeamTalk #019" hreflang="en">Read more</a></div> </div> <span><a title="View user profile." href="/user/preston-so">preston</a></span> <span><time datetime="2020-07-01T05:13:47-07:00" title="Wednesday, July 1, 2020 - 05:13">Wed, 07/01/2020 - 05:13</time> </span> Wed, 01 Jul 2020 12:13:47 +0000 preston 170 at https://www.tag1consulting.com