Components
Media Library
Integrations
Principles
The Filament Media Library Pro is built on a few core principles that guide its design and development. These principles are useful for anyone considering or using the library.
All actions easily configurable
All Filament actions used in the Media Library are defined in their own class. This means you can easily configure any specific action using their ::configureUsing() method:
Which can all be directly configured as such:
Furthermore, you can also easily insert custom actions into all places that you might want them. This includes file actions, empty state actions and bulk actions.
Can power every project
Another core principle that I followed was that the Media Library should be able to power any project. This means projects created from the V1, V2 and V3 of the Media Library with the MediaLibraryItem-structure, projects that already have an existing library of files on a regular Storage-disk, projects that already have an existing library of files on a spatie/media-library-library, or even legacy projects with a wholly different structure.
To learn more about drivers and their details, please read the drivers documentation.