When 500 editors across 130 sites log into our Drupal platform, the first thing they see is a dashboard designed to support their work. But what should that dashboard actually do? Over the last year, we’ve been figuring out how to answer that question. The result is a dashboard that surfaces what matters most to our editors: announcements about new features, their recent edits, broken links, accessibility issues, duplicate profiles, permissions, design settings, and more.
This session isn’t a technical deep-dive into code; it’s the story of the decisions behind the dashboard. We’ll share how we prioritized features, balanced editor needs with technical realities, and decided what belonged on the dashboard—and what didn’t. Attendees will walk away with lessons they can apply to their own platforms, whether they manage one site or one hundred.