[DISCOVERY] Intended breadcrumb behavior (VAMC)

[mmiddaugh]

Issue Description

Work in #10030 standardized the experience for Events, News Releases and Stories. This issue was created to address work to create the ideal/intended behavior going forward.

Considerations/scenarios

From IA feedback

• You are here indicators in left nav
  • For content that is at the top level of the VAMC site, and not part of a "spoke", there is no "You are here" indicator in the left nav. The left nav should be designed to accommodate this, or it should be removed, or the IA should be reviewed for these pages. Example: https://va.gov/pittsburgh-health-care/make-an-appointment/
  • When L3 content that is hidden in the left nav, the left nav is still displayed on the page but without a "you are here" indicator. Example: Women health care
• L3 pages have accurate breadcrumbs but not urls Example: Women health care
• When should breadcrumb include "Home" (Va.gov) vs health system?

Breadcrumb Casing on Vet Center and Vet Center Location Pages Examples: Reno Vet Center Main and Locations page

Related issues

• VAMC Events: Update Home breadcrumb per outcome of testing#9439
• Update VAMC breadcrumb department-of-veterans-affairs/va.gov-team#32303
• FE: Screen readers need guidance on pronouncing "VA" in breadcrumbs#12302
• Vet Center Breadcrumbs not matching H1#12125
• UX debt: Lovell menu, breadcrumbs, and links#12334
• [Components and pattern standards] Your content or feature doesn't use standard global navigation components or is missing a standard navigation component. (04.02.1) department-of-veterans-affairs/va.gov-team#54299 (Lovell staging review)
• [URL standards] URL doesn't accurately reflect the location of the page within the site. (07.02.2) department-of-veterans-affairs/va.gov-team#54291 (Lovell staging review)
• Work in department-of-veterans-affairs/va.gov-team/issues/10038 implemented the health care home page as "Home" (rather than VA.gov) based on Veteran feedback
• Content IA and Accessibility: decide how multi-published events should be treated department-of-veterans-affairs/va.gov-team#13532
• Proper breadcrumbs for nodes that don't have menu items department-of-veterans-affairs/va.gov-team#1238 (Closed)

---

Tasks

• [ ] What work is necessary for this story to be completed?

Acceptance Criteria

• [ ] What will be created or happen as a result of this story?

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[jilladams]

Facilities Speedrun: Keeping. Breadcrumbs are a whole thing, should be considered in context of a bigger effort.

[mmiddaugh]

Updated 10/2023 (CMS Content Model Documentation)

NEW: For nodes that are not in any menu: AP recently changed this logic. Now, nodes in no menu are handled via a Drupal module, Easy Breadcrumb, which makes breadcrumbs available in the JSON:API.

Two modules were added to the CMS

• Easy Breadcrumb does the handling for nodes with no menu. It has all the settings for breadcrumb generation at the link provided. Because the primary vehicle for populating breadcrumbs, the menu_breadcrumbs module, is not configured for all content types the easy_breadcrumb module has been added. The easy_breadcrumb module fills in the gap left by menu_breadcrumbs by populating breadcrumbs based on path for content types without breadcrumb data.
• Computed Breadcrumb is the other module we added. It doesn't have any configurable settings, but it takes the breadcrumbs generated for any node (whether easy breadcrumb or menu-managed) and shoves them into a hidden field. That field data is what shows up in JSON:API