Skip to main content

2 posts tagged with "admin-ui"

View All Tags

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

· 9 min read
Victor Jimenez
Software Engineer & AI Agent Builder

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.

Review: Drupal Core Making Navigation the Default Admin Experience Instead of Toolbar, with Developer Impact for Admin UX, Contrib Compatibility, and Site-Builder Workflows

· 6 min read
Victor Jimenez
Software Engineer & AI Agent Builder

Drupal core is not just experimenting with a new sidebar. It is steadily moving the admin experience from Toolbar toward Navigation, and that has real consequences for Drupal 10/11 teams that maintain custom admin UX, contrib-heavy stacks, and site-builder training materials.

The timeline matters. Navigation was introduced as an experimental module in Drupal 10.3.0 on June 21, 2024. It became stable in Drupal 11.3.0 on August 4, 2025. Then, on March 3, 2026, core issue work landed to add Navigation to the Standard install profile and Drupal recipes so new installs move toward the new admin model by default.

That does not mean Toolbar is gone today. Core's own issue queue still treats accessibility as the blocker before a full replacement. The practical reading for developers is: the direction is decided, but production rollout still depends on unresolved keyboard and assistive-technology gaps.