hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Clean up primary navigation #37

New Issue
Closed
opened 2026-05-21 14:35:25 +02:00 by parkel · 0 comments
parkel commented 2026-05-21 14:35:25 +02:00
Owner
Copy Link

Goal

Make the top navigation reflect the Django control panel as the primary product UI and move secondary/admin-only routes out of the main flow.

Scope

  • Re-evaluate every current top-nav item: Admin, SSH Keys, Self Check, Logs, Purged, Changelog, Status API.
  • Remove or demote Admin from the primary nav if it is only an escape hatch.
  • Group operational/system links in a cleaner way if useful.
  • Keep important operator routes discoverable without making the header feel crowded.
  • Ensure the navigation behaves well on smaller screens.

Acceptance Criteria

  • Primary navigation contains only routes that operators regularly use.
  • Admin remains reachable for staff users, but does not dominate the app flow.
  • Header does not overflow or look cramped on narrower screens.
  • Tests cover the expected nav links for authenticated staff users.
## Goal Make the top navigation reflect the Django control panel as the primary product UI and move secondary/admin-only routes out of the main flow. ## Scope - Re-evaluate every current top-nav item: Admin, SSH Keys, Self Check, Logs, Purged, Changelog, Status API. - Remove or demote Admin from the primary nav if it is only an escape hatch. - Group operational/system links in a cleaner way if useful. - Keep important operator routes discoverable without making the header feel crowded. - Ensure the navigation behaves well on smaller screens. ## Acceptance Criteria - Primary navigation contains only routes that operators regularly use. - Admin remains reachable for staff users, but does not dominate the app flow. - Header does not overflow or look cramped on narrower screens. - Tests cover the expected nav links for authenticated staff users.
parkel added this to the 1.1 milestone 2026-05-21 14:35:25 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label
Milestone
No items
No Milestone 1.1
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#37
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?