david g.

@assetshare2018 are you still experiencing this issue or have you figured it out?

closing due to inactivity - please reopen w requested details if you havent figured it out.

Thanks for the info!

Some of the original placeholder files are here: https://github.com/Adobe-Marketing-Cloud/asset-share-commons/tree/gh-pages/_lib/gfx We can use the "button" effect defined in: https://github.com/Adobe-Consulting-Services/adobe-consulting-services.github.io/blob/master/lib/gfx/psds/acs-site.psd for the package icon (or similar)

Courtesy of @thinkstainless [asset-share-commons-logo.svg.zip](https://github.com/Adobe-Marketing-Cloud/asset-share-commons/files/4524000/asset-share-commons-logo.svg.zip)

@thinkstainless put together a few other options ... not sure if the original posted one is too "delicate"?     

You can also create a new AssetDetailsResolver [1] impl (examples: [2]), which will automatically show up as an option on the Search Page's configuration [3]) and you can use that...

@GL369 to be clear, removing the Hidden Predicate that @godanny86 mentioned will allow dam:Assets that are sub-assets to show up in the results; within ASC there are no real facilities...

@artdirk i can all but guarantee the AEM Authoring code wont be able to be used in any meaningful way here. The Asset APIs of course will help you find...

@deepkamal looks super cool! can you talk a little bit about where these assets get uploaded, and the how they get on AEM Author so they can undergo review/approvals/etc.