Next steps on modernizing the Drupal theme system (Drupal 9 and beyond)
summary
Drupal 9 ships with two versions of stable (Drupal 8 stable and Drupal 9 stable) and will deprecate the older one later; Classy continues but is proposed to become a starter kit so core can change markup without breaking sites. Proposal bundles template, CSS and JS using frontmatter syntax (already used by help topics) so overriding a template requires copying its CSS/JS, implemented with Twig and libraries API to force explicit ownership and reduce unpredictable front-end breakage.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:20Screenshots
- 3:35Plans for Drupal 9
- 5:09Breaking the markup
- 9:13The root cause
- 9:57Drupal 8 Stable
- 12:32Starter Kit
- 14:54Override Variations
- 15:58Starter Kit Overlap
- 17:06Frontmatter Overlap
- 18:05Conclusions
- 18:52Questions
related talks
01h 01mDrupal 8 theme best practices - here's where we burried the bodies
53mState of Drupal 8 frontend
01h 10mJust Right: Goldilocks and CMS theme systems
49mLiving Styleguide in your Drupal projects: Benefit from component driven design.
43mPreprocessors, Components, and CSS in JS
57mProgressively Decoupled Drupal, for everyone!
32mRise above the Framework
41mNext Drupal admin UI improvements