Just Right: Goldilocks and CMS theme systems
summary
Compares concrete choices in Drupal 8 and other CMSes and reports on what was built and what broke: Drupal adds auto-escape (hard to implement but shipping), maintains a stable theme for backwards compatibility (messy but avoids breaking sites), uses Twig and Symfony components, and still suffers XSS vectors, UI/code mismatches, and unthegable forms. Proposes a component-based theme system, calls for a proof‑of‑concept module to show how components, UI personas, and site‑builder needs can coexist without breaking millions of sites.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:27Just Right: Goldilocks & CMS theme systems
- 0:45Lauri Eskola lauriii
- 1:16Scott Reeves Cottser
- 1:57Content Management
- 4:16Leverage agile frameworks top Configure block synopsis for high level overview approaches to corporate strate
- 5:25Frameworks have more limited U
- 7:31Personas
- 8:27Frontend developer/ themer
- 10:45George designar
- 11:13Priorities
- 18:19Current
- 19:03Problems
- 19:18Security
- 20:55Backwards compatibility
- 21:38UV/code
- 22:13Complexity
- 22:41Examples
- 24:20Forms are horrible to theme
- 25:51based theme system
- 26:51should not be the same as data structu
- 28:31Don't break the UI
- 36:21Drupal Site builder Backend Themer
- 51:12Discuss
related talks
25mNext steps on modernizing the Drupal theme system (Drupal 9 and beyond)
45mExternal Design Systems in Practice
57mProgressively Decoupled Drupal, for everyone!
38mFrontend best practices
53mState of Drupal 8 frontend
57mComponent-based Drupal
01h 03mSemantic Site Building
49mLiving Styleguide in your Drupal projects: Benefit from component driven design.