Page 1 of 1

More modern media library

Posted: Sun Jan 12, 2025 5:02 am
by mdsojolh444
The media library only changed in small steps in the first Gutenberg phases. However, the teams had enough other projects to work on. Phase 3 will see a comprehensive modernization.

Expanded management functions such as categories and tags for media are planned. Views and filters are also on the to-do list: This should make it easier to find the right files. For large, long-term projects with thousands of images, this is an enormous challenge today, which is why specialized plugins are often used.

Another goal is to better integrate media editing in the block editor and the individual media views. The official post mentions unified crop functions as an example.

The team also wants to change the way media is inserted so that users don't always have to open the entire media library. For example, if images have already been uploaded but not yet assigned to a post, WordPress could display them directly when an image block is inserted.

Also on the to-do list are workflows around published media and post formats rcs database that only consist of one media block. There will be improvements not only for images, but also for audio, video and other file formats, as Matias Ventura writes in his post on the topic .

Considering how important multimedia content often is these days, these innovations and improvements are definitely very welcome. Finding a specific file is not always so easy these days unless everyone in the team is disciplined and names everything sensibly. At the same time, it will be interesting to see how well the new media library works with other new features such as workflows for teams.


Over 5,000 subscribers are already participating!
Our newsletter provides you once a month with WordPress insights, business tips & more!
First name
e-mail address*
I would like to subscribe to the newsletter to be informed about new blog posts, e-books, features and news about WordPress. I can revoke my consent at any time. Please note our privacy policy .

Subscribe now
Better handling for blocks
Because blocks have become so important, Phase 3 of the Gutenberg Project aims to improve block library management.

The plan is to expand the existing block manager into a central administration for blocks, similar to the environment for plugins. WordPress admins will then be able to activate or deactivate individual block types globally for the entire site. Advanced authorization controls will also make it possible to specify more precisely which blocks are available for which user roles. According to the official plans, individual functions of a block can also then be activated in a targeted manner.

There is also already a hidden function for linking post types to blocks. For example, a certain type could always have an image block instead of an empty text prompt. This function should be easier to find and use in the future.

Installing blocks from the directory should also be more convenient than before. For example, it should be easier to see which blocks a plugin adds.

This extensive wish list should please both admins and users of WordPress. It addresses many points that are currently not optimally resolved because they require additional clicks. And the point of turning off certain blocks and block functions for entire user groups should reduce many headaches for website admins.

backend design and navigation
Finally, an important project in phase 3 is the modernization and revision of the backend. After many years, a comprehensive redesign is now underway. The Site Editor should serve as a starting point and inspiration for this.

One aspect is to make the navigation more flexible and modular. The most important menu items can then be freely positioned and arranged, similar to widgets. A distinction between core functions and plugin areas is also conceivable.

If there are a particularly large number of menu items, a "drilldown"-like navigation should provide more clarity. Areas and settings are opened step by step instead of displaying everything on one level. The backend should also be easier to adapt to individual needs. The team is investigating how parts of the admin area can be optionally shown and hidden.

Another goal here is to unify the backend and block editor. Components and design systems from the editor should therefore be incorporated into the admin area. A library of reusable UI components is being built for plugin developers. This should help plugins to fit harmoniously into the environment.

Last but not least, the Phase 3 team wants to work closely with colleagues from WP Feature Notifications to ensure that notifications have a separate and compact place in the future. This would replace the current uncontrolled growth at the top of the backend.