Bug 1031842
Summary: | Add link checking to the docbuilder/pressgang | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Tim Hildred <thildred> |
Component: | CCMS-Core | Assignee: | Nobody <nobody> |
Status: | ON_QA --- | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.2 | CC: | cbredesen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tim Hildred
2013-11-19 00:09:00 UTC
This assumes that ECS is going to adopt deep linking, something that hasn't been established. I'm all for the idea, but it requires that ppl use pressgang, and not everybody does. Let's establish requirements first. This looks like a request for generic link validity checking. Checking all <a href> targets in a document for a 404 response seems like a sensible thing to do, and a low-hanging fruit. It would be *part* of an eventual larger "deep-linking into other ECS content" solution, but it's valuable in its own right. |