-
How the U.S. Customs and Border Protection uses the U.S. Web Design Standards
on March 30, 2017
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.
-
NASA’s journey with the U.S. Web Design Standards
on March 21, 2017
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 [Furious Otter]*, Senior Software Developer at NASA’s Glenn Research Center, to talk about his team’s use of the U.S. Web Design Standards.
-
One agency’s investments in open source mean others benefit
on March 15, 2017
One of the advantages to working across government is that we often have opportunities to share insights from other projects, repurpose code, and connect otherwise disjointed efforts. This happens in direct work with our partners, but also on our blog and in our GitHub repository. Our code, guides, and other work are all free for other government agencies and the public to use for their benefit (and we love when people do).
-
U.S. Web Design Standards releases version 1.0
on March 13, 2017
The U.S. Web Design Standards are a library of design guidelines and code to help government developers quickly create trustworthy, accessible, and consistent digital government services. Last week, we announced the 1.0 release of the Standards, a milestone that signals the Standards are a stable, trustworthy resource for government designers and developers.
-
To get things done, you need great, secure tools
on February 27, 2017
To folks new to government, one of the most surprising differences between our work and work in the private sector are the barriers in accessing commercially available software, and commercially available Software as a Service (SaaS) in particular. There are many good reasons for these barriers but digital teams need great tools to get work done and compliance requires tradeoffs associated with time to initial delivery and accommodation of constraints that are different from the private sector.
Page 37 of 103