Merge branch 'main' into dependabot/npm_and_yarn/docroot/design-syste…

…m/ejs-3.1.10

.ddev/mutagen/mutagen.yml

@@ -3,8 +3,8 @@
 # and add your own configuration. If you override it you will
 # probably want to check it in.
 # Please do `ddev mutagen reset` after changing the file.
-# See DDEV Mutagen docs at
-# https://ddev.readthedocs.io/en/stable/users/install/performance/#mutagen
+# See ddev mutagen docs at
+# https://ddev.readthedocs.io/en/latest/users/install/performance/
 # For detailed information about mutagen configuration options, see
 # https://mutagen.io/documentation/introduction/configuration
 sync:

.github/ISSUE_TEMPLATE/change-management-epic.md

@@ -3,7 +3,7 @@ name: Change management
 about: Use this template for planning, coordinating and monitoring activities related
   to VFS-CMS updates that have a medium to high impact on VA employees.
 title: Change management for <insert issue name>
-labels: Needs refining
+labels: Needs refining, sitewide
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/cms-team-member-onboarding.md

@@ -96,10 +96,8 @@ Github + Zenhub are the tools required for sprint boards, epics, estimates, and
 You can view team sprint boards using either the Github view with Zenhub browser extension enabled, or the Zenhub webapp view.
 * CMS team: [Github view](https://github.com/department-of-veterans-affairs/va.gov-cms/#workspaces/vagov-cms-team-5c0e7b864b5806bc2bfc2087/board), [Zenhub webapp view](https://app.zenhub.com/workspaces/vagov-cms-team-5c0e7b864b5806bc2bfc2087/board)
 )
-* Sitewide Facilities and Public Websites teams also run their sprints from the same repository, and any repo / workspace changes should be mindful of not impacting their workspaces / boards: 
-  * Facilities: [Github view](https://github.com/department-of-veterans-affairs/va.gov-cms/#workspaces/sitewide-facilities-639f5253e4b702a32376339e/board), [Zenhub webapp view](https://app.zenhub.com/workspaces/sitewide-facilities-639f5253e4b702a32376339e/board
-)
-  * Public Websites: [Github view](https://github.com/department-of-veterans-affairs/va.gov-cms/#workspaces/public-websites-6171bf4bf43742001af18cc5/board), [Zenhub webapp view](https://app.zenhub.com/workspaces/public-websites-6171bf4bf43742001af18cc5/board)
+* Sitewide team also runs their sprints from the same repository, and any repo / workspace changes should be mindful of not impacting their workspace / board: 
+  * VA.gov Sitewide Product team: [Github view](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new/choose#workspaces/vagov-sitewide-product-team-6645154188a81a1f7a0a9464/board, [Zenhub webapp view](https://app.zenhub.com/workspaces/vagov-sitewide-product-team-6645154188a81a1f7a0a9464/board)
 
 ### Process & Principles
 - [ ] Read about our teams' [Agile / sprint best practices](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/cms/onboarding/library/sprint-best-practices.md)

.github/ISSUE_TEMPLATE/octode-project-board-epic.md

@@ -2,7 +2,7 @@
 name: Sitewide Epic - Web Governance Board
 about: Epic template for Sitewide projects that need to be publicized in the Web Governance Board project view, for Public Websites and Facilities teams.
 title: ""
-labels: Epic
+labels: Epic, sitewide
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/pw-clp-request.md

@@ -3,7 +3,7 @@ name: "(PW) Campaign Landing Page request"
 about: Request a new Campaign Landing Page, owned by Public
   Websites team
 title: 'Campaign Landing Page request: <content info>'
-labels: Needs refining, Public Websites, VA.gov frontend, User support, CLP
+labels: Needs refining, Public Websites, VA.gov frontend, User support, CLP, sitewide
 assignees: jilladams, FranECross
 
 ---

.github/ISSUE_TEMPLATE/pw-forms-bad-pdf-link-pw.md

@@ -2,7 +2,7 @@
 name: "(PW) Forms/Bad PDF link defect"
 about: Forms outages / Bad PDF links, owned by Public Websites team
 title: 'Forms defect: <form name>'
-labels: Defect, Find a form, Needs refining, Public Websites
+labels: Defect, Find a form, Needs refining, Public Websites, sitewide
 assignees: jilladams, FranECross
 
 ---

.github/ISSUE_TEMPLATE/pw-injected-header-publish.md

@@ -2,7 +2,7 @@
 name: "(PW) Injected Header/Footer - publish to prod"
 about: Submit a request to publish the injected header/footer to prod.
 title: 'Injected header/footer: Publish to prod: <domain(s)>'
-labels: Injected header, Needs refining, Public Websites, VA.gov frontend
+labels: Injected header, Needs refining, Public Websites, VA.gov frontend, sitewide
 assignees: jilladams
 
 ---

.github/ISSUE_TEMPLATE/pw-injected-header.md

@@ -2,7 +2,7 @@
 name: "(PW) Injected Header/Footer - prep for testing"
 about: Submit a request to add the injected header/footer an existing site.
 title: 'Injected header/footer: <domain(s)>'
-labels: Injected header, Needs refining, Public Websites, VA.gov frontend
+labels: Injected header, Needs refining, Public Websites, VA.gov frontend, sitewide
 assignees: jilladams
 
 ---

.github/ISSUE_TEMPLATE/pw-issue.md

@@ -2,7 +2,7 @@
 name: "(PW) Issue template"
 about: Issue template for Public Websites team
 title: ''
-labels: Needs refining, Public Websites
+labels: Needs refining, Public Websites, sitewide
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-facility-url-change.md

@@ -2,10 +2,12 @@
 name: Runbook - Facility URL Change
 about: Submit a request to change the URL of a facility
 title: 'URL Change for: <insert facility name>'
-labels: Facilities, Drupal engineering, Redirect request, URL Change, User support, VA.gov frontend
+labels: Facilities, Drupal engineering, Flagged Facilities, Redirect request, URL Change, User support
 assignees: ''
 
 ---
+Parent ticket: #number-of-GH-ticket
+
 ### Implementation date
 When does this request need to be live:
 [MM/DD/YYYY]

.github/ISSUE_TEMPLATE/runbook-nca-facility-closed.md

@@ -2,7 +2,7 @@
 name: Runbook - NCA Facility closed
 about: Steps for archiving a NCA facility in VA.gov CMS.
 title: 'NCA Facility closed: <insert_name>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, NCA
+labels: Change request, Drupal engineering, Facilities, User support, Flagged Facilities, NCA
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-nca-facility-name-change.md

@@ -2,7 +2,7 @@
 name: Runbook - NCA Facility name change
 about: Steps for updating names and URLs
 title: 'NCA Facility name change: <insert_name>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, NCA
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, NCA
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-nca-facility-new.md

@@ -2,7 +2,7 @@
 name: Runbook - New NCA Facility
 about: changing facility information in the CMS for NCA facilities
 title: 'New NCA Facility: <insert_name_of_facility>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VBA
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-vamc-facility-closed.md

@@ -2,7 +2,7 @@
 name: Runbook - VAMC Facility closed
 about: Steps for archiving a VAMC facility in VA.gov CMS.
 title: 'VAMC Facility closed: <insert_name>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VAMC
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC
 assignees: ''
 
 ---
@@ -58,7 +58,7 @@ If this facility has been removed from VAST in error, please notify the VA Drupa
 [outro]
 
 [CMS helpdesk signature]
-   
+
 Alternative, for "Removed From Source" flag follow-up:
 -----------------------
 During a site-wide review, our team found a location within the [INSERT SYSTEM NAME] health care system that is no longer listed within the Facilities API, but still exists within Drupal.
@@ -69,26 +69,26 @@ Here is a link to the clinic homepage, which is still published on the live site
 
 Here is a link to this page on the production site:  [INSERT CLINIC HOMEPAGE LINK FROM PRODUCTION SITE]
 
-IF THIS FACILITY IS CLOSED: 
+IF THIS FACILITY IS CLOSED:
 Please follow the steps listed in the following Knowledge Base article in order to fully archive it from VA.gov: https://prod.cms.va.gov/help/vamc/about-locations-content-for-vamcs/how-to-archive-a-closed-facility
 
-Important: Once these steps have been followed, please reach back out to the VA Drupal CMS Help Desk by replying to this email or by writing to [email protected]. 
+Important: Once these steps have been followed, please reach back out to the VA Drupal CMS Help Desk by replying to this email or by writing to [email protected].
 
 From there, our engineering team will proceed with next steps for archiving this facility.
 
 If the clinic has not been closed, please also let our team know as soon as possible.
 
 Thank you for your help!
-   
+
 [Signature]
-   
+
 ```
 </details>
 
 - [ ] 4. Are any of the services or upcoming events for the facility to be closed moving to a different facility?
   - [ ] 4a. If so, note the facility picking up the services and events here: <insert_target_facility>
   - [ ] 4b. If so, note the services and events here: <insert_services_to_be_moved>
-- [ ] 5. Create a [redirect request](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&labels=Redirect+request&template=redirect-request-facility-url.md&title=Redirect+Request+for%3A+%3Cinsert+facility+name%3E) from the URL of the facility to be closed to the URL of its parent system.
+- [ ] 5. Create a [URL change](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&template=runbook-facility-url-change.md&title=URL+Change+for%3A+%3Cinsert+facility+name%3E) to redirect the from the URL of the facility to be closed to the URL of its parent system and to remove the old canonical link.
 
 <insert_redirect_request_link>
 

.github/ISSUE_TEMPLATE/runbook-vamc-facility-duplicate-or-section-change.md

@@ -2,7 +2,7 @@
 name: Runbook - VAMC facility duplicate record or section change
 about: How to update the section of a VAMC.
 title: 'VAMC Facility duplicate record or section change: <insert_name_of_vamc>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VAMC
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-vamc-facility-name-change.md

@@ -2,7 +2,7 @@
 name: Runbook - VAMC Facility name change
 about: Steps for updating names and URLs
 title: 'VAMC Facility name change: <insert_name>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VAMC
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-vamc-facility-new.md

@@ -2,7 +2,7 @@
 name: Runbook - New VAMC Facility
 about: changing facility information in the CMS for VAMC facilities
 title: 'New VAMC Facility: <insert_name_of_facility>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VAMC
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC
 assignees: ''
 
 ---
@@ -31,10 +31,11 @@ Please refer to the Knowledge Base article titled "How do I add a facility to my
 
 #### CMS help desk steps
 **Note: If the help desk is waiting on information from the facility staff or editor, add the "Awaiting editor" flag to the facility with a log message that includes a link to this ticket. Remove the flag when the ticket is ready to be worked by the Facilities team. Be sure to preserve the current moderation state of the node when adding or removing the flag.**
-- [ ] 1. Become aware that the new facility is now on the Facility API (typically, via a Flag, but this may come in as a helpdesk ticket).
-- [ ] 2. If the editor has followed the steps from the above Knowledge Base article and included which section and VAMC the facility belongs to (i.e. VA Pittsburgh), great! **Proceed to step 3.** If not, please check with the editor or VHA digital media regarding what section and VAMC it belongs to.
-- [ ] 3. Updates the Section (default is "VAMC facilities", but it should be a VAMC system in a VISN) and VAMC system field accordingly.
-- [ ] 4. Communicate with editor (cc VHA Digital Media) to give them go-ahead to complete the content, with this [KB article](https://prod.cms.va.gov/help/vamc/about-locations-content-for-vamcs/how-do-i-add-a-facility-to-my-health-care-system). (See sample notification email below)
+- [ ] Become aware that the new facility is now on the Facility API (typically, via a Flag, but this may come in as a helpdesk ticket).
+- [ ] If the editor has followed the steps from the above Knowledge Base article and included which section and VAMC the facility belongs to (i.e. VA Pittsburgh), great!
+  - If not, please check with the editor or VHA digital media regarding what section and VAMC it belongs to.
+    - [ ] Update the Section (default is "VAMC facilities", but it should be a VAMC system in a VISN) and VAMC system field accordingly.
+- [ ] Communicate with editor (cc VHA Digital Media) to give them go-ahead to complete the content, with this [KB article](https://prod.cms.va.gov/help/vamc/about-locations-content-for-vamcs/how-do-i-add-a-facility-to-my-health-care-system). (See sample notification email below)
 
 <details><summary>Email template </summary>
 
@@ -52,23 +53,23 @@ Please let us know when your draft content is complete, so that we can wrap up t
 
 </details>
 
-- [ ] 5. Create a [URL change request](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/new?assignees=&template=runbook-facility-url-change.md&title=URL+Change+for%3A+%3Cinsert+facility+name%3E), changing the entry from the old facility URL to the new facility URL. (**Note: The URL change request ticket blocks the completion of this ticket.**)
+- [ ] When editor has prepared content and let help desk know, proceed to the remaining steps.
 
-<insert_url_change_request_link>
 
-- [ ] 6. When editor has prepared content and let help desk know, reassign this issue to appropriate CMS engineer on Product Support team, for bulk publishing.
-
-#### CMS engineer steps
-- [ ] 7. CMS engineer executes the steps of the URL change request ticket from step 5 above.
-
-(Redirects deploy daily except Friday at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)
-
-#### Drupal Admin steps (CMS Engineer or Help desk)
-_Help desk will complete these steps or escalate to request help from CMS engineering._
-- [ ] 8. Drupal Admin bulk publishes nodes and facility.
-- [ ] 9. Drupal Admin edit facility node and remove `New facility` flag and save node.
-- [ ] 10. Let Help desk know this has been done, if not done by Help desk.
+#### Drupal Admin steps (CMS Engineer or Help desk) _Help desk will complete these steps or escalate to request help from CMS engineering._
+- [ ] Update the facility **Meta description** field, using the following format: "Get address and hours, parking and transportation information, and health services offered at [facility name]."
+- [ ] Move the facility link in the health care system menu to its place in the alphabetized list (medical centers first, then clinics).
+- [ ] Drupal Admin bulk publishes nodes and facility.
+- [ ] Drupal Admin edit facility node and remove `New facility` flag and save node.
+- [ ] Contact Lighthouse via Slack at #cms-lighthouse channel that this facility requires a canonical link in the following format (replacing the placeholder data with the actual API Id and VA.gov URL):
+  - `vha_691GM,https://www.va.gov/greater-los-angeles-health-care/locations/oxnard-va-clinic/`
+- [ ] Add the "Awaiting CSV" flag to the facility node with a revision log message that includes a link to this ticket.
+- [ ] Let Help desk know this has been done, if not done by Help desk.
 
+#### Wait (days or weeks, potentially)
+- [ ] After the canonical link has been added to the websites.csv and you have confirmation from Lighthouse that the CSV has been deployed, validate that the change has deployed by checking that the Facility Locator has been updated with the new url.
+- [ ] Update this ticket with a comment that the CSV change has been deployed.
+- [ ] Remove the "Awaiting CSV" flag to the facility node with a revision log message that includes a link to this ticket.
 
 #### CMS Help desk (wrap up)
-- [ ] 11. Notify editor and any other stakeholders.
+- [ ] Notify editor and any other stakeholders.

.github/ISSUE_TEMPLATE/runbook-vamc-system-name-change.md

@@ -2,7 +2,7 @@
 name: Runbook - VAMC system name change
 about: How to update the name of a VAMC.
 title: 'VAMC system name change: <insert_name_of_vamc>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VAMC
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-vba-facility-closed.md

@@ -2,7 +2,7 @@
 name: Runbook - VBA Facility closed
 about: Steps for archiving a VBA facility in VA.gov CMS.
 title: 'VBA Facility closed: <insert_name>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VBA
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-vba-facility-name-change.md

@@ -2,7 +2,7 @@
 name: Runbook - VBA Facility name change
 about: Steps for updating names and URLs
 title: 'VBA Facility name change: <insert_name>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VBA
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-vba-facility-new.md

@@ -2,7 +2,7 @@
 name: Runbook - New VBA Facility
 about: changing facility information in the CMS for VBA facilities
 title: 'New VBA Facility: <insert_name_of_facility>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, VBA
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/runbook-vet-center-cap-to-outstation.md

@@ -2,7 +2,7 @@
 name: Runbook - Vet Center CAP becomes an Outstation
 about: Steps for upgrading a CAP to an Outstation
 title: 'Vet Center CAP becomes an Outstation: <insert_name_of_facility>'
-labels: Change request, Drupal engineering, Facilities, User support, VA.gov frontend, Vet Center
+labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, Vet Center
 assignees: ''
 
 ---