Review: Four Kitchens CMS Dashboard Patterns Applied to Drupal 10/11, Drupal CMS, and WordPress Editorial UX

Four Kitchens has been making the same argument for years in slightly different forms: editors do better work when the CMS stops acting like a developer control panel and starts acting like a task-focused workplace. That sounds obvious, but most Drupal and WordPress admin experiences still expose too much structure, too many options, and too little guidance at the moment editors actually need it. The useful part is not the visual style. It is the pattern library underneath: role-based entry points, constrained navigation, strong preview loops, and governance signals embedded in the authoring flow instead of buried in documentation. Those patterns translate cleanly into both Drupal 10/11 and WordPress, even though the implementation details are different. Executive take If you want a better editorial UX, stop trying to "improve the dashboard" in the abstract. Improve the top ten editorial tasks. The Four Kitchens pattern set maps into five practical rules: show editors the work queue be