VACMS-20086: Adds code for Manila VA Clinic and removes unused code.

[omahane]

Description

Relates to #20086

Testing done

Manually
Cypress

Screenshots

QA steps

Set up the editor

• Log in as an admin
• Assign QA Content Publisher to the following roles
  • Content creator - VAMC
  • Content publisher
• Assign QA Content Publisher to the following Sections
  • Manila Va Clinic
  • VA Pacific Islands health care

Make sure the Manila path is correct

• Log in as QA Content Publisher

Create an Event in the Manila section

• Choose "---Manila VA Clinic" for Section
• Fill in all required fields
  • Try to choose a non-Manila option for the Where should the event be listed? field
• Save as Published
  • Confirm that you cannot save the node until you choose the Manila option for the Where should the event be listed? field
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain
• Edit the event
  • Save as published
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain

Create a Story in the Manila section

• Choose "---Manila VA Clinic" for Section
• Fill in all required fields
  • Initially, try to choose a non-Manila option for the Where should the story be listed? field
• Save as Published
  • Confirm that you cannot save the node until you choose the Manila option for the Where should the story be listed? field
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain
• Edit the story
• Save as published
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain

Create a News Release in the Manila section

• Choose "---Manila VA Clinic" for Section
• Fill in all required fields
  • Initially, try to choose a non-Manila option for the News releases listing field
• Save as Published
  • Confirm that you cannot save the node until you choose the Manila option for the News releases listing field
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain
• Edit the news release
• Save as published
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain

Create a Staff Profile in the Manila section

• Choose "---Manila VA Clinic" for Section
• Fill in all required fields
  • Initially, try to choose a non-Manila option for the Related office or health care region field
• Save as Published
  • Confirm that you cannot save the node until you choose the Manila option for the News releases listing field
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain
• Edit the news release
• Save as published
• After save, from the event node:view, confirm that the url contains "/manila-va-clinic/" after the domain

Make sure to check for regressions

Create an Event in the VA Pacific Islands health care section

• Choose "---VA Pacific Islands health care" for Section
• Fill in all required fields
• Save as Published
• After save, from the event node:view, confirm that the url DOES NOT contain "/manila-va-clinic/" after the domain
• Edit the event
  • Save as published
• After save, from the event node:view, confirm that the url DOES NOT contain "/manila-va-clinic/" after the domain

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[dsasser]

Code changes look good. I had no problems with the QA test steps as well. Nice work!

[dsasser]

👍

[github-actions]

Checking composer.lock changes...

[va-cms-bot]

Cypress Accessibility Violations

/test-data-quo

ID: button-name
Impact: critical
Tags: cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, ACT, TTv5, TT6.a
Description: Ensures buttons have discernible text
Help: Buttons must have discernible text
Nodes:

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Page introduction' field" data-proofing-help="Add an introduction that helps visitors understand if information on the page is relevant to them."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: .field--name-field-intro-text-limited-html > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Generate a table of contents from major headings' field" data-proofing-help="By checking this box, all h2's below this point on the page will be linked with with anchor links. This helps users navigate content on very long pages. Do not check this box unless there is at least 2 h2's on the page.">
  Impact: critical
  Target: .field--name-field-table-of-contents-boolean > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Main content' field" data-proofing-help="The main body of the page, which appears below the featured content."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: button[data-proofing-help-title="About 'Main content' field"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element's default semantics were not overridden with role="none" or role="presentation"