USWDS 3.0 is an important major design system update that's easy to apply to an existing USWDS 2 project. USWDS 3.0 allows teams to update their projects to modern Sass syntax, improve performance, and reduce the size of project CSS.
From time to time we post product updates, guidance, and interviews we’ve conducted with USWDS users.
Learn how the Accelerator team collaborated with other digital teams and end-users across the federal government to bring new and updated components to the USWDS community in Release 2.10.
Today we’re releasing a new and exciting report and strategy that outlines what’s next for the U.S. Web Design System (USWDS) and our community.
USWDS Release 2.10 brings new components and updates as a result of our research into recent federal agency emergency response.
In this digital age, it’s simpler than ever to share the #GovLove virtually on Valentine’s Day, and the U.S. Web Design System (USWDS) is here to help you do just that.
We improved the security banner that's featured on many government websites and we encourage teams to update to this new security language as soon as possible.
Today, we’re launching U.S. Web Design System 2.0 (USWDS 2.0), a new foundation for the future of our design system. This new version was designed to make it easier for any project to integrate USWDS and use it to support both your mission and the needs of your audience.
In this 12th post in our series, we sat down with Jason Garber, front-end web developer at the U.S. Digital Service’s Defense Digital Service, to talk about his work creating a Ruby gem that integrates USWDS into a Ruby on Rails application.
For our 11th post in the series, we talked with Scott Weber, front-end developer, who worked on America’s Seed Fund site for the National Science Foundation (NSF). The site was created for people who want to get federal grant funding for their science or technology projects.
The U.S. Web Design System (formerly Standards) is currently being used on hundreds of government sites, with an audience of more than 100 million monthly users. In this 10th post in our series, we met with Kyle Jennings, creator of the Benjamin WordPress theme (and Franklin plug-in) (both of which are available on GitHub) using the System.
After listening to a lot of thoughtful feedback and discussion from a wide range of voices in the government web community, we’ve decided to change our name to the U.S. Web Design System.
2017 was a big year for the U.S. Web Design Standards. Here’s a look at where we’re headed in 2018.
The U.S. Web Design Standards are currently being used on hundreds of government sites, with an audience of more than 59 million monthly users. In this ninth post in our series, we met with the team at USA.gov to talk about their use of the Standards. USA.gov, and its Spanish counterpart GobiernoUSA.gov, are the official guides for government information.
The U.S. Web Design Standards are currently being used on hundreds of government sites, with an audience of more than 59 million monthly users. In this eighth post in our series, we met with Jennifer Thibault, visual designer and innovation specialist, to talk about the Federal Election Commission (FEC)’s use of the Standards on fec.gov.
The U.S. Web Design Standards are currently being used on hundreds of government sites, with an audience of more than 59 million monthly users. In this seventh post in our series, we sat down with Maureen Earley, program management specialist with the Office of Evaluation Sciences (OES), an office within the General Services Administration, to talk about her team’s use of the Standards on oes.gsa.gov. The OES brings diverse scientific experts onto their team for year-long rotations, where they work with federal agencies to implement and rigorously test changes made to government programs to evaluate whether or not they increase the ability of agencies to achieve their missions with greater success and efficiency.
The U.S. Web Design Standards team continues to sit down with various agencies who are using the Standards. In this sixth post in our series, we talked to Olivier Kamanda, project manager for code.gov to learn how that team adopted the Standards. Code.gov is a new platform designed to be the home for federal source code–a platform for improving the quality of government software. It launched in November 2016.
We've added two powerful, new tools to our development workflow.
As mentioned in our recent Q&A with the team at NASA, the U.S. Web Design Standards team is sitting down with various agencies that are using the Standards. In this second post in our series, we met with the team at the U.S. Customs and Border Protection and learned how they used the Standards to train, develop, and design their various websites and applications.
Every quarter the team takes a look at how many users have been exposed to the U.S. Web Design Standards across the federal government. We do this by pulling a subset of information that's collected as part of the Data Analytics Platform.
The team recently worked on the design assets to ensure that the latest components are present in the provided sticker sheets. These sticker sheets are meant to provide design teams with the assets they need to create wireframes or high-fidelity compositions quickly and effectively. The biggest change is the team's decision to retire the Omnigraffle sticker sheet.
The U.S. Web Design Standards are currently implemented on hundreds of government sites, with an audience of more than 26 million monthly users, and they’ve been recommended by the Office of Management and Budget for all government agencies. We chatted with Brandon Ruffridge, Senior Software Developer at NASA’s Glenn Research Center, to talk about his team’s use of the U.S. Web Design Standards.
With the recent launch of U.S. Web Design Standards 1.0, it's time for the team to take a look at the road ahead and determine what areas of the Standards they should focus on. To accomplish this, the team meet for a collaborative research and design workshop where ideas were proposed then mapped based on the ideas importance and feasibility.