starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Enable ability to skin the title of a model for greater customization #2752

New Issue
Closed
opened 2025-12-29 18:21:46 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:21:46 +01:00
Owner
Copy Link

Originally created by @Xelinor on GitHub (Jul 23, 2019).

Proposed Functionality

Allow re-naming (skinning) of the models in Netbox from the Admin console so that they display under different names on the web front end

Use Case

'Tenants' is an overloaded term in my company. In my production environment, I go into the HTML template and essentially skin it so that it shows up as 'Environments' instead. It's still tenants in the back-end, just the front end appears to show differently to users because to them, a 'Tenant' is an entirely different thing in our business, and it was extremely confusing for our users.

I believe this functionality could be baked into the admin page to allow skinning for several of the models. Someone might want to change 'Sites' to 'Campus' or 'Floor', for example, or regions to 'Building'. The purpose is for better clarity of terms.

There are plenty of use cases where various organizational types are re-purposed by users, giving the admins the ability to change that in the UI would save a lot of time.

Database Changes

A table would need to be added that would give the 1 to 1 correlation between the real name and the fake name so that the django template could call it correctly on render...other then that, no changes needed.

External Dependencies

None. This can be done with Django templating.

Originally created by @Xelinor on GitHub (Jul 23, 2019). ### Proposed Functionality Allow re-naming (skinning) of the models in Netbox from the Admin console so that they display under different names on the web front end ### Use Case 'Tenants' is an overloaded term in my company. In my production environment, I go into the HTML template and essentially skin it so that it shows up as 'Environments' instead. It's still tenants in the back-end, just the front end appears to show differently to users because to them, a 'Tenant' is an entirely different thing in our business, and it was extremely confusing for our users. I believe this functionality could be baked into the admin page to allow skinning for several of the models. Someone might want to change 'Sites' to 'Campus' or 'Floor', for example, or regions to 'Building'. The purpose is for better clarity of terms. There are plenty of use cases where various organizational types are re-purposed by users, giving the admins the ability to change that in the UI would save a lot of time. ### Database Changes A table would need to be added that would give the 1 to 1 correlation between the real name and the fake name so that the django template could call it correctly on render...other then that, no changes needed. ### External Dependencies None. This can be done with Django templating.
adam closed this issue 2025-12-29 18:21:46 +01:00
adam commented 2025-12-29 18:21:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 23, 2019):

This is not something that can be undertaken without an unreasonable amount of developer effort, and ultimately would only lead to confusion.

@jeremystretch commented on GitHub (Jul 23, 2019): This is not something that can be undertaken without an unreasonable amount of developer effort, and ultimately would only lead to confusion.
adam commented 2025-12-29 18:21:47 +01:00
Author
Owner
Copy Link

@Xelinor commented on GitHub (Jul 23, 2019):

This is not something that can be undertaken without an unreasonable amount of developer effort

Maybe I'm confused about this, but at least how I imagined this being accomplished, this should be as simple as adding a django template tag with a very simple text replacement function to the navigation menus and table headers, a very very small and repeatable change...is there a gotcha I'm not aware of somewhere? I do basically do this already in my own Netbox, just hard-coding the replacement template tag rather then making it part of the admin page...

(To be clear, not arguing about the decision, it was just something I figured might add value but it definitely could add confusion, just wondering if I'm missing something now that might bite me later?)

@Xelinor commented on GitHub (Jul 23, 2019): > This is not something that can be undertaken without an unreasonable amount of developer effort Maybe I'm confused about this, but at least how I imagined this being accomplished, this should be as simple as adding a django template tag with a very simple text replacement function to the navigation menus and table headers, a very very small and repeatable change...is there a gotcha I'm not aware of somewhere? I do basically do this already in my own Netbox, just hard-coding the replacement template tag rather then making it part of the admin page... (To be clear, not arguing about the decision, it was just something I figured might add value but it definitely could add confusion, just wondering if I'm missing something now that might bite me later?)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2752
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?