Content audit: Provide ability to easily identify Menu links that should be updated if a URL changes OR prevent redirects from resulting in broken links #18109
Labels
CMS Team
CMS Product team that manages both editor exp and devops
Drupal engineering
CMS team practice area
Needs refining
Issue status
Search
[CMS feature] Editors can find content
User Story or Problem Statement
As a content editor (CAIA), I want to redirect old content to new content sometimes, so that Veterans are presented with the most accurate / recent content.
As a content editor (CAIA) and as Helpdesk, I want to keep the noise of the content-broken-links channel / broken link checker to a minimum, so that it's clear when a broken link is a real veteran facing issue.
Description or Additional Context
During week of May 6, two redirects shipped that were requested by CAIA, that led to broken links in the broken links report. (We think bc the broken links report interprets redirected URLs as broken?)
This led to a discussion with CAIA, where Mikki Northuis suggested that moving forward, redirect tickets should include a content audit for uses of the old URL to be redirected, so CAIA can act quickly to update those links when redirects ship (Slack discussion).
If broken link checks shouldn't call redirects broken
The work here might be to change the broken links report so that redirects are no longer reported as broken? However: that behavior may be intentional.
If broken link checker is doing the right thing
As a content editor (CAIA), I want to know everywhere in Drupal that a specific URL is used, e.g. https://va.gov/health-care/apply/application.
CAIA would like the ability to identify where a specific URL may appear in the CMS, in any entity, in order to be able to quickly update those links after a redirect ships / before the broken link report catches them. In example 2 above, the URL https://va.gov/health-care/apply/application was used in a Menu. Because the broken link checker runs against static pages, it was hard to identify where some references to the broken link originated from.
Sitewide Drupal folk ideated in SLack that it's possible to make a View of Menu links that could be searched with exposed filters, or that with some custom code, Menu links could potentially be added to Content search
Steps for Implementation
Acceptance Criteria
The text was updated successfully, but these errors were encountered: