Drupal 8 theme best practices - here's where we burried the bodies
summary
Claims that Drupal 8 theming is a full rethink not just Twig syntax change with concrete results: Classy and Stable base themes live in core so themes can rely on stable markup, the site uses about 135 template files organized into base/components/layout folders, debugging runs via Kint and Drupal Template Helper plus twig debugging set in services.yml, examples show attach_library/libraries.yml, attributes.addClass/removeClass, inline SVG menus, and a components/Pattern Lab workflow that actually ships.
AI-written summary · about
chapters (24)
- 0:00Start
- 4:16Google Design Camp
- 5:04The Angry Steamer
- 8:02Build a Base Theme
- 8:31Why Do We Have Two Different Based Themes in Drupal Core
- 10:54Debugging
- 11:45The Drupal Template Helper
- 13:01Quick Libraries Debug
- 13:56Templates
- 14:27Group Your Templates
- 15:02Template Naming
- 18:24Fields
- 19:21Field Template
- 24:40Set Classes
- 26:29Attributes Attribute
- 27:25Remove a Class
- 31:01Pre Process
- 32:09Libraries
- 33:53Declare Dependencies
- 35:43Inline Libraries
- 38:36Trick Blocks
- 38:49Trick Block
- 44:27Menu Links
- 54:00Components
related talks
25mNext steps on modernizing the Drupal theme system (Drupal 9 and beyond)
53mState of Drupal 8 frontend
43m[T]alking about [W]hat [I]s [G]reat about TWIG
41mWhat’s New in Drupal 8?
17mDive deep into Drupal 8 Render API
49mLiving Styleguide in your Drupal projects: Benefit from component driven design.
45mExternal Design Systems in Practice
38mFrontend best practices