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

Improve efficiency of UI layout #5492

New Issue
Closed
opened 2025-12-29 19:28:39 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:28:39 +01:00
Owner
Copy Link

Originally created by @dreng on GitHub (Oct 8, 2021).

NetBox version

v3.0.6

Feature type

Change to existing functionality

Proposed functionality

The new UI offers a modern look but wastes a lot of space. This leads to a view where information seems to become less important than buttons and search fields. I'd like to ask if it is possible to consolidate some parts in order to get back space for interesting data.

Furthermore the font is (and has always been) quite big. I reduce the browser view to 80% since I use netbox in order to see more information. Reducing the font size is not absolutely necessary since it is always possible to reduce the browser view. Nevertheless I integrated the reduction into the following mockup.

This is what I propose:

Original new UI
2021-09-23 09_58_26-Devices _ NetBox

Original new UI reduced to 80%
2021-09-23 10_01_00-Devices _ NetBox

Consolidated new UI reduced to 80%
2021-09-23 10_13_05-Devices _ NetBox

Please notice that you can see only 10 lines of data in the original view but 17 with the proposed change.

Use case

The proposed change leaves more space for the information you're interested in.

Database changes

No response

External dependencies

No response

Originally created by @dreng on GitHub (Oct 8, 2021). ### NetBox version v3.0.6 ### Feature type Change to existing functionality ### Proposed functionality The new UI offers a modern look but wastes a lot of space. This leads to a view where information seems to become less important than buttons and search fields. I'd like to ask if it is possible to consolidate some parts in order to get back space for interesting data. Furthermore the font is (and has always been) quite big. I reduce the browser view to 80% since I use netbox in order to see more information. Reducing the font size is not absolutely necessary since it is always possible to reduce the browser view. Nevertheless I integrated the reduction into the following mockup. This is what I propose: Original new UI ![2021-09-23 09_58_26-Devices _ NetBox](https://user-images.githubusercontent.com/20901110/136511292-9f5ad6ef-1a39-4bab-be9a-532a5f238bd5.png) Original new UI reduced to 80% ![2021-09-23 10_01_00-Devices _ NetBox](https://user-images.githubusercontent.com/20901110/136511302-c493be8e-a524-423d-a3a6-bd5a1126d969.png) Consolidated new UI reduced to 80% ![2021-09-23 10_13_05-Devices _ NetBox](https://user-images.githubusercontent.com/20901110/136511309-7728725a-f24c-4fa5-899e-e4368b2b02c7.png) Please notice that you can see only 10 lines of data in the original view but 17 with the proposed change. ### Use case The proposed change leaves more space for the information you're interested in. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:28:39 +01:00
adam closed this issue 2025-12-29 19:28:39 +01:00
adam commented 2025-12-29 19:28:40 +01:00
Author
Owner
Copy Link

@teixemf commented on GitHub (Oct 12, 2021):

I would like to mention #6925 could also help to recall some UI space.

@teixemf commented on GitHub (Oct 12, 2021): I would like to mention #6925 could also help to recall some UI space.
adam commented 2025-12-29 19:28:40 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Oct 22, 2021):

After long testing I've migrated to v3. And I have to applaud the NetBox team that they have managed to save space in the horizontal direction for the main tables. Even with the menu now vertical, it is astonishing!

But it can always be improved - especially in the vertical direction as some of the suggestions in the OP.

I for one would definitely not want to have the "filter" or whatever it is (item labeled as "1" in the OP last screenshot) take horizontal space away from the tables!

When viewing data tables there should be no UI elements on the side of the data table - they should be at top/bottom.

Horizontal screen real estate is the most precious commodity and it should not be wasted to UI elements wherever possible, it should be saved for data such as the tables. IMHO only when editing something UI elements could be at left/right since most of the horizontal space is padding anyways.

While testing v3 I also initially played around with scaling the whole NetBox site to something less than 100%. I wonder if it would be possible to have a configurable setting for the "base size" of the NetBox UI - something that currently is done with browser zoom functionality? That would put to bed the question of what is the right font size/scaling.

And in general when viewing data tables of course there should be only the absolute minimum padding & margin in my opinion.

@bluikko commented on GitHub (Oct 22, 2021): After long testing I've migrated to v3. And I have to applaud the NetBox team that they have managed to _save_ space in the horizontal direction for the main tables. Even with the menu now vertical, it is astonishing! But it can always be improved - especially in the vertical direction as some of the suggestions in the OP. I for one would **definitely not** want to have the "filter" or whatever it is (item labeled as "1" in the OP last screenshot) take horizontal space away from the tables! When viewing data tables there should be no UI elements on the side of the data table - they should be at top/bottom. Horizontal screen real estate is the most precious commodity and it should not be wasted to UI elements wherever possible, it should be saved for data such as the tables. IMHO only when editing something UI elements could be at left/right since most of the horizontal space is padding anyways. While testing v3 I also initially played around with scaling the whole NetBox site to something less than 100%. I wonder if it would be possible to have a configurable setting for the "base size" of the NetBox UI - something that currently is done with browser zoom functionality? That would put to bed the question of what is the right font size/scaling. And in general when viewing data tables of course there should be only the absolute minimum padding & margin in my opinion.
adam commented 2025-12-29 19:28:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 12, 2021):

Tagging this as needs owner for anyone who would like to propose specific improvements.

@jeremystretch commented on GitHub (Nov 12, 2021): Tagging this as `needs owner` for anyone who would like to propose specific improvements.
adam commented 2025-12-29 19:28:40 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 12, 2022):

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.

@github-actions[bot] commented on GitHub (Jan 12, 2022): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:28:40 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 11, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Feb 11, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner type: feature
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#5492
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?