Configure the Magnolia Assets subapp
Magnolia Assets subapp is Magnolia’s native solution for simple Digital Asset Management (DAM) scenarios.
Installing the dam-app-jcr submodule automatically adds the subapp to the Assets app.
The submodule uses a definition decoration at /dam-app-jcr/decorations/dam-assets-app/apps/dam.subApps.yaml to register itself with the container app.
For installation information, see DAM App module.
Configuration
Image manipulation actions such as resizing or cropping are provided by the UI Media Editor module.
Configuration of these actions can be found at /modules/ui-mediaeditor/mediaEditors/image, with some of its parts defined in YAML-based decorations under /ui-mediaeditor/decorations/ui-mediaeditor/mediaEditors.
Bulk publishing
Bulk publishing allows you to simultaneously publish multiple assets. This feature is preconfigured and enabled by default for the Assets app.
The publish, unpublish, and delete actions in the Magnolia Assets subapp are configured with bulk: true, which uses the uuids parameter instead of a single path to process multiple items.
To disable bulk publishing for a specific action, set bulk: false in the action configuration or remove the bulk property.
For more information on bulk publishing configuration, see Publishing module: Activate bulk publishing.
Turning image thumbnails off in the asset browser
By default, image thumbnails are displayed next to the asset names in the asset browser.
This behavior can be changed by setting the thumbnails property to false for the jcrName column (line 15 in the configuration snippet below):
workbench:
contentViews:
- name: tree
$type: treeView
dropConstraint:
$type: jcrDropConstraint
primaryNodeType: mgnl:asset
multiSelect: true
columns:
jcrName: &name
class: info.magnolia.dam.app.contentview.column.JcrAssetNameColumnDefinition
nodeTypeToComponent:
mgnl:folder:
icon: icon-folder
mgnl:asset:
icon: icon-assets-app
thumbnails: falseA universal icon is then displayed next to the asset names instead of thumbnails:
Workspace
The subapp operates on the JCR dam workspace.
The dam workspace stores the uploaded original assets and variations created with image operations such as cropping.
Node types
The DAM module registers a custom mgnl:asset node type.
Magnolia Assets subapp operates on nodes of this type and on folders.
How to handle many assets
The DAM can handle a very large number of assets and is used in installations with hundreds of thousands or even millions of files. To keep both JCR operations and the Assets app UI fast and usable, avoid very flat hierarchies and organize assets into folders, aiming for roughly 500 assets per folder and using subfolders where needed.
When your total volume of assets or the size of individual binaries starts to impact publication times, storage footprint, or operational workflows, consider offloading binaries to DAM 6.0, our External DAM integration framework, our DAM API, or one of our Incubator modules extensions.
For best performance with JCR assets, limit each folder to around 500 assets regardless of type (images, PDFs, etc.)
Use subfolders to stay organized and avoid performance issues.
-
Avoid placing too many assets in a single folder.
-
Use subfolders to improve performance and maintain structure.
Using the app
See Managing assets for how to use the subapp.