a repeatable process to identify and address duplicative web content

[ryanwoldatwork]

Draft a process that any GSA-staff person (or outsider) can use to identify duplicate content for review/assessment and assignment to a backlog.

References

• 21st Century Idea - does not overlap with or duplicate any legacy websites and, if applicable, ensure that legacy websites are regularly reviewed, eliminated, and consolidated;
• the DRY Principle

Example of this issue

An actual instance of duplicative content:

• https://tech.gsa.gov/guides/0_a_guide_newtoagile/
• https://agile.18f.gov/
• [redacted] intranet site

Draft process example

1. user identifies duplicative content
2. user creates an issue
3. somebody tbd reviews the issue
4. that somebody coordinates with the website managers involved
5. website manager 1 updates the canonical content (that will remain)
6. website manager 2 sunsets the duplicative content

graph TD;
    user-->|identifies|duplicativeContent;
    user-->|creates|issue;
    somebody-->|reviews|issue;

    websiteManager1-->|is a|websiteManager;
    websiteManager2-->|is a|websiteManager;

    somebody-->|coordinates with|websiteManager;
    websiteManager1-->|updates|canonicalContent;
    websiteManager2-->|sunsets|duplicativeContent;

Related issues

• https://github.com/GSA/wg-web-modernization/issues/54