Maestro: The Inline Admin Menu Editor

Maestro lets you orchestrate the appearance of the WordPress admin menu — rename admin menu items, reorder them, change their icons, and hide admin menu items from the roles and people who don't need them. Every WordPress install accumulates menu clutter. A dozen plugins each claim a top-level slot, submenus sit in an order nobody chose, and clients meet a dashboard full of tools that aren't theirs. Maestro is how you customize the admin menu back into shape: declutter it for a client site, rename cryptic plugin labels into the words your team actually uses, reorder the admin menu so what you touch daily is at the top, and hide admin menu items per user role — or from one named person — so everyone sees only their own work. Instead of a separate settings screen, Maestro turns the admin menu into something you edit in place — right where it lives. Toggle Edit Menu from the admin bar, and the menu becomes editable. Click a menu item to rename it, hide it from selected user roles, or change its icon. Drag submenu items and whole menu groups to reorder them. Nothing to configure first, and nothing to learn: the menu you are editing is the menu you are looking at. And it stays out of the way. Maestro adds no autoloaded options and does no work at all on the front end, so a menu you tidied for the dashboard costs your visitors nothing (see Performance & footprint below). Try Maestro right here. Launch a demo in WordPress Playground — it boots a throwaway site with the plugin active in edit mode, plus User Switching and test users (editor, author, contributor, subscriber; password password) so you can try per-role visibility by switching to another user's account. What you can do — as a site administrator Maestro's enhancements are only activated for logged-in users with an Administrator role. They can:

• Rename any top-level or submenu item — just click the label.
• Reorder items by dragging (top-level items among themselves, submenu items within their parent), or with the keyboard (Alt+Arrow).
• Swap icons on top-level items. The icon picker offers Dashicons and bundled Bootstrap Icons with search. It accepts any of WordPress's four native icon forms (dashicon, "none", base64 image data-URI, or an image URL).
• Hide items from chosen roles — including administrators. Custom roles registered by other plugins (User Role Editor, Members, etc.) appear automatically.
• Hide items from specific people, by name, when a role is the wrong unit — one person on a shared role who doesn't need a particular tool. Search for someone in the visibility popover and add them; a parent's sub-items can be hidden per person too, with the parent left visible. Like every other hide in Maestro, this is cosmetic only: the page still loads by URL for anyone authorized to see it.
• Reset a single item to its WordPress default, or reset everything at once.

Changes are global — one configuration applies to everyone. Your custom menu configuration is stored as a sparse delta (just the differences) layered over the menu WordPress builds on each load. Nothing is rebuilt or duplicated, so a reset simply removes the delta, and the original menu returns. Important: visibility is cosmetic, not access control Hiding a menu item only declutters the menu. The underlying admin page still loads for anyone who knows or types its URL if they're authorized to see it. That's because a page's own registered capability is the true lock. Maestro operates on the menu (presentation), which is a different plane from authorization. If you need to actually prevent access, pair Maestro with a capability manager like PublishPress Capabilities**. It's menu-aware, and its Pro tier can block admin pages by URL. The maestro_capability filter lets such a plugin hand editing rights to a custom capability instead of the default manage_options. Accessibility and localization The editor is keyboard-operable end to end — select with Enter/Space, reorder with Alt+Arrow, and every move and save is announced to screen readers. Modified items carry a non-color indicator with screen-reader text, so their state is never indicated by color alone. Maestro uses the maestro-menu-editor text domain and ships a translation template plus starter language packs for Spanish (es_ES), German (de_DE), Japanese (ja), French (fr_FR), Portuguese – Brazil (pt_BR), and Italian (it_IT). WordPress.org language packs override and extend these; native-speaker and WordPress Polyglots reviews are welcome.

1.5.3

• WordPress 7.1 support. 7.1 keeps the toolbar on screen in the post and site editors, where it used to be hidden. Maestro's Edit Menu button appeared there too — on screens with no admin menu to edit. It now appears only where it can actually do something.
• Fixed: Edit Menu on a phone or narrow window opened the editor without opening the menu. WordPress hides the admin menu at narrow widths behind the toolbar's menu button. Edit mode started anyway, so you got the editing toolbar and no menu, with nothing saying to tap the menu button first. It now opens the menu for you, and the menu button keeps working normally while you edit.
• Fixed: in the site editor, Edit Menu led nowhere. The site editor never shows the admin menu and has no way to bring it back, so the button had nothing to act on. It now takes you to the Dashboard with the editor already open.
• Fixed: your unsaved post could raise a browser warning when entering or leaving Edit Menu. Both are ordinary page loads, so an unfinished post triggered the browser's "Leave site?" prompt. Maestro now saves your work first, the same way WordPress's own autosave does. It never publishes anything — a draft stays a draft and a published post keeps the version your readers see.
• Fixed: the Collapse menu button did nothing during editing. Collapsing is not possible while the menu is being edited, but the button was still there to click. It is now hidden until you finish.

1.5.2

• Fixed: an override could silently stop applying when the same menu item was saved under two spellings of its address. Some items can be addressed more than one way — with or without a version number or tracking parameter, for instance. If a single save carried two such spellings of the same item, Maestro stored both, then read the item as ambiguous and applied neither. A rename or a visibility rule would stop working while still appearing in your settings, which is the worst way for something to break. Maestro now keeps one entry per item, so the situation cannot arise.
• This also closes a way for someone who can edit the menu but cannot list users to undo a per-person visibility rule set by an administrator. As always, hiding is cosmetic: no capability was granted or removed, and the affected page stayed reachable by URL throughout for anyone allowed to open it.

1.5.1

• Fixed: the edit-mode toolbar no longer shifts while a change saves. The save status now sits in a reserved slot, so the rename field stays where it is instead of sliding sideways every time a save cycles through "Saving…" and "Saved".
• Accessibility: a locked sub-item role is now reachable, and says why it is locked. When a role is already hidden at the parent level, that role's checkbox under "Hide its sub-items from:" is shown as locked. It was previously skipped by keyboard and screen-reader navigation entirely — so the explanation was written for assistive technology but could never actually be heard. It is now reachable and announces its reason. The value still cannot be changed.
• Accessibility: dismissing the visibility popover by clicking outside it now returns focus to the button that opened it, matching what pressing Escape already did. Previously focus fell to the top of the page and a keyboard user had to tab back.
• The focus outline on edit-mode toolbar buttons is lighter, giving a clearer ring against dark admin colour schemes.
• Fixed: an override could look applied in the editor when it was not being applied. On a site where two menu rows resolve to the same address — the same screen registered twice with different version or tracking parameters — the visibility popover could show roles as checked while the menu itself ignored the rule, and saving from that state could store what the popover showed. The editor now applies nothing for an ambiguous row, exactly as rendering the menu already did.
• Internal: a stored override key carrying an HTML-encoded > is now classified consistently as a top-level or a sub-item key.

1.5.0

• New: hide menu items from specific people, not just roles. The visibility popover now has a search box for people alongside the role lists. Type a name, pick them, and the item disappears from that person's admin menu only — everyone else with the same role still sees it. You can target several people, and on an item with sub-items you can hide the sub-items per person while the parent stays visible. Use it when a role is the wrong unit: one editor on a team of editors who doesn't need a particular tool.
• Still cosmetic, exactly like hiding by role. This changes what someone sees, never what they can do. A hidden page still opens normally for anyone who types its URL and holds the capability it requires, and no capability is added or removed by any rule. If you need to actually restrict access, pair Maestro with a capability manager — hiding a menu item is not a security measure.
• Targeting your own account is allowed. Maestro warns you inline, and you can always undo it: the Edit Menu control lives in the WordPress toolbar where no rule can reach it, and a row you have hidden from yourself still appears while you are editing so you can remove the rule.
• Targeting people requires the ability to list users. If you have handed Maestro to a custom role via the maestro_capability filter and that role cannot list users, the person search is hidden and hiding by role continues to work as before.
• Known limitation: on a multisite network, network super admins are not affected by person-targeted hides. Role-targeted hides still apply to them, unchanged.

1.4.1

• Fixed: editing a top-level item no longer changes a submenu item that happens to share its slug. WordPress and many plugins register a submenu under the same slug as a top-level item — the "All Products" self-link under a custom post type, or a plugin shortcut that points at an existing top-level screen. Renaming or hiding the top-level item could carry to that submenu row as well. It now applies only to the item you edited. This completes the fix started in 1.4.0, which covered the reverse direction (editing a submenu never touched its parent).
• Configs are now stamped with a schema version, so Maestro can tell an override you saved recently from one saved before submenu items could be addressed individually. Overrides saved by earlier versions keep behaving exactly as they did until you next save.
• If a submenu item was already renamed along with its parent, that name is kept when you upgrade, so nothing changes under you unexpectedly. Select that submenu item and use Reset Item once to restore its original label.

1.4.0

• Hide sub-items independently of their parent. The visibility popover now offers a second role list, "Hide its sub-items from:", on any item that has children — so a parent can stay visible while its sub-items are hidden from the roles you choose. A role already hidden at the parent level shows as implied and is never stored twice.
• Renames keep count bubbles and badges. Renaming an item that carries a count bubble or a "NEW" badge (WooCommerce order counts, plugin notification badges) now preserves that markup instead of stripping it. The stored title stays plain text; the badge is re-read from the live menu on every request.
• Editing a submenu no longer changes its same-slug parent. WordPress registers some submenu items under the same slug as their top-level parent (the "All Products" style self-link under a custom post type). Renaming or hiding that submenu row now applies to that row alone. Editing the top-level item still carries to a same-slug submenu row until you give that row an edit of its own — that is deliberate, so overrides saved by earlier versions keep behaving exactly as they did.
• Better coexistence with other menu plugins. Maestro no longer overrides another plugin's custom_menu_order when it has no ordering of its own to apply.
• Hiding a top-level item is now strictly cosmetic by construction: Maestro only removes a row the current user could already reach, so WordPress core's own permission check still fires on every page. Hiding can never widen access.
• Internal hardening: the stored config is bounded (slug length, icon URL length, sub-order parents, and a 1 MB aggregate ceiling), and an over-size payload is rejected whole rather than partially written.
• Accessibility: the two role lists in the visibility popover are now programmatically grouped and named, so screen-reader users can tell "hide this item" from "hide its sub-items".
• Fixed: a very long menu name written in a multibyte script (Japanese, Chinese, emoji) is now shortened on a character boundary instead of being cut mid-character.

1.3.1

• Editor restyle: the edit-mode toolbar and controls now look native to wp-admin — quiet, borderless icon buttons replacing the coloured-outline toolbar introduced in 1.2.0. Colour is now reserved for errors and the destructive "Reset All".
• Exit is a single control: the admin-bar "Exit Menu Editor" toggle (the duplicate Exit button in the bottom toolbar is gone). Clicking it saves any pending change before leaving edit mode.
• Quieter save status — a muted "Saved" confirmation, with red shown only when a save fails.
• The controls panel, the icon/visibility popovers, and the first-run tour adopt core wp-admin styling; the first-run banner's text and button are now vertically centered.
• Accessibility: improved contrast for the "Reset All", "Save failed", and "Saved" indicators on dark admin colour schemes (e.g. Midnight).

1.3.0

• Saved overrides now keep applying even when your site moves to a new host, when a plugin updates and changes a version number in its menu URL, when UTM tracking parameters drift on external-tool links, and when a taxonomy slug is stored with & encoding instead of & (or vice versa) — no manual re-save needed.
• Edit-mode toolbar: the Exit and Reset All controls now use clearer, more consistent icons (Exit matches the admin-bar toggle).
• New: a first-run guided tour walks you through editing the menu — selecting an item, the rename/icon/visibility controls, reordering, autosave, and exit. A "?" button in the edit-mode toolbar replays it anytime. (It replaces the previous one-time menu highlight.)
• Fix: while editing, the menu's group separators no longer show as a stray dark band between sections (most noticeable above the Posts group); they collapse so items sit flush. The normal menu is unchanged.

1.2.0

• Redesigned edit-mode toolbar: every control is now a compact icon button in one consistent system, with colour signalling meaning — green for editing/saved, amber for unsaved changes, red for Reset All. Fully accessible: each control keeps its name for screen readers and shows a tooltip on hover.
• Mobile: the editor is reachable on phones now — the admin-bar "Edit Menu" toggle stays visible at small screen widths (it was hidden before), and the toolbar and controls are sized for touch.
• "Edit Mode" indicator: a persistent, glanceable cue that you're editing, plus a one-time first-run hint highlighting the menu.
• Rename: the field shows a placeholder label, and the transient "Saved" confirmation now clears itself after a moment so the toolbar stays quiet.
• Reorder: keyboard (Alt+Arrow) and the new ▲/▼ buttons leave menu separators in place; the per-item Reset button is disabled when there's nothing to undo.
• Robustness: Maestro engages WordPress's menu-order machinery only when you've actually reordered top-level items (otherwise it stays out of other plugins' way); the stored configuration is size-bounded; and concurrent save / reset / exit actions are race-safe.
• Fix: the "modified" indicator now sits on the changed row's label for items that have submenus.

1.1.1

• Editor: the selected item's name is now screen-reader-only — the visible breadcrumb duplicated the rename field and ate horizontal space, and the controls are self-explanatory. Screen-reader users still get the item/submenu context.
• Editor: shorter reset button labels — "Reset Item" and "Reset All".

1.1.0

• Keyboard reordering: select a menu item, then press Alt+ArrowUp / Alt+ArrowDown to move it. Each move is announced to screen readers (politely for success, assertively when already at the boundary). No mouse required.
• Modified indicator: changed items show a non-color glyph (•) with screen-reader text "(modified)" in edit mode. The indicator refreshes live on every rename, icon change, visibility change, and reset.
• Discoverable per-item reset: the Reset this item button in the controls panel is now keyboard-reachable (Tab + Enter/Space) and is visually emphasised whenever the selected item has unsaved overrides.
• Solid bundled icons: the Bootstrap Icons set now uses solid (*-fill) variants, so it mixes naturally with WordPress's dashicons in the picker.
• Edit-mode polish: clearer toolbar grouping, a more scannable icon grid, and a dismissible first-run hint.
• Native save status: the saving / saved / error states now use WordPress dashicons (a spinner, a check, a warning) instead of emoji glyphs that some platforms recoloured or dropped; the idle state shows no icon.
• Fixes: the saved status no longer renders a double check mark; the rename field no longer shifts as the title length changes; toolbar controls wrap instead of overlapping on narrow screens.
• Listing: rewritten description and FAQ, plus a "Try it first" link to a live WordPress Playground demo.

1.0.0

• Initial release: rename, reorder, per-role visibility, reset.
• Icons: accepts all four native WordPress forms (dashicon, none, base64 image data-URI, image URL); picker bundles dashicons + curated Bootstrap Icons with search, keyboard accessibility, and mobile-sized touch targets.
• Editor: click-to-select with a shared panel, debounced single-flight autosave, and folded-mode neutralization.