What is the best practice for DAM custom metadata schema and custom search forms. Do we commit the /conf/../dam/adminui-extension/metadataschema/.. into Git codebase and deploy through maven into AEM? OR do we treat metadata schema similar to /content and install the package manually on different environments?
In my opinion that is a good practice to keep your metadata schema configuration in git repository. I think that this is more application than content part. It's always good to have ability to track history of changes regarding metadata schema structure.
In my opinion that is a good practice to keep your metadata schema configuration in git repository. I think that this is more application than content part. It's always good to have ability to track history of changes regarding metadata schema structure.
sounds good. I too believed anything /content/ shouldn't go into git, but all rest folder should be committed. Was checking if there was opinion or reasons for otherwise.
