Improve VAMC system health service content with a focus on "Care we provide"

[kevwalsh]

User Story or Problem Statement

• Care we provide h3s can be "hardened".
• Semantic headings in VAMC system health service are not structured properly in all displays.

Screenshot


Change management triage

The change represented by this user story will:

• [x] Be a site-wide change to appearance or key functionality (such as log-in process)
• [x] Be a specific change that requires more than 30 minutes of work by a user to meet a publishing requirement
• [x] Remove a piece of functionality (such as restricting editing functions, or “hardening”)
• [x] Require action by some or all users by a specific deadline
• [x] Change the front end and be highly visible to the public

Acceptance Criteria

• [x] VAMC system description field is "rich text limited" moving forward
• [x] All existing VAMC system nodes have been set to use rich text limited only.

Prelaunch

• [x] #7658 (Lynn)
• [x] https://github.com/department-of-veterans-affairs/va.gov-team/issues/22115
• [x] #6828 (Lynn)
• [x] #7656 (Denise)
• [x] Figure out how to run Jay's script
• [x] Test the assumption in department-of-veterans-affairs/content-build#9 below to make sure it works. it does not work. Needs a script.
• [x] #7662

  Runbook for launch

2. Search for h2 and export CSV (21 as of Jan 18) - Jay
3. Search for H4 and export CSV (53 as of Jan 18) - Jay
4. Search for H5 and export CSV (4 as of Jan 18) - Jay
5. Right before deploy:
   • [x] Run script to remove H3 "Care we provide" - drush scr ./scripts/content/VACMS-6456-remove-leading-care-we-provide-h3-tags.php - Nate
   • [x] Toggle feature flag FEATURE_CARE_WE_PROVIDE on https://prod.cms.va.gov/admin/config/system/feature_toggle - Jay
   • [x] Search for H3 and export CSV to capture. - Jay
     6. Right after deploy field setting change https://github.com/department-of-veterans-affairs/va.gov-cms/pull/7661
   • [x] run script to convert and save drush scr scripts/content/VACMS-7662-node-regional_health_care_service_des-force-limited-rich-text.php - Nate
   • [x] rerun all the searches to verify no H's exist in america - Jay
6. Send memo to VHA Digital Media to send to all VAMC content creators - Denise
7. PR to remove feature flag logic on content-build repo.
8. Delete feature flag FEATURE_CARE_WE_PROVIDE on https://prod.cms.va.gov/admin/config/system/feature_toggle

[ContentBrewmaster]

Added CM triage text

[JayDarnell]

Counts:

h2 (21 items) - vamc-system-service-audit-h2.csv

Post care we provide cleanup script: h3 (538 items) - vamc-system-service-audit-h3.csv

h4 (57 items) - vamc-system-service-audit-h4.csv

h5 (7 items) - vamc-system-service-audit-h5.csv

[swirtSJW]

Do we have to do anything more with these counts or can we call this epic done?

[JayDarnell]

I think they are mostly for posterity @swirtSJW - after the deploy finished and I ran the checks again all headers were gone (as expected). The final two steps in the deployment above aren't yet complete but one is its own ticket: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/8914

Do we need another issue to delete the feature flag for good?

[JayDarnell]

PR to remove the feature flag now that it is no longer needed: https://github.com/department-of-veterans-affairs/va.gov-cms/pull/9040