Suggestion: Please remove the "collection indicator" in content trees.

[markadrake]

When a content node in the tree is configured as a collection, a "collection indicator icon" is layered on the content type's icon.

It blocks the visibility of that icon by ~50%.

This icon does not provide any value to the editor (it literally has no impact on them at all) and may even hinder their productivity.

Combining icons and a color scheme allows us to design our sites consistently, and our clients become fluent in this language. This current practice makes an icon, already difficult to see because of its razor-thin lines, even less legible.

Version 15 Today

Recommendation

[Luuk1983]

At first, I wasn't a fan of removing the icon completely, but a agree it's too large. However, if I'm not mistaken, all list views will also show the children in the content tree anyway in Umbraco 14+. In the past, the list view would hide the children, creating the necessity for the icon the show that there are in fact children. That necessity is now gone, so I wouldn't really mind if the icon were to be removed. But if the icon were to stay, it should be a lot smaller,

[Luuk1983]

Options could be: use coloring for list views and nodes that are protected. Or in Sitecore (I know, eew), you had a bar left to the content tree where icons could be placed, like this:

Not saying this is the answer, but still a possible option.

[bjarnef]

Something like this could be a possible option: https://dev.to/icebeam7/creating-a-treeview-control-in-net-maui-49mp

However it may look odd with a gap for tree nodes with none of these mini icons.

Screenshots from article above.

Currently there are also an icon for save node with pending changes (to publish), but if IIRC only one icon is shown at the time.

From VS I have examples like these:

It seems to have a reserved space for the mini icon.

I agree the mini icon on top of tree next clutter the tree node icon, and if moved next to it, it may work better in a smaller size (and the gap wouldn't be too large).
It would probably still only show one mini icon at the time in this order:

• Protected node
• Collection/Listview node
• Draft changes / changes to publish