DAM module releases

DAM module is split into dam and dam-app (both required).

This change separates UI components (Assets app, preview functionality, and so on) from the API for better modularity and resolves async circular dependency issues with the Imaging and UI modules.

New DAM JCR S3 submodule

The optional dam-jcr-s3 submodule connects Magnolia DAM to S3 storage. Use it if you choose to store asset binaries in S3 while metadata remains in the JCR.

New binary management API.

The DAM 5 API simplifies adding new storage options and supports varied implementations. It ensures backward compatibility for custom extensions.

Binary detection enhancements.

DAM 5 detects if binaries are stored in S3, Hybrid Assets, or JCR using node property checks. This feature enhances storage flexibility.

Hybrid Asset incubator module replacement.

The Hybrid Asset incubator module, which offered connections to S3 and Azure, is replaced with DAM 5’s natively extensible solution. The incubator module is planned for deprecation.

External DAM framework S3 connector replacement.

DAM 5 aims to replace the External DAM framework S3 connector, which stores both binaries and metadata in S3, due to performance issues. The S3 connector is planned for deprecation, while the Bynder connector remains unaffected.