Lovell Programs page split into two separate Programs pages

[ian-sears]

User Story or Problem Statement

As a Lovell Editor, I need to separate the Programs page into the two since they have different program offerings. Original JIRA CMS Help Desk ticket: VAHELP-7771

https://www.va.gov/lovell-federal-health-care-va/programs/

We only have one possible editable Programs section for both the TRICARE and VA site - I’m not able to make my own but we need to be able to separate them since they have different program offerings:

Programs | Lovell Federal Health Care | Veterans Affairs (va.gov) (note: this is VA)

Programs | Lovell Federal Health Care | Veterans Affairs (va.gov) (note: this is Tricare)

facilities-support Slack thread

Acceptance Criteria

• [ ] Existing feature functionality of the Lovell Programs page(s) is/are preserved (toggling)
• [ ] Editor able to add unique information (or) content to each Programs page
• [ ] Existing side(bar) Menus functionality is preserved
• [ ] Requires Content Model Documentation
• [ ] Requires design review
• [ ] Requires KB article update

Implementation steps

Alter the exisitng Programs page to no longer serve "both" TRICARE and VA Alter the existing Programs page to serve the VA side of the Lovell health care system Add a duplicate of this Programs page that serves the TRICARE side of the Lovell health care system

Design principles

Veteran-centered

• [ ] Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
• [ ] Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
• [ ] Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
• [ ] Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

• [ ] Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
• [ ] Efficient: Remove distractions and create clear, straightforward paths to get the job done.
• [ ] Approachable: Offer friendly guidance over authoritative instruction.
• [ ] Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
• [ ] Empowering: Provide clear information to help editors make decisions about their work.

[ian-sears]

dsva discussion https://dsva.slack.com/archives/C02730UEZPS/p1721751062452559

[ian-sears]

@TroyCMSSupport and @ian-sears discussed this in depth. We found the Lovell Contact Us pages have been separated like this, and see that the Editor updated these today as well. It may help to notice the 3 Blue Chevrons (look closely as they are unique to each Contact Us page) to see what may be motivating the Editor to need this Programs page separation.

[ian-sears]

Today, the Editor attempted to do this and mistakenly (temporarily) Archived the Programs page on the va side. CMS Help Desk revisioned the page to the previous Published revision and the page is now functioning as it was.

[ian-sears]

While we (CMS HD) can likely create the two new Programs pages (from the existing), we recommend this first be examined and possibly tested on the development sites (or) assist the CMS Help Desk in a decisive response to the Editor for this request. CMS HD asked the Editor to please hold off making changes (to the Prod site) for this until Engineering can consider the best resolution to this request. CMS Help Desk ticket is Awaiting Developers (consideration and decision) currently.

[jilladams]

Per Slack thread, assigned this ticket to Michelle for follow up with the requester (Rowan) to understand the need / priority better.