null/Queue-North-Website
null
/
Queue-North-Website
1
0
Fork 0
Code Issues 27 Pull Requests Packages Projects Releases Wiki Activity

Active nav link should be visually distinct (white or underlined) for current page #164

New Issue
Closed
opened 2026-05-18 09:24:00 -05:00 by null · 1 comment
null commented 2026-05-18 09:24:00 -05:00
Owner
Copy Link

UX Issue

The top navigation should clearly indicate which page the user is currently on. The active link should be white, underlined, or otherwise visually distinct from the other links.

Currently the Header uses text-white/70 for inactive links and text-white underline for active - but the underline may be too subtle or the contrast too low on the navy background.

Location

src/components/layout/Header.jsx - nav link styling

## UX Issue The top navigation should clearly indicate which page the user is currently on. The active link should be white, underlined, or otherwise visually distinct from the other links. Currently the Header uses `text-white/70` for inactive links and `text-white underline` for active - but the underline may be too subtle or the contrast too low on the navy background. ## Location `src/components/layout/Header.jsx` - nav link styling
null added the
P2 Medium
frontend
ux
 labels 2026-05-18 09:30:00 -05:00
null closed this issue 2026-05-18 13:52:24 -05:00
null commented 2026-05-18 13:52:25 -05:00
Author
Owner
Copy Link

Duplicate — addressed in v0.7.3 UI fixes.

Duplicate — addressed in v0.7.3 UI fixes.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
dev
main
v0.8.0
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels   
P0 Critical

Critical — must fix before production. Data loss, security, or outage risk.

  
P1 High

High — should fix soon. Functional bugs, security hardening, data integrity.

  
P2 Medium

Medium — fix in next cycle. Quality of life, robustness, minor security.

  
P3 Low

Low — nice to have. Polish, optimization, minor UX.

  
accessibility

Accessibility issues

  
backend

Server-side code, API, database.

  
bug

Something is broken or behaves incorrectly.

  
content

   
data-integrity

Data consistency, constraints, validation.

  
enhancement

Feature or improvement request

  
frontend

Client-side code, UI components.

  
infra

Docker, deployment, CI/CD, infrastructure.

  
integration

   
owner

Direct feedback from the site owner. Top priority.

  
owner-input

   
performance

Performance or optimization.

  
performance

   
phase-7

   
phase-8

Phase 8 — Deferred enhancements (testimonials, blog, SEO, performance)

  
security

Security vulnerability or hardening.

  
seo

   
ui

UI/visual issues

  
ux

User experience issue.

No Label
P0 Critical
P1 High
P2 Medium
P3 Low
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
performance
phase-7
phase-8
security
seo
ui
ux
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: null/Queue-North-Website#164
No description provided.
Delete Branch "%!s(<nil>)"

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?