Redesign Extend Page in Claro

Created on 8 October 2020, about 4 years ago
Updated 30 August 2024, 4 months ago

Problem/Motivation

The Extend page in Claro is cluttered and could use better filtering and organization. Modules are sorted into categories which are themselves details components. Ideally, we could find a better way to filter modules and reduce the visual clutter on the page without using details elements for the module groups.

Prior art

  • Module Filter is a potential module to look at for generating ideas and comparing affordances.
  • The Eleven theme experimented with the design for the extend page. It still keeps the details wrappers, but has cards instead of rows. You can see it in the eleventheme beta 1 presentation video (starting approx 6m40s).
📌 Task
Status

Active

Version

11.0 🔥

Component
Claro 

Last updated 2 days ago

Created by

🇺🇸United States dyannenova

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇺🇸United States worldlinemine

    The issue of the problems with the Extend Page arose today in the Drupal Usability Meeting 2024-08-30 📌 Drupal Usability Meeting 2024-08-30 Active in response to this issue Unmet module requirements are too hard to find on admin/modules .

    In a comment on another issue of note ( here 📌 Rename the drupal.org (json:api) source type Active ) the concerns about the Extend Page and how it's challenges need to be part of a broader discussion was mentioned.

    This particular issue has remained dormant for some time now despite the smaller attempts in other issue to address some of the usability issues of the page. Regardless of if the solution lies in redesigning how the Extend Page works in core or in Claro it would be helpful to try and coordinate efforts and improve communication.

    In my opinion, if we need inspiration to move this issue forward we need only look at the WordPress plugin admin page to know that Drupal can do better.

    What next step can we take to unstick this issue and move it forward?

Production build 0.71.5 2024