Better communication of "enabled/disabled" status on multi-site builds

[mildlygeeky]

I find that Craft can be more than a bit misleading when communicating an element's enabled/disabled status on builds that use mult-site.

For example, if an entry is enabled for Site A but disabled on Site B:

• In the Entries list while on Site B, the entry shows as disabled, flat out. This may lead me to believe that it can be safely deleted, but then I would also be wiping it out on Site A. "Delete for Site" can help with this sometimes, but it is still hard to know in list view if something is disabled globally or just for this site.
• If I am unsure and click into the entry while on Site B, I get a lightswitch that shows as disabled. However, I still do not know that globally it is "semi-enabled" until I click the three dots next to the site it's disabled for, which then will change the lightswitch over to a "partially enabled" status.

I'm not sure I know of the best fix for this, but wanted to note that right now there is a lot of doubt in a user's mind when working with statuses and multiple sites together.

Some possible ideas:

• In list view, a status indicator could show the current site's status as is, but show a "stack" of one additional status indicator behind it on multi-site if any other sites have a different status. This way, in the above example Site B would have its Disabled status at the forefront, while an Enabled indicator would peek out from behind it to show that one (or more) other sites differed from Site B (indicating that it might not be safe to delete the entry).
• As well, when deleting an entry, the alert modal should note if the site is enabled for any sites, and how many.
• In the CP's detail view, it feels like the rolled-up view for showing that an Entry is enabled is kind of odd. Once it is expanded, it cannot be collapsed, and the collapsed view only gives part of the story anyway. I would recommend getting rid of the collapsed view, or at least making it the default. Not sure if this would be an issue for sites with a very large number of sites, but as-is you really need to expand it to know the full story on an entry's enabled/disabled status.