Merge branch 'main' into dependabot/composer/mglaman/phpstan-drupal-1…

….2.11

.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-vamc-facility-new.md

@@ -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,21 +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.
-
-#### 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-vet-center-new.md

@@ -8,7 +8,8 @@ assignees: ''
 ---
 
 ## Description
-Use this runbook if: a Vet Centers, Mobile Vet Centers, Vet Center Outstations is flagged as New, OR if an existing facility is flagged as New with a new Facility API ID. (This may happen  if a Vet Center moves districts, or a Mobile Vet Center is reallocated to a different Vet Center.)
+Use this runbook if: a Vet Center, Mobile Vet Center, or Vet Center Outstation is flagged as New, OR if an existing facility is flagged as New with a new Facility API ID.  
+- This may also occur when an Outstation is promoted to main Vet Center or if an existing Mobile Vet Center is reallocated to a different Vet Center 
 
 ## Intake
 - [ ] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media)
@@ -20,7 +21,7 @@ Help desk ticket: <insert_help_desk_link>
 - [ ] Name of submitter (if applicable)
 Submitter: <insert_name>
 
-- [ ] If the submitter is an editor, send them links to any relevate KB articles for the Vet Center product.
+- [ ] If the submitter is an editor, send them links to any relevant KB articles for the Vet Center product.
 KB articles: <insert_kb_article_links>
 
 - [ ] Link to facility in production:
@@ -36,20 +37,22 @@ Facility API ID: <insert_facility_API_ID>
 **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.**
 
 **If a Mobile Vet Center:**
-- [ ] Confirm what Vet Center it belongs to, and set the "Main Vet Center location" field. The parent location may be derived by the Facility ID.
+- [ ] Confirm the Vet Center to which it belongs and and set the "Main Vet Center location" field. The parent location may be derived by the Facility ID.
+- [ ] Follow up with Barb Kuhn/RCS Central office to let her know we've identified this new Mobile unit and confirm the District, Vet Center Director, and Outreach Specialist (names/email addresses) who will be responsible for updates
 - [ ] Contact the Vet Center editor to remind them to (1) add a photo of the Mobile Vet Center and then they can publish when ready and (2) remind them that if this Mobile Vet Center is used by any other facilities to communicate with those Vet Center editors
-- [ ] Consider: Following up with Barb/RCS Central office to be sure that she's aware that the mobile Vet Center is in-flight
 
 **If a Outstation:**
-- [ ] Confirm what Vet Center it belongs to, and set the "Main Vet Center location" field. The parent location may be derived by the Facility ID.
-- [ ] Contact the Vet Center editor to remind them to (1) add a photo of the Outstation and then they can publish when ready
-- [ ] Consider: Following up with Barb/RCS Central office to be sure that she's aware that the Outstation is in-flight
+- [ ] Become aware that the new facility is now on the Facility API (typically, via a Flag).
+- [ ] Confirm the Vet Center to which it belongs and set the "Main Vet Center location" field. The parent location may be derived by the Facility ID.
+- [ ] Follow up with Barb Kuhn/RCS Central office to let her know we've identified the new Outstation and confirm the District, Vet Center Director, and Outreach Specialist (names/email addresses) who will be responsible for updates
+- [ ] Contact the Vet Center editor to remind them to (1) add a photo of the Outstation
+- [ ] If the new Outstation replaces a CAP, the editor should consider updating the operating status for the CAP to direct Veterans to the new location with “as of” date and set a reminder on the calendar to archive the CAP 30 days after the new location has opened   
 
 **If a Vet Center:**
-- [ ] 1. Become aware that the new facility is now on the Facility API (typically, via a Flag).
-- [ ] 2. Check with Readjustment Counseling Services to (1) confirm what district the Vet Center belongs and (2) Identify the Vet Center Director and Outreach Specialist (names/email addresses)
-- [ ] 3. In [Sections taxonomy](https://prod.cms.va.gov/admin/structure/taxonomy/manage/administration/overview), move the Vet Center Section to the appropriate district.
-- [ ] 4. Create accounts (or restrict existing accounts) with editor rights only for Vet Center Director and Outreach Specialist so that they cannot publish on their own.
+- [ ] Become aware that the new facility is now on the Facility API (typically, via a Flag).
+- [ ] Check with Readjustment Counseling Services to (1) confirm what district the Vet Center belongs, (2) identify the Vet Center Director and Outreach Specialist (names/email addresses), (3) confirm the new location isn't a replacement for an existing Outstation
+- [ ] In [Sections taxonomy](https://prod.cms.va.gov/admin/structure/taxonomy/manage/administration/overview), move the Vet Center Section to the appropriate district.
+- [ ] Create account access as directed by RCS. If editors are new to Drupal, create accounts with editor rights only for Vet Center Director and Outreach Specialist so that they cannot publish on their own.
 - [ ] 5. Contact Vet Center Director and Outreach specialist to onboard for training [@TODO write sample email - SEE runbook-vamc-facility-new] **Note: this should include instructions for adding content and preparing for publishing and RCS Central Office should be included as CC**
 - [ ] 6. Add flag `Awaiting editor` to this facility. Note: This is now blocked until RCS Central office approves.
 - [ ] 7. **Once approved by RCS Central Office as complete, proceed to Drupal Admin publishing steps**

READMES/migrations-facility.md

@@ -102,7 +102,11 @@ For these migrations to function, you'll need to obtain a Facility API Key from
 $settings['post_api_endpoint_host'] = 'https://sandbox-api.va.gov';
 $settings['post_api_apikey'] = 'PASTE_KEY_HERE';
 
-$facility_api_urls = ['https://sandbox-api.va.gov/services/va_facilities/v0/facilities/all'];
+$facility_api_urls = [
+  'https://sandbox-api.va.gov/services/va_facilities/v1/facilities?per_page=1000',
+  'https://sandbox-api.va.gov/services/va_facilities/v1/facilities?per_page=1000&page=2',
+  'https://sandbox-api.va.gov/services/va_facilities/v1/facilities?per_page=1000&page=3',
+];
 $facility_api_key = $settings['post_api_apikey'];
 $facility_migrations = [
   'va_node_health_care_local_facility',

composer.json

@@ -80,7 +80,7 @@
         "drupal/entityqueue": "^1.2",
         "drupal/environment_indicator": "^4.0",
         "drupal/epp": "^1.1",
-        "drupal/expirable_content": "1.0.x-dev@dev",
+        "drupal/expirable_content": "^1.0@alpha",
         "drupal/fast_404": "^3.0",
         "drupal/feature_toggle": "^2.0",
         "drupal/field_group": "^3.4",
@@ -225,7 +225,7 @@
         "symfony/phpunit-bridge": "^5.1",
         "symfony/process": "^6.3",
         "symfony/routing": "^6.3",
-        "va-gov/content-build": "^0.0.3497",
+        "va-gov/content-build": "^0.0.3536",
         "vlucas/phpdotenv": "^5.3",
         "webflo/drupal-finder": "^1.0.0",
         "webmozart/path-util": "^2.3",
@@ -555,7 +555,6 @@
         "va:npm": "Run NPM transparently (all arguments will be passed).",
         "va:nuke": "Remove all Composer package and cache directories.",
         "va:phpcbf": "Run PHP Code Beautifier and Fixer transparently (all arguments will be passed).",
-        "va:remove-git-dirs": "Remove .git directories within this directory, e.g. those created by Composer.",
         "va:set-path": "Display a command for updating the path to include `./bin`.",
         "va:ds:drupal": "Build the Drupal theme.",
         "va:ds:storybook": "Build the Storybook.",
@@ -657,11 +656,6 @@
             "# Test the SOCKS proxy.",
             "curl -v --proxy socks5h://127.0.0.1:2001 sentry.vetsgov-internal"
         ],
-        "va:remove-git-dirs": [
-            "# Remove .git directories within this directory, e.g. those created by Composer.",
-            "! ./scripts/should-run-directly.sh || ./scripts/remove-git-dirs.sh",
-            "./scripts/should-run-directly.sh || ddev composer va:remove-git-dirs --"
-        ],
         "va:set-path": [
             "# Run the command output below to set your current terminal PATH variable.",
             "# This will allow you to run any command in the ./bin directory without a path.",