[wp-trac] [WordPress Trac] #47012: Proposal: Simplify WordPress Admin Navigation
WordPress Trac
noreply at wordpress.org
Fri Aug 16 21:33:48 UTC 2019
#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 MikeSchinkel):
Another thought — and if someone has already suggested this and I missed
it, sorry about that — but a new menu system of this nature could
potentially **allow new menu options to be added by classification rather
than position**, with a default positioning that the plugin vendor does
not control, and the ability for the user to easily reorganize and/or hide
options.
So when your plugin wants to add a menu option is might look something
like this:
{{{
// This would be put into content
wp_menu()->add_submenu(array(
'label' => 'Courses'
'post_type' => 'mysite_course',
'callback' => '...'
));
// This would be put into content
wp_menu()->add_submenu(array(
'label' => 'Subjects'
'taxonomy' => 'mysite_subject',
'callback' => '...'
));
// This would be put into manage
wp_menu()->add_submenu(array(
'label' => 'MyPlugin Settings'
'settings' => new WP_Settings_Page("myplugin",...),
'callback' => '...'
));
}}}
I did not include an example for "design" as I could not think of a good
one. What should a plugin put in the "design" menu?
There would be a need to give the plugin vendor the ability to put things
where they want them, but maybe we should want to add a
**"''Miscellaneous"''** top level option so that items that literally
don't fit elsewhere can go into that menu option. And most vendors
probably would not want their menu being put in a ''"Miscellaneous"''
option, so they would be less likely to pollute it.
**With this constraint in place** no plugins or themes should be able to
pollute the top level menu. We could make is to that top level menus could
only be modified by a drop-in so that people implementing a custom site
could have that control, but no plugin or theme could do it automatically.
''(Or maybe we could allow a theme to also modify the menu?)''
Anyway the above and especially the code is just meant to be **a catalyst
to encourage consideration of and discussion about** how to ensure plugins
don't destroy the simplicity and cohesiveness of this potential design as
well.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47012#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list