Skip to content

Move the Gateway config UI nav back to the top - #165

Merged
julioest merged 1 commit into
cppalliance:masterfrom
julioest:143-top-nav
Oct 21, 2026
Merged

julioest merged 1 commit into
cppalliance:masterfrom
julioest:143-top-nav

Conversation

@julioest

@julioest julioest commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Moves the primary nav from the left column back into the header, per Cynthia's feedback on #159. No CSS changes: the cells, colors and sizes are what's on master.

  • Move the seven nav links into the header, between the profile switcher and the status cluster
  • Drop the nav column so the content starts at the left edge
  • Turn the group dividers vertical for the row
  • Give the links their own row under 1024px so none get cut off; icons only under 710px, same as before

Preview

Click through it here: https://runvil-gateway-165.ngrok.app (fake data, nothing real behind it; temporary, so it may be offline)

Before After
1-before-local 1-after-local

Under 1024px the links take their own row:
4-after-860px-apply

Testing

  • npm test (211 pass) and tsc --noEmit in crates/gateway/config-ui/ui
  • cargo clippy -p gateway-config-ui
  • Checked from 1440px down to 390px, with and without Apply/Revert showing: no hidden links, no sideways scroll

The style guide CSS is on hold until the updated mock is ready (see #159).

Part of #143

The primary nav returns to the header strip as a row between the
profile switcher and the right cluster, instead of a column beside
the content. The cells, groups, and colors stay as they are. Under
1024px the nav takes its own row below the switcher and actions so
all seven links stay visible, and under 710px it shows only icons.

@cprevatte cprevatte left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thank you!

@julioest
julioest merged commit ceae9ad into cppalliance:master Oct 21, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants