What’s new

Product roadmap

Here, you’ll find our product roadmap — an up-to-date report on the work we’re doing.

Current work: our sprint milestones

See what we’re working on now and in the future by viewing what is being worked on or queued up to work on in our sprint milestones below. These are two-week increments of work that we commit to finishing, using Agile Product Development practices.

View our sprint milestones

Future work: our product roadmap

Below is our our product roadmap: a long term plan of the goals, features, and long-term direction of the U.S. Web Design Standards. We update this every few months with the status of our progress, as well as add new high-level future requests and ideas.

Milestone 1 - Make the best thing the easiest thing.

  • A public, up-to-date product road map. Done
  • A public maintenance plan. Done
  • A bare-bones HTML starter page, with CSS and JS pre-linked and necessary tags and classes. In Progress
  • Defined processes for active and public implementer support. Done
  • Contribution guidelines for both designers and developers. Done
  • Form patterns that include recommendations for just-in-time instructions. Done
  • UI components are comprised of clean, semantic code. Done
  • Simple "Getting Started" process and instructions. Done
  • A core set of common, usable web components. Done
  • Ready to go HTML templates (and related design stencils) for common types of government site pages. Done

Milestone 2 - Design for flexibility. Reuse, reuse, reuse.

  • Form templates structured in short chunks. Done
  • The ability to quickly copy and paste code from the website. Done
  • Form patterns that allow for easy recovery of mistakes. Done
  • Easy ways to customize the Standards to fit an agency’s brand and needs. Done
  • Design stencils and assets. Done
  • Interaction patterns for save-as-you-go functionality In Progress
  • A fork-able starter project representing a simple, static site with a few common pages. Done
  • Build out the documentation and increase the ease of the process for Windows users to start up. Done
  • Final clean up and launch 1.0 Done

Milestone 3 - Showcase benefits for agencies and users.

  • Highlight and track sites using the WDS more proactively, collect and link to them on the main site to show agencies what is possible. In Progress
  • Create and publicize a public slack channel for support, questions and sharing best practices. Done
  • Start a series of Case Study and Best Practice blog posts sharing the work that agencies have done using the Web Design Standards and what they’ve learned. Done
  • Produce more video tutorials and webinars for the community to learn how to more easily use the WDS. In Progress
  • Produce DigitalGov webinars more frequently and find more speaking engagements to share the work and code. In Progress
  • In an upcoming WDS site update, create a more visible location for all learning materials to showcase and help folks out. In Progress
  • Build a tighter API integration with the Digital Analytics Program to track usage of the WDS to help guide our decision making, along with continued user interviews and research. In Progress
  • Continue listening tours to meet with more than a half dozen agencies per quarter to learn more about their experience, needs, and collect feedback on the Web Design Standards. In Progress

Milestone 4 - Advanced Components & Speed, Speed, Speed.

  • Perform a Web Performance review and update to components to make sure they’re optimized to load as fast as possible. In Progress
  • Launch the Yeoman generator to quickly build out sites with the WDS base design. In Progress
  • Create a series of open source boilerplate language to include in government contracts to make it easier for Contracting Officers and Program Managers to define and request the use of the WDS in government contracts.
  • Find partners to work with and fund the development of more complex open source components for wayfinding components, such as progress indicators.
  • Find partners to work with and fund the development of more complex open source components for maps.
  • Find partners to work with and fund the development of more complex open source components for data visualizations.
  • Find partners to work with and fund the development of more complex open source components for standarized iconography.
  • Find partners to work with and fund the development of more complex open source components for complex form structures.
  • Find partners to work with and fund the development of more complex open source components for multi-lingual support for website chrome.
  • Find partners to work with and fund the development of more complex open source components for email formats.
  • Find partners to work with and fund the development of open source templates for government-used content management systems such as Drupal, Wordpress, Sharepoint, and more designer prototyping templates.
  • Create and implement modularized CSS and JS for each component so that they are easily used on a case by case basis.