I have placed a folder containing multiple CSS files inside the ui.content module and configured both filter.xml and .content.xml to deploy it to /content/dam/my-project. After deploying the codebase, the folder appears in the AEM DAM console at the expected path, but the individual CSS files do not show up inside the folder. How can I ensure that these CSS files are correctly uploaded as DAM assets with their content visible without manually uploading each file?
I compared a CSS file manually uploaded to AEM DAM with one deployed via code. I noticed that the manually uploaded file is stored as a dam:Asset and includes subnodes like metadata, renditions, and related. In contrast, the CSS file deployed via code is stored as an nt:file and lacks these subnodes. As a result, the deployed file doesn't behave like a true DAM asset and its content isn't visible in the AEM DAM console. How can I ensure that CSS files deployed via code are treated as proper DAM assets with all necessary metadata and renditions?