Generate AEM Content Package with binary properties

great thanks.

this issue is solved since CONGA AEM Plugin 1.7.0 via the "aem-contentpackage" post processor and the "contentPackage.files" property
https://devops.wcm.io/conga/plugins/aem/extensions.html

a real-world example:
https://wcm-io.atlassian.net/wiki/x/AQDYEQ

yes - but that would be an invention only for CONGA - my goal is to be fully compatible with the other sling tools that interpret JSON as content (JCR content loader, file system resource provider, sling mocks etc.)

I thought we could have a pattern in json property values like "file:<filename>" which addresses the path to the binary file to read.

this makes definitely sense. but we have to think how we represent this.
currently an CONGA-generated package is represented by exactly 1 json file. this cannot contain a binary file (and it would be quite inconvenient to put it there e.g. base64-encoded).

instead we should think about allowing to define packages in files/folder structures e.g.:

• Sling-Initial-Content with a combination of JSON files and binary files

• expanded FileVault XML layout in AEM packages

in both cases we still need to support handlebars templating.