Official websites use .gov
A .gov website belongs to an official government
organization in the United States.
Secure .gov websites use HTTPS
A
lock (
) or https:// means you’ve safely connected to
the .gov website. Share sensitive information only on official,
secure websites.
Guidance on building better digital services in government
Making software, source code, and the development process available to the public
Open source development prioritizes using Open Source Software to make source code available for public use. Open Source Software encourages federal government teams to share technical knowledge and encourages a collaborative approach to the review and reuse of source code.
Published open source policy guidelines from the 18F service delivery team.
How well do 18F software development practices work? The 18F team reflected on a recent project for the Cybersecurity and Infrastructure Security Agency (CISA) .gov registry to gauge the effectiveness of six recommendations aligned with what they actually did. — via 18F
The Open Data, Design, and Development (ODDD) team has replaced signed consent forms with a more accessible user research agreement process, offering multiple opt-in points. This ensures informed consent and participant autonomy. Explore why and how the ODDD team implemented this comprehensive participant consent process in their user research. — via Office of Natural Resources Revenue
Best practices for security administration of control systems and their components. Specific guidance and lessons learned from a federal information system manager.
In December 2020, the United States Tax Court introduced DAWSON, a modern open-source case management system developed with assistance from an industry partner and 18F. DAWSON streamlined Court operations and changed the way the public interacts with the Court. — via 18F
The 18F Engineering Sandwich for Cloud-based Web Apps—18F Engineering is often thought of as a technology shop, but that’s too broad. There are very few technology choices we actually make at the project level, so, more often than not, we combine a limited set of technologies to make our applications. To explain this, we’ll use the metaphor of a sandwich shop. — via 18F
Learn how Federal Source Code Policy supports reuse and public access to custom-developed federal source code.
25 posts
The Open Data, Design, and Development (ODDD) team has replaced signed consent forms with a more accessible user research agreement process, offering multiple opt-in points. This ensures informed consent and participant autonomy. Explore why and how the ODDD team implemented this comprehensive participant consent process in their user research. — via Office of Natural Resources Revenue
How well do 18F software development practices work? The 18F team reflected on a recent project for the Cybersecurity and Infrastructure Security Agency (CISA) .gov registry to gauge the effectiveness of six recommendations aligned with what they actually did. — via 18F
Best practices for security administration of control systems and their components. Specific guidance and lessons learned from a federal information system manager.
In December 2020, the United States Tax Court introduced DAWSON, a modern open-source case management system developed with assistance from an industry partner and 18F. DAWSON streamlined Court operations and changed the way the public interacts with the Court. — via 18F
The 18F Engineering Sandwich for Cloud-based Web Apps—18F Engineering is often thought of as a technology shop, but that’s too broad. There are very few technology choices we actually make at the project level, so, more often than not, we combine a limited set of technologies to make our applications. To explain this, we’ll use the metaphor of a sandwich shop. — via 18F
Learn how we used GitHub to conduct a card sort and tree testing to improve the information architecture for onrr.gov.
In this recap of the October 2021 U.S. Web Design System (USWDS) Monthly Call, the USWDS team shares how their community can help teams solve problems together, and what tools and channels we can use to ask questions, get answers, and provide useful feedback.
This guide provides acquisition professionals the steps and resources needed to operationalize the evaluation process developed for the Discovery BPA.
Through the use of an open-source procurement process, we created an experiment others can replicate to encourage Agile thinking.
Digital.gov
An official website of the U.S. General Services Administration
