Hey,
Wondering if there is a simple, end user friendly solution (not having to write a 5 page code, or any at all) to change the default folder thumbnails look. It is clear how to change the thumbnail, so lets skip that part. Currently all thumbnails are covered in black shade that takes 70% of the thumbnail image. What's the point of having a thumbnail feature if it is covered with black or white shade? It makes no sense... This option neither shows the thumbnail, nor makes it easy to read the folder title due to transparency in the shade. Same applies to the collections... images with people have their faces covered by white shade. See attached for reference. AEM DAM 6.5 needs a bit of an aesthetic revamp.
Many thanks
Solved! Go to Solution.
Hello @PovEim
its the default Asset thumbnail view provided here. But if anyone wants to customized it then we need to change via code only, there are other options but it will not help for your requirement.
Add below code in the client libs
.cq-dam-thumbnail-overlay {
background-color: transparent; /* Or set to color that you want*/
opacity: 0.5; /* Adjust the opacity accordingly*/
}
this is simplest ways, you can more customized it.
Hello @PovEim
its the default Asset thumbnail view provided here. But if anyone wants to customized it then we need to change via code only, there are other options but it will not help for your requirement.
Add below code in the client libs
.cq-dam-thumbnail-overlay {
background-color: transparent; /* Or set to color that you want*/
opacity: 0.5; /* Adjust the opacity accordingly*/
}
this is simplest ways, you can more customized it.
Sure, Let us know if it helps
Hi @PovEim, thank you for sharing your thoughts! I completely agree with you. This UI has been around for about 10 years, and while the new AEM Cloud Assets offers a much better interface, updating the AEM on-premise UI typically requires custom coding. I understand the intention behind the black shade, as the white letters need contrast, but I’d prefer the entire thing to be positioned at the bottom instead of the top. Regardless, this shouldn’t pose a significant issue for a developer.