Quality of life configurations with Sitecore

Considering the difficulties that editors encounter in distinguishing between legacy, converted, and legacy supportive components, owing to the absence of folder structure and clear naming, we've introduced a streamlined approach. All component icons are now set to grey or red by default. However, converted and supportive components, along with the majority of new work, will be marked with either blue icons for compatible renderings or green for new arches components. This blue color is intended to be the default setting both arches and legacy supportive components. It's essential for the development team to review and ensure this default setting when releasing new work into the platform. In any instance where the blue green or grey is not the icon for the rending, the setting must be promptly corrected.
Further Icon Definition allow for even easier recognition in the back end will be. Page Layout components should be Starts, Vue/JavaScript driven components should be puzzle pieces.

When looking at the display view list in the backend you only see the render name and its relative location that it is placed in the list. As the teams move forward in using more and more shared content and breaking down content into chunks the Display view gets rather unusable because you would see RichText written possibly 5 times on the page the same is true with accordions. In that view is it possible to interject at least the details of the source which can be altered with a nickname like intro-text, benefit grid.....

The component dependency tree outlines the interrelationships between components in a Sitecore instance, specifically identifying those that are either children of a component or have dependent child components. Only necessary components should be configured in this instance to maintain simplicity and reduce confusion for editors. This approach also minimizes the risk of including non-supportive components by lessening the need for editors to manually add components. Ultimately, this method aids in preventing the appearance of non-supportive components within converted pages, ensuring a clean and efficient working environment.