I don’t see this as being about designing for customers on our hosting vs. designing for people hosting themselves or elsewhere.
I see this being about designing for people wearing different hats, regardless of where the site is hosted.
A single person may wear multiple hats, but that’s not always the case.
Even in the self hosting world, we see people here whose focus is on running their community, and leaning on a friend or someone else they find to help with more of the technical parts.
Even if you’re doing it all yourself, it may be helpful to be a bit more conscious of when you’re wearing your “sysadmin” hat vs. your “site admin” hat vs. your “community manager” hat.
We’ve been attempting to tease apart this distinction here in our docs and discussions as well.
The latest round of changes have indeed shifted the focus on the admin dashboard to things of concern for people wearing the “community manager” hat.
But within /admin as a whole, we still need to address the needs of all of these different hats.
I can see a future where /admin is even more customizable, possibly with personal choices for what is on the landing page there for individuals in a single site.
But in this latest round of changes, we’ve been teasing things apart within existing pages.
The “manage updates” page is where we’re currently consolidating more of this version information, and adding more info like update history and links to changelogs.
I think a way to go about thinking of contributing there would be to:
- (a) consider how to make that page itself more useful
- (b) consider how to make that page more discoverable
- (c) consider what information there could/should also be surfaced elsewhere (possibly related to (b) if we assume anytime we do this it should link to the page itself)