Clean up primary navigation #37

Closed
opened 2026-05-21 14:35:25 +02:00 by parkel · 0 comments
Owner

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.