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.
Read the articleDrupal Pixels
Practical Drupal design and implementation decisions
Latest
More reading
Recent articles, in order of publication.A Drupal Site Audit Before Redesign: Content, Editors, Accessibility, And Caching
Content models, view modes, accessibility, caching, and editor workflow before redesign work begins. The article includes a worked example, an evidence artifact, source…
Drupal Planning Before A Build Starts: Decisions To Write Down
A Drupal planning pass should capture content model, editorial workflow, accessibility, caching, ownership, and release risks before theme or module work begins.
Drupal Theme Regression Checklist Before A Minor Release
A focused Drupal Pixels article about drupal theme regression checklist before a minor release, with the reader situation, tradeoffs, examples, and boundaries mad...
Drupal Content Model Cleanup Before A Redesign
Clean up a Drupal content model before redesign by reviewing content types, fields, view modes, editor workflow, migration risk, and component assumptions.
Drupal View Mode Planning Before Theming Starts
Plan Drupal view modes before theming by mapping editorial use cases, fields, cache behavior, accessibility needs, and component ownership.
Drupal Design Token Handoff Checklist For Theme Builds
A Drupal design token handoff needs more than color names; it needs field, component, editor, accessibility, and cache decisions the theme team can actually use.
Plan Empty States Before Drupal Components Break
Plan Drupal empty states around content, permissions, loading, accessibility, and editor ownership before components ship.
Drupal Content Preview Checks Before Launch
Drupal content preview should be tested with real fields, view modes, permissions, responsive states, cache behavior, and editorial handoff before launch.
Drupal Cache Contexts For Theme Planning
Drupal cache contexts belong in theme planning because they explain why the same component may need different cached variants for routes, users, languages, or permissions.
