Neos Dev DocsAssets
In this chapter we discuss media assets, these are all by editors uploaded documents. In contrast the next chapter discusses resources - files which belong to a Neos package and are versioned in git.
With Neos, editors can organize those assets professionally. The extensibility of the media-module allows to integrate external libraries and storages.
#Media Browser
The Neos Media Browser represents a Media Library where editors can upload and manage images and files.
These documents ("assets") can be searched, tagged and grouped in collections.
An asset can belong to one collection and to many tags.
The media browser also allows to replace an asset with a newly uploaded one. When using in combination with the Neos Redirect Handler it can automatically create redirect links as well.
#How to change and extend the media management
#Extended Options
Extendable Media Management
- Asynchronous Image Generation
- Cropping and scaling of images are deferred optionally until the image is actually requested by a browser to optimize performance.
- Responsive Images
- With "responsive images" visitors always get the optimal image-sizes for their device for maximum quality and speed.
#Cloud Storage Support
The "StorageInterface" integrates external storage without any difference for the editing workflow. Implementations exist for "Amazon S3" and "Google Cloud Storage".
#Asset Sources
External Assets can be intergrated via "AssetSourceInterface". This allows to connect DAM-Systems as well as MediaLibraries
#"Asset Management" Integrations
Digital Asset Management Systems manage media libraries across whole companies. Neos integrates PixxIO, more integrations are being developed.
#Photo-library Integrations
Various stock-photo services can be integrated into the media-library. Unsplash, Pexels, Shutterstock offer high quality stockphotos with reasonable terms.
#MediaWiki Integration
Using "assetsource mediawiki", the whole MediaWiki library is available via the Neos media-library.