ON HOLD Navigation on Pages for Logged-in Users

[r-bartlett-gsa]

Before proceeding with this, investigate the feasibility: https://github.com/GSA/Challenge_platform/issues/30

User Story

As a site user, in order to efficiently orientate and navigate between public site and authenticated site, I would like to consistent access to navigation options from anywhere of the site and an accurate representation of my user status.

Acceptance criteria:

• [ ] When the user is logged in, the Pages header accurately reflects user's authentication status
  • [ ] "Login" button is replaced with "Logout" button
  • [ ] "Create account" button is replaced with "Switch Task" button
• [ ] When the user is logged in, a task-appropriate utility menu is displayed
  • [ ] User's email address is displayed within the utility menu

Definition of Done

Doing (dev team)

• [ ] Code complete
• [ ] Code is organized appropriately
• [ ] Any known trade offs are documented in the associated GH issue
• [ ] Code is documented, modules, shared functions, etc.
• [ ] Automated testing has been added or updated in response to changes in this PR
• [ ] The feature is smoke tested to confirm it meets requirements
• [ ] Database changes have been peer reviewed for index changes and performance bottlenecks
• [ ] PR that changes or adds UI
  • [ ] include a screenshot of the WAVE report for the altered pages
  • [ ] Confirm changes were validated for mobile responsiveness
• [ ] PR approved / Peer reviewed
• [ ] Security scans passed
• [ ] Automate accessibility tests passed
• [ ] Build process and deployment is automated and repeatable
• [ ] Feature toggles if appropriate
• [ ] Deploy to staging

• [ ] Move card to testing column in the board

  Staging

• [ ] Accessibility tested (Marni)
  • [ ] Keyboard navigation
  • [ ] Focus confirmed
  • [ ] Color contrast compliance
  • [ ] Screen reader testing
• [ ] Usability testing: mobile and desktop (Tracy or Marni)
• [ ] Cross browser testing (tool to be determined) (Tracy or Marni)
  • [ ] UI rendering is performant
• [ ] AC review (Renata)
• [ ] Deploy to production (production-like environment for eval capability) (dev team)

• [ ] Move to production column in the board

  Production

• [ ] User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)
• [ ] PO / PM approved (Jarah or Renata)
• [ ] AC is met and it works as expected (Jarah or Renata)
• [ ] Move to done column in the board (Jarah or Renata)

[r-bartlett-gsa]

@stepchud Look into if this is possible when proxying Pages through Rails.