Summary for November 23rd 2010 UI Chat
Good meeting today
- We now have a completed wp-admin.psd (props TECannon, Chexee)
- Screenshot: http://cl.ly/3MsY
- Downloadable file: http://cl.ly/3NA9
- Upcoming UI tasks will heavily surround Google Code-In
- All other tasks directed at 3.2 as 3.1 goes into beta
Simon Wheatley 11:57 am on November 24, 2010 Permalink |
Hi UI Gang,
I want to push discussion of an issue I outlined in Trac ticket #15477, that there is insufficient differentiation between the network admin screens and their site admin equivalents. The issue has been slightly mitigated by Ryan’s addition of the network name in the graduated bar at the top to the right of the WP logo… but I still maintain that the two areas don’t have sufficient differentiation.
For those who’ve not run the latest alpha version of WP 3.1, the two links below show screenshots. To push my point, I’ve outlined the two main visible signifiers of whether you are in the Network of Site admin area.
Users in network admin: http://dl.dropbox.com/u/72676/wp-3.1-vis-diff/network-101124-1.png
Users in site admin: http://dl.dropbox.com/u/72676/wp-3.1-vis-diff/site-101124-1.png
What was the UX problem we aimed to solve by splitting out the Network Admin area? Does solving it outweigh the issues I’m describing? Do other people agree that there even is an issue in differentiating between the two areas?
I wish I’d made the UI Chat to talk this over, but unfortunately family business intervened. Apologies.
Cheers,
Simon
Ryan Boren 7:31 pm on November 30, 2010 Permalink |
What’s there now for network and user admin is just v1. It is by no means complete or ideal and we should improve it in 3.2.
Why a separate network admin?
One canonical place per network for net admin tasks.
You get a full admin area for adding menus vs. adding everything under one top-level.
It allows us to fully separate network-wide and blog-specific tasks and notifications.
It can be locked down with more restrictive cookies or served from specific servers.