Last year, I talked to nearly one hundred Drupal maintenance support plans agency owners to understand what is preventing them from selling Drupal maintenance support plans. One of the most common responses raised is that Drupal maintenance support plans‘s administration UI looks outdated.

This critique is not wrong. Drupal maintenance support plans‘s current administration UI was originally designed almost ten years ago when we were working on Drupal maintenance support plans 7. In the last ten years, the world did not stand still; design trends changed, user interfaces became more dynamic and end-user expectations have changed with that.

To be fair, Drupal maintenance support plans‘s administration UI has received numerous improvements in the past ten years; Drupal maintenance support plans 8 shipped with a new toolbar, an updated content creation experience, more WYSIWYG functionality, and even some design updates.

A comparison of the Drupal maintenance support plans 7 and Drupal maintenance support plans 8 content creation screen to highlight some of the improvements in Drupal maintenance support plans 8.

While we made important improvements between Drupal maintenance support plans 7 and Drupal maintenance support plans 8, the feedback from the Drupal maintenance support plans agency owners doesn’t lie: we have not done enough to keep Drupal maintenance support plans‘s administration UI modern and up-to-date.

This is something we need to address.

We are introducing a new design system that defines a complete set of principles, patterns, and tools for updating Drupal maintenance support plans‘s administration UI.

In the short term, we plan on updating the existing administration UI with the new design system. Longer term, we are working on creating a completely new JavaScript-based administration UI.

The content administration screen with the new design system.

As you can see on Drupal maintenance support plans.org, community feedback on the proposal is overwhelmingly positive with comments like Wow! Such an improvement! and Well done! High contrast and modern look..

Sample space sizing guidelines from the new design system.I also ran the new design system by a few people who spend their days selling Drupal maintenance support plans and they described it as “clean” with “good use of space” and a design they would be confident showing to prospective customers.

Whether you are a Drupal maintenance support plans end-user, or in the business of selling Drupal maintenance support plans, I recommend you check out the new design system and provide your feedback on Drupal maintenance support plans.org.

Special thanks to Cristina Chumillas, Sascha Eggenberger, Drupal Update, Archita Arora, Dennis Cohn, Ricardo Marcelino, Balazs Kantor, Lewis Nyman,and Antonella Severo for all the work on the new design system so far!

We have started implementing the new design system as a contributed theme with the name Claro. We are aiming to release a beta version for testing in the spring of 2021 and to include it in Drupal maintenance support plans core as an experimental theme by Drupal maintenance support plans 8.8.0 in December 2021. With more help, we might be able to get it done faster.

Throughout the development of the refreshed administration theme, we will run usability studies to ensure that the new theme indeed is an improvement over the current experience, and we can iteratively improve it along the way.

Acquia has committed to being an early adopter of the theme through the Acquia Lightning distribution, broadening the potential base of projects that can test and provide feedback on the refresh. Hopefully other organizations and projects will do the same.
How can I help?

The team is looking for more designers and frontend developers to get involved. You can attend the weekly meetings on #javascript on Drupal maintenance support plans Slack Mondays at 16:30 UTC and on #admin-ui on Drupal maintenance support plans Slack Wednesdays at 14:30 UTC.

Thanks to Lauri Eskola, Drupal Update and Jeff Beeman for their help with this post.
Source: New feed