Surface broken links in a way that helps editors find and repair them

[rachel-kauff]

Background

Currently the only way editors know about broken links is the link checkers on individual nodes. Problems with this:

• Node link report design is noisy and difficult to read and understand
• "out of sight, out of mind" - once an editor navigates away, the problem is no longer surfaced to them

User Story or Problem Statement

<As a , I need so I can _____.>

or

<Problem description. How might we _____ ?>

Affected users and stakeholders

• CMS_editors_of_X_product
• Developers of Y teams

Hypothesis (TBD)

Ideas

• Broken links surfaced in "dashboard" like areas on user profile pages an/or product landing pages

We believe that _thissolution will achieve _thisoutcome. We'll know that to be true when this measurable outcome occurs.

Assumptions

• Tk
• Tk

(How will these assumptions be validated?)

Acceptance Criteria

• [ ] Testable_Outcome_X
• [ ] Testable_Outcome_Y
• [ ] Testable_Outcome_Z
• [ ] Requires KB article update

Change management triage

The change represented by this user story will:

• [ ] 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
• [ ] Remove a piece of functionality (such as restricting editing functions, or “hardening”)
• [ ] Require action by some or all users by a specific deadline
• [ ] Change the front end and be highly visible to the public
• [ ] Noticeable performance improvements (publishing speed, predictability)

[swirtSJW]

We now have machine readable broken link data that could be used to surface broken links either through a dashboard or notifications. https://s3-us-gov-west-1.amazonaws.com/vetsgov-website-builds-s3-upload/broken-link-reports/vagovprod-broken-links.json

[ContentBrewmaster]

Added epic sections including change management section with suggested value.

[ContentBrewmaster]

@EWashb wanted to confirm the status for this work for Q3?

[EWashb]

We need to refine this epic for the current state.

How might we put in the appropriate limits in real-time for editors so that they can fix broken links as they happen and prevent one editor from breaking content build with a broken link.

[EWashb]

How might we provide real-time error messaging so that folks can fix their broken links BEFORE save (real-time validation). Also, how do we allow folks who may need to link to a page that does exist quite yet but will undoubtedly show a broken link until they do? For example, someone is making multiple pages at once that cross reference, but they would only be live pages publishing on the same day. One might show a broken link since the page doesn't exist yet.

[EWashb]

Related to #6008