Remove rich text editor from the VAMC System Operating Status content type

[kmariepat-cityfriends]

Background

In this content type there is a section for a Local emergency resources directory and within that a Patient resources rich text editor. This rich text editor has a format dropdown available, which means that editors can add heading levels here and possibly create accessibility heading violations.

When an editor creates a new VAMC system operating status page, the content in the Patient resources WYSIWYG is prefilled with multiple phone numbers - we do not know where this information is coming from and therefore we do not know if this information is accurate. For example - the Veterans Crisis Line phone number is the old number, not the 988 number.

The Operating status content type has been hardened, so the ask here (from Dave C) is to continue iterating and hardening this. Remove the Full rich text editor, do not allow editors to add headings here; we can continue to prefill any phone numbers that are going to be the same across all VAMCs (i.e. 911 and the correct Crisis Line number) but also allow editors to add individual unique VAMC numbers.

Acceptance Criteria

• [ ] I expect the rich text editor in the patient resources field within the local emergency resources directory fieldset is removed (VAMC System Operating Content Type)
• [ ] I expect this field now

[davidmpickett]

Might be an opportunity to address other known issues with this content type https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13733

[davidmpickett]

[kmariepat-cityfriends]

Next Steps:

• Answer what phone numbers are expected to present on all pages vs. local?

Hardening Steps:

• Discovery around state of the content
• Discovery with VHA DM
• Specification of moving from current state to new state
• Implementation.

[kmariepat-cityfriends]

Current Priority:

• Patient Safety First THEN accessibility
• Other high priority hardening efforts at this time
• Confirm with @laflannery that there isn't an accessibility issue with the issue presented in this card

Next Steps:

• add to VHA DM sync agenda
• make a content card to review phone schema
• make an ask of the content team to have a standardized design patterns for phone numbers and labels when it's not Call us toll free at 800-827-1000. We’re here Monday through Friday, 8:00 a.m. to 9:00 p.m. ET. for example, what's the right labeling system for emergency phone numbers
• Proposed Editorial Changes: Change the pattern to include phone; google snippet phone could capture incorrect numbers