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

Deploy Multi-life event feature branch (loss of a loved one only) with the new design on usa.gov #717

Closed
danny-englander opened this issue Apr 10, 2023 · 0 comments · Fixed by #661
Assignees
Labels

Comments

@danny-englander
Copy link
Contributor

danny-englander commented Apr 10, 2023

User Story

As a developer, I need to deploy the Multi-life event feature branch to production. The branch for this deploy will be multi-life-event-2023 https://github.com/GSA/usagov-benefits-eligibility/tree/multi-life-event-2023

Description

We will need to deploy the Multi-life event feature branch to production as it will have the new USA gov design as well as updated header and footer links, updated logos, and removal of the header beta message. See all the related tickets below for any questions about this.

The PR for this deploy below is for a single life event (loss of a loved one) but with the multi-life event capability and the new usa.gov design. See #674 and #652 for adding in the CrossSell component back in for true Multi-life event capability once these are set.

To deploy, Follow the steps in "Developer documentation for BEARS Task 3" on Gdrive.

Key point

It will be important that usa.gov do not yet link to our disability and retirement pages. Internally in the Bears app, there will not yet be links to those pages, i.e. #652 but just noting this for reference.

PR

Multi-life event feature branch #661

Related tickets

10x project phase 4 issues

@danny-englander danny-englander changed the title Deploy Multi-life event feature branch Deploy Multi-life event feature branch (loss of a loved one only) with the new design on usa.gov Apr 12, 2023
@scottqueen-bixal scottqueen-bixal linked a pull request Apr 27, 2023 that will close this issue
18 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants