[wp-trac] [WordPress Trac] #47012: Proposal: Simplify WordPress Admin Navigation

[WordPress Trac]

#47012: Proposal: Simplify WordPress Admin Navigation
------------------------------------------------+--------------------------
 Reporter:  lessbloat                           |       Owner:  (none)
     Type:  enhancement                         |      Status:  new
 Priority:  normal                              |   Milestone:  Awaiting
                                                |  Review
Component:  Administration                      |     Version:
 Severity:  normal                              |  Resolution:
 Keywords:  needs-design-feedback dev-feedback  |     Focuses:  ui,
                                                |  accessibility
------------------------------------------------+--------------------------

Comment (by DeFries):

 Replying to [comment:32 jameskoster]:
 > Just in case it wasn't clear, WooCommerce would not be the exception. I
 imagine all of those kinds of plugins you mention would introduce their
 own menu, just as WooCommerce does in the prototype I shared.
 Yes, I interpreted it that way.

 > Content Management might just be the default "app" on fresh WP installs.
 It and other "apps" (e.g. Woo) run on top of WordPress as an operating
 system. We might abstract all of the general settings and options into a
 dedicated "system preferences" section, so the "Content Management app"
 feels more like an app, rather than a kernel.

 Yes, this makes a lot of sense.

 > Am I right in understanding that you think we should explore enabling
 plugins to apply context within a single core menu system? Without the
 separate "meta level" menu?-

 No, that's not what I meant. I think what you've shown so far is the way
 to go with what we're calling a "meta-level menu" and "Content Management
 app". I absolutely think this is the way to go.

 Replying to [comment:33 lessbloat]:
 > @DeFries, what I'm hearing you say is that you're worried about there
 being a situation where ''some'' plugins reside in the default WP menu,
 while others (perhaps the more complicated plugins) are broken out into
 their own sections. Is that your primary concern?

 I'll try and answer both your questions here @jameskoster @lessbloat.
 My concern here is if our goal is to simplify the way we currently have
 menus, and plugins adding extra menus to it, we need to be as consistent
 as we can. So, when a plugin adds a content component as WooCommerce does
 with its products, we should recognize the fact that we'll be teaching
 people to understand that the Content menu and its submenus are where they
 should be looking for all things related to content.

 Whether they want to add a new blog post, a new page, that's where they
 should go. And that should also imply that new content within other
 content creating plugins should also be found exactly there.

 So, for creating their new job post, new event, or new product, the
 location to start that process should be the Content menu. All the time.
 That's being consistent. Doing that for some plugins but not others,
 that's inconsistent and introducing a similar problem like we're having
 now in this new interpretation.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47012#comment:36>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform