Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide dedicated, non-modal view (page) for assets #962

Closed
erquhart opened this issue Dec 22, 2017 · 6 comments
Closed

Provide dedicated, non-modal view (page) for assets #962

erquhart opened this issue Dec 22, 2017 · 6 comments

Comments

@erquhart
Copy link
Contributor

- Do you want to request a feature or report a bug?

feature

- What is the current behavior?

When media library link is clicked in top bar, assets are displayed in a modal.

- What is the expected behavior?

Media library should have a dedicated page, with modal only used when an asset is being selected from the editor.

- Please mention your CMS, node.js, and operating system version.

CMS 1.0.3

@erquhart
Copy link
Contributor Author

cc/ @neutyp

@t1merickson
Copy link

Sharing some designs from the last state they were in; these don't fully address everything they should and are a bit rough around the edges; but wanted to share to kickoff discussion here.

grid view copy 2x
media library copy 2x
media library 2x

@t1merickson
Copy link

issues;

  1. why is the list view wider than the hero card
  2. why does the list view have a dark header when nothing else does
  3. modal view still needs "select" action
  4. actions (delete, rename? etc?) need to be visualized for page version of grid and list view

@erquhart
Copy link
Contributor Author

erquhart commented Jan 2, 2018

There are a lot of similarities between what we need in an entry list view and a media list view - wondering if we can get away from the table styled list here and converge to a single, more robust list view for use in both collection types (thinking forward to media collections being a thing).

@stale
Copy link

stale bot commented Oct 29, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale label Oct 29, 2019
@martinjagodic
Copy link
Member

Closing as stale and/or outdated.

@martinjagodic martinjagodic closed this as not planned Won't fix, can't repro, duplicate, stale Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants