Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide Archive directory pages #2113

Open
38 tasks
r-bartlett-gsa opened this issue Dec 26, 2024 · 0 comments
Open
38 tasks

Hide Archive directory pages #2113

r-bartlett-gsa opened this issue Dec 26, 2024 · 0 comments
Assignees

Comments

@r-bartlett-gsa
Copy link
Member

User story

As a site manager, in order for the site users to access the most up-to-date challenge.gov pages and avoid outdated content, I would like archived pages to not be accessible for the public users.

Examples:
https://www.challenge.gov/archive/root/pages/toolkit/phases/
https://www.challenge.gov/toolkit/mentor-network/ (the content for this page is in the archive directory)

Acceptance Criteria:

  • Content pages in the archive directory are not accessible for the public users
  • Redirects that pull the content from the archived pages are removed

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 - UI rendering is performant on below listed devices/browsers (Tracy or Marni)
    • Windows/Chrome
    • Windows/Edge
    • Mac/Chrome
    • Mac/Safari
    • iOS/Safari
  • 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 r-bartlett-gsa transferred this issue from GSA/Challenge_gov Dec 26, 2024
@r-bartlett-gsa r-bartlett-gsa added this to the Sprint 01/28/25 milestone Jan 15, 2025
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

No branches or pull requests

2 participants