-
New guide provides tools for product leads
on March 31, 2016
To help our product managers, newcomers and veterans alike, wear the many hats that their jobs require, we’ve developed the 18F Product Guide. The guide will help get our team on the same page and provide a resource to our newcomers.
-
How we share a visual style across multiple sites
on March 30, 2016
In developing a redesign for cloud.gov, we needed a technical solution to coding the visual style that would scale to multiple sites with separate codebases without requiring us to copy code. Our solution is our “shared style library”, a library of CSS, JavaScript, images, and fonts that can be distributed to multiple codebases to create a shared visual style.
-
Best practices for building an accessible website using the Draft U.S. Web Design Standards
on March 29, 2016
When you work for the federal government, accessibility isn’t simply a nice-to-have — it’s the law. That’s why the Draft U.S. Web Design Standards set developers on the path of creating websites that anyone can use. The Draft Standards feature documentation that can help you keep your websites accessible, even after you make modifications.
-
Interesting things we learned from examining traffic patterns on analytics.usa.gov
on March 28, 2016
Ten federal agencies now have public dashboards and datasets for their web traffic on analytics.usa.gov. The dashboards show insights into how the public interacts with specific agency websites.
-
How design consistency helps users navigate federal websites
on March 25, 2016
We launched the Draft U.S. Web Design Standards last September, and over the next month, we plan to explore various topics related to design standards. In this post, we detail how our user research informed the decision decisions we made.
18F Blog
Delivering civic technology
Page 59 of 103