Problem/Motivation

At the usability meeting (video here - https://www.youtube.com/watch?v=eRTK--QbRmQ ) it was mentioned that the way the Media module does browsing has a table and grid view; it makes more sense for the list view to be a table, and not a re-flowed card. Suggestion starts around time 48:25.

Proposed resolution

Turn the list view into a <table> instead.

TBD: Handling a wide table for mobile? Essentially goes back to card??

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

    Comments

    chrisfromredfin created an issue. See original summary.

    kwiseman’s picture

    Issue summary: View changes
    kwiseman’s picture

    Issue summary: View changes
    narendrar’s picture

    Version: 1.0.x-dev » 2.0.x-dev
    tim.plunkett’s picture

    Assigned: Unassigned » tim.plunkett

    Looking into this

    phenaproxima’s picture

    Issue tags: -beta blocker

    I'm not clear on why this is tagged as a beta blocker.

    Beta is where the PHP API and update path begin, but this has nothing to do with either of those. The frontend code is completely internal and we can change it however we like, whenever we like, so I'm tentatively untagging this as a beta blocker...but certainly a worthwhile feature!

    phenaproxima’s picture

    Assigned: tim.plunkett » Unassigned
    keondral’s picture

    I am working on this as a part of #Atlanta2025

    phenaproxima’s picture

    Issue tags: +Atlanta2025
    leslieg’s picture

    keondra. I'm not sure if you saw this comment in the Project Browser channel from chisfromredfin:

    Yes, you can make those decisions and when we review we will discuss. I would borrow from the media library list view as much as possible, and I would keep the fields we have to the extent possible (though I imagine some might combine into one column)