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

[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.

[dct2023]

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

[jdotyoon]

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

[finekatie]

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?

[ceperkins]

I agree that this should be broken up into two tickets. @catherine Fine - QUAB-C ***@***.***> - let's discuss the audit - agree that we need to prioritize given what time we have.

…

On Fri, Feb 7, 2025 at 12:47 PM Katie Fine ***@***.***> wrote: Hello, this is one of those issues @ceperkins <https://github.com/ceperkins> and I added to get info into the system before she had access. I have already started preliminary audit <https://docs.google.com/spreadsheets/d/1oaaYt9LpO_cftzdfwe-uvZxdjgSIJUkNHOwhPlXeWOg> 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 <https://docs.google.com/spreadsheets/d/1oaaYt9LpO_cftzdfwe-uvZxdjgSIJUkNHOwhPlXeWOg/edit?gid=554307338#gid=554307338> and a select few others would be best for now? — Reply to this email directly, view it on GitHub <#3107>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BO7ZHGIAHIYML2VDU4IPOF32OUEVXAVCNFSM6AAAAABWPDAGNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBTHEZTSMZTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[finekatie]

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.

[ceperkins]

Updated issue

[finekatie]

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.

[amycole501]

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

[finekatie]

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.