Contrib.social

Find a way to differentiate different media types in the administrative media library grid view

Open on Drupal.org →
Created on 16 July 2018, over 6 years ago
Updated 6 September 2023, about 1 year ago

Problem/Motivation

In #2962525-70: Create a field widget for the Media library module → , this feedback was raised:

Last thing I noticed is we are not showing the media type in the library. This is probably a separate issue, but it could be hard to see the difference between a remote video and an image at first glance. They both show an image thumbnail. This might be an issue when users enable multiple types for a field (like for a slideshow or something).

This was a conscious decision by the UX team:

This will need to be discussed in another issue, but the UX team decided that including the type made the library look cluttered. The items in the library use a new view mode and template, so a theme could implement some custom styling to make types look distinct without just including the type name above the media item name.

Let's talk about that in this issue, and see what we can come up with.

Proposed resolution

Figure out if and how to visually differentiate different media types in the media library.

Remaining tasks

Agree on a course of action, write a patch and iterate it directly into the ground. Then commit it.

User interface changes

The media library may receive new UI elements or functionality.

API changes

None anticipated.

Data model changes

None anticipated.

📌 Task
Status

Active

Version

11.0 🔥

Component
Media  →

Last updated about 3 hours ago

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Needs accessibility review

    Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.

  • Needs usability review

    Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

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.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024