-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow plugins to inject top-level navigation menu items #9071
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide. |
I thought I'd revisit this now that a couple of months have passed and I implemented our plugin at two customers and in my own environment. A complaint that I hear quite often is that access to plugins is somewhat hidden from view, which tends to confuse casual users. So I think the option of optionally "promoting" a plugin to be a first class menu entry is still on the wish list. |
There should also be the ability to add our plugin menu under the existing headers like |
NetBox version
v3.2.0
Feature type
Change to existing functionality
Proposed functionality
Currently, plugins can define menu items only under the "Plugins" header within the navigation menu. Several plugin authors have proposed the ability for a plugin to "register" its own top-level section in the menu.
IMO the simplest approach would be to allow a plugin to define a menu heading with a title and icon. If defined, its menu items will appear there; if not, they will appear under the general "Plugins" heading.
We'd also want to give some thought to influencing the ordering of top-level menu items; assigning a "weight" to each item might suffice.
Use case
Greater visibility for plugin functions; control over order of placement (potentially?)
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: