Semantic Site Building
summary
Argues that naming and architecture decide editor usability and developer maintainability, not visual design alone; shows a pattern: use Drupal 8 entities (not forcing everything into nodes), create custom entity types for things like notifications, and prefer paragraph types + inline entity form for editable page sections. Demonstrates Search API, Media, Entity Browser and config management working together, gives a 30‑page audit produced in 2.5 days, and recommends a ~30‑hour build plan to standardize naming and view modes so the CMS actually works.
AI-written summary · about
chapters (22)
- 0:00Semantic Site Building
- 3:40Back in 2012
- 4:03Naming
- 4:42What do we need
- 6:02Consistency
- 7:43Redundancy
- 8:19Linking Fields
- 8:42Extensibility
- 10:16Malleability
- 11:19Usability
- 14:24Content Types
- 21:40Node
- 23:55Entities
- 26:27Drupal Console
- 34:33View Mode
- 36:01Roles
- 38:19Path breadcrumb
- 40:42Paragraph
- 48:58Build Plan
- 54:53Site Audit
- 58:18Code Review
- 59:21Final Questions
related talks
30mAce any design in Drupal - layout tools and components in your site-building toolbox
01h 10mJust Right: Goldilocks and CMS theme systems
15mDesigning for modularity – from art direction, to site design, to back-end
17mPaving the Way to Construction
38mFrontend best practices
22mA Journey of Building a Media Publishing Platform
15mWhy You Should be Building Design Systems and CSS Architectures
42m"Site Building 2.0: How Layout Builder will change everything"