Visitar URL original
USWDS-Site: Identify which pages need to be updated for new products · Issue #3107 · uswds/uswds-site · GitHub
Skip to content

USWDS-Site: Identify which pages need to be updated for new products #3107

Open
1 of 1 issue completed
Open

Description

@jdotyoon

As a user, I want to understand how to use the new products, and I want to know they exist.

As such, comms/content staff need to determine which current pages on site need to be updated with language about the products. This work should be based off an audit conducted by @finekatie. Due to time constraints, pages to update will need to be prioritized.

Activity

  1. dct2023 commented on Feb 7, 2025

    @dct2023

    @jdotyoon Does this need to be slated for @ceperkins or @finekatie for an upcoming deliverable?

  2. jdotyoon commented on Feb 7, 2025

    @jdotyoon
    Author

    @dct2023 yes, but I'm not sure who's leading this one. @finekatie and @ceperkins can you please confirm?

  3. finekatie commented on Feb 7, 2025

    @finekatie
    Contributor

    Hello, this is one of those issues @ceperkins and I added to get info into the system before she had access.

    I have already started preliminary audit as we work to identify pages that will need updates.

    I think this needs to be two separate issues, on looking at it:
    1 - identify where it's needed
    2 - draft the language

    I think that we should prioritize what pages need to be audited. This site has A LOT, and me doing an audit of any kind could take more time than we have. So perhaps just sticking to top level pages and a select few others would be best for now?

  4. ceperkins commented on Feb 10, 2025

    @ceperkins
  5. finekatie commented on Feb 11, 2025

    @finekatie
    Contributor

    Clarissa and I discussed today. This should be three tickets: What pages that currently exist need to be updated with new product info and announcements and what's priority. For new products, where will those new pages live in the IA?
    So this is really three tickets:

    1. ID current pages
      • draft language (sub task)
    2. Decide new pages (IA work, etc.)
    3. Draft language new pages.
  6. ceperkins commented on Feb 11, 2025

    @ceperkins

    Updated issue

  7. changed the title [-]Identify site location and draft language for new products[/-] [+]Identify which pages need to be updated for new products[/+] on Feb 11, 2025
  8. transferred this issue fromuswds/uswdson Feb 12, 2025
  9. removed their assignment
    on Feb 12, 2025
  10. changed the title [-]Identify which pages need to be updated for new products[/-] [+]USWDS-Site: Identify which pages need to be updated for new products[/+] on Feb 12, 2025
  11. transferred this issue fromuswds/uswds-teamon Feb 12, 2025
  12. moved this from Triage to Scheduled in USWDS Core Project Dataon Feb 12, 2025
  13. moved this from Scheduled to In progress in USWDS Core Project Dataon Feb 18, 2025
  14. finekatie commented on Feb 20, 2025

    @finekatie
    Contributor

    Met with @amycole501 yesterday to discuss prioritizing what pages to update first in time for launch. Preliminary decision made to update 10 pages first and stagger other updates as needed, while we add new page content. Amy will create report based on search metrics and GA traffic data to confirm the first 10 pages it makes most sense to update first. Also shared prospective page info with Clarissa and Amy in Slack. Hope to present about this next week in CS/UX sync.

  15. amycole501 commented on Feb 20, 2025

    @amycole501
    Contributor

    Here is the list of pages to prioritize along with a couple of others that rose to the top during my data pull.

  16. finekatie commented on Feb 20, 2025

    @finekatie
    Contributor

    Discussed further with @jaclinec and @cfpollack today. May reduce from longer list to 5 pages for MVP. Plan to discuss in CS/UX sync next week.

  17. moved this from In progress to Peer Review in USWDS Core Project Dataon Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions