Add new sites to use the Injected Header/Footer: ptsd.va.gov; mirecc.va.gov; mentalhealth.va.gov #20329
Labels
Header/footer
Owned by Sitewide Public Webites
Public Websites
Scrum team in the Sitewide crew
sitewide
VA.gov frontend
CMS team practice area
Description
The VCL modal on the TeamSite header for these sites is not currently working, so it was requested by Josh Tuscher (VAHELP-8452) that 3 sites be added to use the injected header/footer.
Production url:
Please handle both www and non-www versions of the URL.
Tasks
Public Websites team will need to:
add the domain with both www and non-www to the proxy-rewrite-whitelist.json allow list, with
"cookieOnly": true
for staging testing. - .5hradd the domain to Devops code that handles the TeamSite CORS allowed origins for
bucket-prod-va-gov-assets
andbucket-preview-va-gov-assets
. The buckets are now part of the vets-api module, so you just need to make sure any needed origins are in the local allowed_origins list: https://github.com/department-of-veterans-affairs/devops/blob/master/terraform/environments/dsva-vagov-prod/main.tf#L274 - .5hrPR shepherding - .5-1hr
2-2.5hrs
Additional context
DEPO teamsite overview - explains the mechanisms, and has notes on testing, for the implementing team. (And has an incorrect code pointer, ticketed here: department-of-veterans-affairs/va.gov-team#43364)
After PW updates allowlists, the requesting team will need to test on Staging by setting a cookie in browser, per the TeamSite docs. The main issues are styling related, where styles from the site may affect the presentation of the header/footer. Those issues can/should be fixed by updating the CSS of the site / app (rather than by modifying styles for the header / footer globally). This is the bulk of their work, and if no style issues occur, it could potentially be a no-op. Once requesting team confirms that the injected header/footer work and they're ready to publish, PW will manage a separate issue to update code to
cookieOnly: false
in order to permanently expose the header/footer on the site.To test
Acceptance Criteria
The text was updated successfully, but these errors were encountered: