Changes between Version 1 and Version 2 of Ticket #47012, comment 28
- Timestamp:
- 08/13/2019 01:58:46 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #47012, comment 28
v1 v2 7 7 == Rough concepts 8 8 9 As a quick experiment, I added our proposed Woo menu items to the concepts shared above. [Take a look](https://jameskoster.files.wordpress.com/2019/08/combo.png).9 As a quick experiment, I added our proposed Woo menu items to the concepts shared above. Take a look: https://jameskoster.files.wordpress.com/2019/08/combo.png. 10 10 11 11 Now, it's not clear whether users would be able to expand all sections simultaneously like in the screenshot - but regardless - the menu gets very, very long when the WooCommerce menu items (purple) are added. And this is just a single plugin. Add a couple of other big players like BuddyPress or bbPress into the mix and things could get totally out of hand. … … 13 13 How could we solve this? 14 14 15 One solution we explored was to add an abstracted "meta menu" affordance that would enable plugins to provide their own contextual interfaces within wp-admin. This is probably easier to explain with a [picture](https://jameskoster.files.wordpress.com/2019/08/meta.png).15 One solution we explored was to add an abstracted "meta menu" affordance that would enable plugins to provide their own contextual interfaces within wp-admin. This is probably easier to explain with a picture: https://jameskoster.files.wordpress.com/2019/08/meta.png. 16 16 17 17 The benefit here is that users always understand the context of their current workflow. To manage products it's clear you have to switch to Woo context. To draft a blog post it's clear you have to switch to "WordPress" context. We've usability tested a similar concept with very positive results.