UI/UX: Navigation: header/footer pattern for unauthenticated area — scannability and `Sign In` salience [RC26Q2-F16]

[thlpkee20-wq]

Description

Navigation: header/footer pattern for unauthenticated area — scannability and Sign In salience — UI/UX and product design for Revora-Frontend (React, Vite, TypeScript). This is not a “generic frontend feature” ticket: focus on information architecture, accessibility, responsive layout, and copy. No new backend or Soroban work unless a mock is strictly required. Deliverables: states, flows, and implementation notes. Scope = UI/UX, not Revora-Backend.

Requirements and context

• Conform to existing glass-card, btn-primary, and Tailwind/utility style in the tree.
• Clarify WCAG-oriented choices (contrast, focus, labels) in the PR.

Suggested execution

• Fork the repo, then:

  • git checkout -b ux16-navigation--header-footer-pattern-for-unauthenti

• Relevant modules: src/pages/Login.tsx, src/pages/Signup.tsx, src/pages/ForgotPassword.tsx, src/components/AuthLayout.tsx, src/App.tsx, global styles.

• Implement and verify

  • Branch: git checkout -b ux16-navigation--header-footer-pattern-for-unauthenti
  • Update src/pages/, src/components/, App.tsx as needed; no unrelated refactors.
  • If the repo has no Storybook, use PR text + structured checklist; otherwise follow repo patterns.

• Test and document

  • Add or extend automated tests; cover edge cases and invariants
  • Document security assumptions; include test output summary and a short security / risk note in the PR
  • For Revora-Contracts (Soroban): cargo test, cargo clippy, rustdoc/NatSpec-style entrypoint docs where applicable. Do not implement Solidity; this work targets Rust/WASM in this repository.
  • For Backend / Frontend: follow the repo’s existing Jest/TS/ESLint/Vite setup.
  • Example commit message: ux(frontend): navigation: header/footer pattern for un

Labels and GitHub label colors

• Create the labels in this issue’s labels: line under Settings → Labels in the target repo.
• Assign distinct colors (avoid all grey): e.g. #0052CC (blue, platform), #B60205 (red, security), #0E8A16 (green, tests), #5319E7 (purple, P1), #F9D0C4 (scope), #1D76DB (api), #BFD4F2 (docs) — pick a non-default palette so issues are scannable in the board.

Guidelines

• Target ≥ 95% test coverage for new or materially changed code paths
• Clear, linked documentation in-repo
• Timeframe: 96 hours from assignment

[Enemuo-debug]

@Enemuo-debug has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Can I please work on this?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Enemuo-debug to this issue.

[Icebear-16]

@Icebear-16 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I'd really love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Icebear-16 to this issue.

[MKNas01]

@MKNas01 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Let me work on this issue too and make the PRs immediately for review

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MKNas01 to this issue.