Phase 3: Collaboration > Media Library

[ramonjd]

Tasks that are a part of the Phase 3 Media Library work described here.

Design

Scope

i1 — parity for the existing media library

• Use DataViews to implement a Media screen. With fields including:
  • Media preview
  • Author
  • Upload date
  • File name
  • File size
  • Pixel dimensions
  • Media type (image, audio, pdf, etc.)
  • Attached to
• Uploading via Add media button and drag and drop.
• A Media details / MediaEditor view, using DataView Forms. Allow updating metadata including:
  • Title
  • Caption
  • Alt text
  • Description
• Within the Media details / MediaEditor view, implement an image cropper that supports:
  • Aspect ratio
  • Crop
  • Rotation
  • Flip
  • Tracking edits associated with the attachment entity (for eventual support of undo/redo, and resetting state)
    • To support this, we might need the core data store to support clearing edits directly?
• Within the block editor, add a MediaPicker that implements a picker version of DataViews for selecting one or many media items.
  • Used for selecting images in the Image block, setting a Featured Image, setting a background image, or selecting media for the Audio, Video, and Gallery blocks
  • Support filtering by Attached to to show all media that is attached to the current post/page

i2 — beyond

• Categories and tags support. Some investigation took place in Site editor: 🥝 Media library proof of concept 🥝  #53788.

Completed

• List View: Add media previews to list view for gallery and image blocks #53381

Related reading

• Media Library - Make WordPress Core post
• Site editor: 🥝 Media library proof of concept 🥝  #53788
• DataForm component #59745
• Tracking: Client-side media processing #61447
• Media workflows around patterns #58172
• Image Block: When adding an existing image within a post, explore "attaching" the image to the post if it isn't already attached #66663
• DataViews for Posts, Categories and Tags #62371

[antpb]

Hello! in a recent Media component meeting we decided to start flagging trac tickets with phase-3-media-triage so we can in a future meeting discuss the impact of the Media Library revamp relative to the flagged issues. We see a lot of opportunity in this initiative to solve longstanding Media issues that have been held back by either backbone of the overall data structure of media items.

One that I was just reviewing for instance: 42751 gives us a really good indicator of plugins that are extending the current media library frames. We could check for anyone deregistering the mediaelement css.

More to come as we parse through trac. Just wanted to share our efforts to help align our component focus with this initiative. Please feel free to join any future Media component meetings ( Every Wednesday at 15:00 UTC ) we'd be very open to changing or alternating the time if the current one isn't good for anyone working on the project.

[David-Lazo]

Allow us to organize media in Folders which we can also color code and bake the functionality of these two plugins into WordPress Core.
https://wordpress.org/plugins/enable-media-replace/
https://wordpress.org/plugins/post-types-order/

Also add an option to download all media.

Competing products:
Happy Files:https://happyfiles.io/

FileBird:https://codecanyon.net/item/media-folders-manager-for-wordpress/21715379

Take inspiration from Eagle Application for some great media filtering ideas: https://en.eagle.cool/

[shoelaced]

Would love to have the ability to control responsive image cropping. Here's a great example of why:
https://youtu.be/fp9eVtkQ4EA?si=3ApM7CS569t0iQqB&t=614

Basically: Please bring back the thumbnail editor and further allow isolated edits to all of the other image sizes.

[jameskoster]

I updated the designs in the OP based on the latest data view work. We should decide:

• Default views (e.g. 'All media', 'Images', 'Video', etc.)
• Default layout (grid or list).
• Primary actions.
• Fields to include (mockups are based on wp-admin, but it might be nice to include things like file size/type).
• Which fields should be visible by default.
• What filters users can enact.
• Default setting for 'per page' view option.