You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use a simple and flexible design style guide for the service. Use the [U.S. Web Design Standards](https://playbook.cio.gov/designstandards) as a default
The U.S Web Design Standards now appears to be called U.S. Web Design System and is located here: https://designsystem.digital.gov/.
Impact
People who try to access the link above through the Digital Services Playbook or who link to https://playbook.cio.gov/designstandards (like 18F does here will need to bear an additional load time of 1s (or more based on their internet speed). Separately, correcting the name will help people avoid confusion.
In Play 3, update reference of U.S. Web Design Standards to U.S. Web Design System (addressed in pull request Play 3: Update USWDS name #233).
Additional Notes
put in usa.gov redirects 18F/dns#418 addressed a problem called out earlier in this ticket where standards.usa.gov failed to redirect at all. It would still be worth updating the USDS redirect to remove the dependency on standards.usa.gov.
It appears that playbook.cio.gov/designstandards is used in part to track usage with Google Analytics. The U.S. Web Design System is linked to directly at the bottom of https://www.usds.gov/. Choosing to link directly in Play 3 to designsystem.digital.gov would cut a full 2.6s+ off of the redirect.
The text was updated successfully, but these errors were encountered:
Problem
In Play 3: Make it simple and intuitive, item 1 of the checklist states:
Impact
People who try to access the link above through the Digital Services Playbook or who link to https://playbook.cio.gov/designstandards (like 18F does here will need to bear an additional load time of 1s (or more based on their internet speed). Separately, correcting the name will help people avoid confusion.
Proposed Solutions
Additional Notes
The text was updated successfully, but these errors were encountered: