A Drupal Site Audit That Produces Build Decisions
Turn a Drupal audit into an ordered set of content-model, accessibility, caching, editor-workflow, and maintenance decisions.
Tag
Turn a Drupal audit into an ordered set of content-model, accessibility, caching, editor-workflow, and maintenance decisions.
Content models, view modes, accessibility, caching, and editor workflow before redesign work begins. The article includes a worked example, an evidence…
A focused Drupal Pixels article about drupal theme regression checklist before a minor release, with the reader situation, tradeoffs, examples, and boundaries…
Clean up a Drupal content model before redesign by reviewing content types, fields, view modes, editor workflow, migration risk, and component assumptions.
Plan Drupal view modes before theming by mapping editorial use cases, fields, cache behavior, accessibility needs, and component ownership.
A Drupal design token handoff needs more than color names; it needs field, component, editor, accessibility, and cache decisions the theme team can actually…
Drupal content preview should be tested with real fields, view modes, permissions, responsive states, cache behavior, and editorial handoff before launch.
Drupal cache contexts belong in theme planning because they explain why the same component may need different cached variants for routes, users, languages, or…
Check Drupal media fields before theming so editors, responsive images, alt text, view modes, and future components do not inherit bad assumptions.
A Drupal theme performance budget gives teams concrete limits for CSS, JavaScript, images, caching assumptions, and component behavior before launch.