Skip to content
This repository has been archived by the owner on May 6, 2024. It is now read-only.

Landing page for multiple life events #579

Closed
1 of 17 tasks
r-bartlett-gsa opened this issue Dec 14, 2022 · 11 comments
Closed
1 of 17 tasks

Landing page for multiple life events #579

r-bartlett-gsa opened this issue Dec 14, 2022 · 11 comments

Comments

@r-bartlett-gsa
Copy link
Contributor

r-bartlett-gsa commented Dec 14, 2022

As a benefits tool user, in order to navigate between USAGov and benefits tool subsite without confusion, I would like the benefit tool subsite to resemble USAGov as close as possible and life experiences to be seamlessly integrated to appropriate USAGov content.

Note: currently when multiple life experiences are turned on, BEARS nav displays instead of USAGov nav and a landing page exist with links to all life experiences.

Acceptance Criteria:

  • When multiple life experiences are enabled:
    • the users are not able to navigate to BEARS legacy landing page
    • the header, main nav and footer are the same as on a single-life experience (replicated USAGov's header, main nav and footer; additional header, main nav and footer changes are described in separate user stories: Header updates #580, Main nav updates #581, Footer updates #582)

Definition of Done:

  • Code complete
  • Tests coverage is greater than team benchmark (90% goal)
  • Security scans passed
  • Acceptance Criteria is met and it works as expected
  • Accessibility tested
  • Cross browser tested
  • Build process and deployment is automated and repeatable
  • Load testing/performance testing
  • Self Documentation whenever possible
  • Feature toggles if appropriate
  • Deployed to staging
  • Usability testing
  • PR approved / Peer reviewed
  • A11y tested by Meghan
  • PO approved (UX, usability, edge cases)

More details about each item can be find in BEARS P4 DoD google doc

QA checklist

@fpigeonjr
Copy link
Contributor

@r-bartlett-gsa @erniedeeb:
Was thinking about this today and was wondering what should we do if the user naviagtes to the root of the site?
Maybe we just redirect to the death-of-a-loved-one life event like we do in the in the single life event version?

also tangentially-related, do we want to remove the pages for benefits by type and benefits by agency since it sounds like the user will never see these?

SCR-20230117-cmn

@r-bartlett-gsa
Copy link
Contributor Author

Great questions @fpigeonjr! I'm thinking that all (root/benefits by life event, benefits by type and benefits by agency) should redirect to either https://beta.usa.gov/benefits or https://www.usa.gov/benefits. Considering that we are preparing to launch additional life events, it does not seem correct to redirect all to a single bereavement life event. Also, this is assuming that the benefit page page on USAGov will have appropriate links to BEARS life events.

What are your thoughts @erniedeeb?

@fpigeonjr
Copy link
Contributor

maybe something like this?
SCR-20230117-dj4

@r-bartlett-gsa
Copy link
Contributor Author

@fpigeonjr I'm not sure if I fully understand the diagram above (or agree with it). I was thinking that:
benefit-tool-beta.usa.gov redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/types redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/agencies redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/becoming-a-parent redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/financial-hardship redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/military-service redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/national-emergency-and-disaster redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/school-and-education redirects to usa.gov/benefits
benefit-tool-beta.usa.gov/death-of-a-loved-one does not redirect
benefit-tool-beta.usa.gov/retirement does not redirect
benefit-tool-beta.usa.gov/disability does not redirect

@fpigeonjr
Copy link
Contributor

updated the diagram to make it a little easier to understand.
SCR-20230117-ezj

@erniedeeb
Copy link

Good convo here. I'd want the redirect to beta pages instead of the old usa.gov. So either https://www.beta.usa.gov/benefits or https://www.beta.usa.gov/life-experiences should work. I like the latter because it gets people thinking about life events, but the former is more broad and might be more helpful. A concern with the former though is that benefits.gov is front and center, which may end up pulling people away from benefits locator. What do you think @r-bartlett-gsa?

@r-bartlett-gsa
Copy link
Contributor Author

r-bartlett-gsa commented Jan 19, 2023

@erniedeeb
I'm leaning more towards life-experiences page on beta.usa.gov, it would be more in line with BEARS approach, however the life experiences don't exactly match up. As it is today, the user will not be able to get to disability benefits from https://beta.usa.gov/life-experiences We don't want to introduce additional barriers for the users to get to the information they need. As BEARS additional life experiences are released, will usa.gov update this page?

@danny-englander
Copy link
Contributor

We'd like our UX person, Ernesto, who just came on to the project to give this a full review.

@r-bartlett-gsa
Copy link
Contributor Author

@danny-englander It will also be beneficial for Ernesto to review the documents in this folder: https://drive.google.com/drive/folders/1QuQ5rGRXrpdfYG5pKS0yjaOecDEzUW9S?usp=share_link

danny-englander added a commit that referenced this issue Jan 27, 2023
danny-englander added a commit that referenced this issue Jan 27, 2023
danny-englander added a commit that referenced this issue Jan 30, 2023
@fpigeonjr fpigeonjr mentioned this issue Feb 6, 2023
16 tasks
@fpigeonjr
Copy link
Contributor

I have completed my involvement with this GitHub issue and am stepping away from it.
Thank you for your understanding.

@danny-englander danny-englander changed the title Landing page and main nav changes for multiple life events Landing page for multiple life events Mar 10, 2023
@danny-englander
Copy link
Contributor

Since we won't have a landing page anymore in V1 of the app, this is no longer relevant so going to close.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants