[2024-08-08] [Fran] Randi has finished forking and releasing the code. Only two tickets left; documentation and removing flipper.
[2024-03-12] - Randi has completed all but the auth portion, which the DST team will be handling. They will prioritize their tickets soon.
[2024-02-20]
This epic created to house all injected header tickets
Randi has completed all work except for fonts, which remain problematic. She has requested that the Design team look attempt this work.
The Design Team will be working on the Authenticated portion of the injected header.
We can't link the Design Team's tickets to our repo. They are noted below.
Note that as of the week of 2/14, the work on the new header is on hold per the OFCIO.
Description
This epic is in support of the new Federal Header/Footer initiative, in that the Injected Header/Footer needs to be forked so that code isn't updated when the new header/footer is implemented/released.
AS A PO/PM who manages the TeamSites injected header/footer
I WANT to experience no issues in using those features regardless of updates to the new header/footer
SO THAT Veterans, their caregivers, family members and survivors don't experience any adverse visual or usability issues when the new header/footer is released or worked on.
Engineering notes / background
Analytics considerations
Quality / testing notes
Acceptance criteria
[ ] Design team tickets are completed and verified
[ ] PW team's code is released in cooperation with the Design Team's code
Statuses
Status
[2024-08-08] [Fran] Randi has finished forking and releasing the code. Only two tickets left; documentation and removing flipper. [2024-03-12] - Randi has completed all but the auth portion, which the DST team will be handling. They will prioritize their tickets soon. [2024-02-20]
Description
This epic is in support of the new Federal Header/Footer initiative, in that the Injected Header/Footer needs to be forked so that code isn't updated when the new header/footer is implemented/released.
Design Team's Tickets
User story
AS A PO/PM who manages the TeamSites injected header/footer I WANT to experience no issues in using those features regardless of updates to the new header/footer SO THAT Veterans, their caregivers, family members and survivors don't experience any adverse visual or usability issues when the new header/footer is released or worked on.
Engineering notes / background
Analytics considerations
Quality / testing notes
Acceptance criteria