United States

— Oakland

Declarative Shadow DOM and the future of Drupal Theming

camp: BAD Camp 2025

For a frontend developer, Drupal is old-school. For the past decade, developers have been experimenting with JavaScript-based frontend frameworks that completely replace Drupal's frontend. But what if we could inject a fully modern JavaScript API into Drupal's rendering system? Can Single Directory Components and Declarative Shadow DOM get us there?

Web Components with a 95% working live demo!
— Seattle

CSS-in-JS and Drupal
 sitting in a tree...

conference: Drupalcon Seattle 2019

So you are a Drupal themer thinking about styling a decoupled Drupal website? It can be daunting to look at the JavaScript community; there seems to be a new best practice every week. And picking the right CSS-in-JS solution appears to be a nightmare of infinite choices. What to use? Styled Components? Glamorous? Inline CSS? Once you’ve decided on a solution for your decoupled project, do you now maintain two different CSS build tools for your projects, one for Drupal and one for decoupled?

Decoupled website (illustrated). Shows an outline of a horse cut into two parts, with Drupal on the backend, React on the frontend, and GraphQL connecting the two halves.
— New Orleans

Six Easy Pieces for the New Front-end Development

conference: Drupalcon New Orleans 2016

Modern front-end devolopment has become a tangle of fast-moving technologies. Our job is to implement HTML, CSS, image formats, and JavaScript, but with over 200,000 JavaScript projects on NPM alone, how do you find and learn about the best tools and techinques? And even after we've learned a new tool, it can feel like our skills are soon out-dated.

Frontendia: a path from "Ye Olde Selector Hell" through the "Sea of Specificity" and past the "Isles of NPM installs"
— Los Angeles

Drupal 9 Components Library: The next theme system

conference: Drupalcon Los Angeles 2015

For every version of Drupal I can remember, if a module wanted to display content, it had to provide the default HTML and CSS for it. This paradigm has served us well for years, but its time to radically improve the re-usability of our HTML and CSS by implementing a core components library.

Drupalcon Los Angeles: Drupal 9 Components Library
— Austin

Twig is dead. Long live web components!

conference: Drupalcon Austin 2014

<hyperbole-alert>Everyone is excited about Drupal 8’s Twig system, but it's already dead to me.</hyperbole-alert> The W3C is working on a specification for a templating system that is native to the HTML language, called Web Components.

Twig is fine. I'm just trolling MortenDK.
— Austin

Managing Complex Projects with Design Components

conference: Drupalcon Austin 2014

Our CSS sucks. We've been building sites for over a decade using crappy, ornamentation techniques and shoddy selectors. Our styles unintentional bleed across the site. Our stylesheets are fragile and unmaintainable and full of specificity landmines. Pandas wander alone in the wilderness.

The “Fugly” Selector Hack: use Sass' @extends to extend a class name I wish I could use in the DOM to the actual selector in the DOM I couldn't change.
United States