<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/gray-brooks/</link>
    <description>Recent content on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/gray-brooks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API.Data.gov</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/services/service_api-data-gov/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/services/service_api-data-gov/</guid>
      <description>A free API management service for federal agencies.</description>
    </item>
    <item>
      <title>10x Project Lightning Talks: 2020</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/event/2020/06/30/10x-project-lightning-talks-2020/</link>
      <pubDate>Tue, 30 Jun 2020 14:00:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/event/2020/06/30/10x-project-lightning-talks-2020/</guid>
      <description>10x project teams will demonstrate their work to date and provide brief overviews of each project. We hope that these talks will highlight some of the most interesting work happening in government today and inspire others to submit ideas to 10x.</description>
    </item>
    <item>
      <title>Q&amp;amp;A With Ryan Day About GSA’s API Strategy</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2019/03/27/qa-with-ryan-day-about-gsas-api-strategy/</link>
      <pubDate>Wed, 27 Mar 2019 13:00:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2019/03/27/qa-with-ryan-day-about-gsas-api-strategy/</guid>
      <description>These new API standards will make it easier for GSA staff to launch and maintain good APIs.</description>
    </item>
    <item>
      <title>Application Programming Interfaces (APIs)</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/communities/apis/</link>
      <pubDate>Thu, 29 Mar 2018 03:30:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/communities/apis/</guid>
      <description>Working to advance the cause of APIs in the federal government.</description>
    </item>
    <item>
      <title>Exciting Additions to Analytics.usa.gov</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/06/17/exciting-additions-to-analytics-usa-gov/</link>
      <pubDate>Fri, 17 Jun 2016 12:30:45 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/06/17/exciting-additions-to-analytics-usa-gov/</guid>
      <description>We’ve expanded analytics.usa.gov to include 15(!) more agency-specific dashboard pages. We now offer agency-specific analytics data pages for a total of 25 major federal agencies, and each one is accessible from the dropdown menu at the top of the site.</description>
    </item>
    <item>
      <title>Analytics.usa.gov: Now with Agency-Specific Dashboards</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/02/18/analytics-usa-gov-now-with-agency-specific-dashboards/</link>
      <pubDate>Thu, 18 Feb 2016 11:10:51 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/02/18/analytics-usa-gov-now-with-agency-specific-dashboards/</guid>
      <description>We’ve added agency-specific dashboards to analytics.usa.gov!</description>
    </item>
    <item>
      <title>Analytics.usa.gov: New Features and More Data</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/12/01/analytics-usa-gov-new-features-and-more-data/</link>
      <pubDate>Tue, 01 Dec 2015 13:00:53 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/12/01/analytics-usa-gov-new-features-and-more-data/</guid>
      <description>As of writing this post, 25,225 of the 124,878 total visitors on federal government websites participating in the Digital Analytics Program (DAP) are NOT located in the United States. And as a result of</description>
    </item>
    <item>
      <title>An Introduction to HTTPS, by 18F and DigitalGov University</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/07/21/an-introduction-to-https-by-18f-and-digitalgov-university/</link>
      <pubDate>Tue, 21 Jul 2015 11:10:31 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/07/21/an-introduction-to-https-by-18f-and-digitalgov-university/</guid>
      <description>18F uses HTTPS for everything we make, and the U.S. government is in the process of transitioning to HTTPS everywhere. As part of this effort, we’ve recently partnered with DigitalGov University to produce a two-video series introducing the why’s and how’s of HTTPS. In an Introduction to HTTPS for beginners, we cover what happens when</description>
    </item>
    <item>
      <title>Taking the Pulse of the Federal Government&#39;s Web Presence</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/06/03/taking-the-pulse-of-the-federal-governments-web-presence/</link>
      <pubDate>Wed, 03 Jun 2015 13:10:57 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/06/03/taking-the-pulse-of-the-federal-governments-web-presence/</guid>
      <description>The U.S. federal government is launching a new project to monitor how it&amp;rsquo;s doing at best practices on the Web.</description>
    </item>
    <item>
      <title>Take a Gander at Our /Developer Page!</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/07/28/take-a-gander-at-our-developer-page/</link>
      <pubDate>Mon, 28 Jul 2014 10:00:05 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/07/28/take-a-gander-at-our-developer-page/</guid>
      <description>A growing trend both inside government and outside is to have a simple welcoming page for outside developers who may be interested in your team’s efforts. This material is often located at website.gov/developer 1 and points visitors to technical material that developers may be interested in, especially APIs. Collecting technical documentation in one place facilitates</description>
    </item>
    <item>
      <title>Packaging Up API Usability Testing for Agency Reuse</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/05/20/packaging-up-api-usability-testing-for-agency-reuse/</link>
      <pubDate>Tue, 20 May 2014 01:00:12 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2014/05/20/packaging-up-api-usability-testing-for-agency-reuse/</guid>
      <description>Over the past year, a GSA collaboration has seen a project that offers API Usability Testing to federal agencies go from the pilot stage to a regular, robust series. Already, 13 agencies and programs have participated, and several more participate with every monthly session</description>
    </item>
    <item>
      <title>API Security</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/07/29/api-security/</link>
      <pubDate>Mon, 29 Jul 2013 01:12:58 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/07/29/api-security/</guid>
      <description>Like website development, API security revolves around three stages—planning the API, testing the API, and monitoring the API after it has launched. The planning stage requires those involved to conceptually map several design decisions and the impact that they will have on security. The second stage applies your agency’s security program to the API release</description>
    </item>
    <item>
      <title>Develop with Web Standards</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/06/30/develop-with-web-standards/</link>
      <pubDate>Sun, 30 Jun 2013 01:23:02 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/06/30/develop-with-web-standards/</guid>
      <description>What It Is Do you remember the days when web pages had banners announcing that they were “best viewed with browser X”? Veteran web developers and designers certainly do, because they had to consider numerous exceptions for certain browsers and their versions. Today, building websites isn’t as challenging and that’s because developers are moving toward</description>
    </item>
    <item>
      <title>/Developer Kit</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/05/21/developer-kit/</link>
      <pubDate>Tue, 21 May 2013 13:05:45 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/05/21/developer-kit/</guid>
      <description>These are the elements that make up a well-rounded developer hub. Homepage The API efforts of any agency should all be accessible via one easy to reach developers hub. This Web page should provide a path to all public APIs and any associated resources. Once an agency has begun to publish multiple APIs, certain resources</description>
    </item>
    <item>
      <title>API Release Kit</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/05/16/api-release-kit/</link>
      <pubDate>Thu, 16 May 2013 13:04:03 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/05/16/api-release-kit/</guid>
      <description>These are the elements you should include in your federal API release. Homepage Each of your public APIs needs a page to serve as a hub to provide access to all information and tools associated with it. By using the page’s sidebar, footer, and sub pages, you can directly include or link to each of</description>
    </item>
    <item>
      <title>We the People API</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/05/09/we-the-people-api/</link>
      <pubDate>Thu, 09 May 2013 09:09:16 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/05/09/we-the-people-api/</guid>
      <description>“APIs for WhiteHouse.gov? What in the heck does that mean?” Like President Obama, you may be asking the same question.</description>
    </item>
    <item>
      <title>APIs in Government</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/04/30/apis-in-government/</link>
      <pubDate>Tue, 30 Apr 2013 02:12:53 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/04/30/apis-in-government/</guid>
      <description>This page is about what an Application Programming Interface or API is and what it does and how government agencies are using them to operate more efficiently.</description>
    </item>
    <item>
      <title>Producing APIs through Data.gov</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/04/30/producing-apis-through-data-gov/</link>
      <pubDate>Tue, 30 Apr 2013 01:07:53 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/04/30/producing-apis-through-data-gov/</guid>
      <description>One way agencies can offer APIs for their data is to use the built–in functionality of Data.gov. The information that is hosted as interactive datasets have an API layer which agencies can make available through documentation in the developer’s section of the agency’s website. The guide below will help you do this. Process Upload a dataset</description>
    </item>
    <item>
      <title>Usability Testing &#43; Gov APIs = Best</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/04/29/usability-testing-gov-apis-best/</link>
      <pubDate>Mon, 29 Apr 2013 04:37:18 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/04/29/usability-testing-gov-apis-best/</guid>
      <description>Good APIs can transform intimidating data sets into something that people can use. Good government APIs can create a better connection between government and citizens. The Digital Government Strategy has spurred Federal adoption of APIs, and the Digital Services Innovation Center and DATA.GOV teams are supporting these efforts by releasing a swath of guidance and</description>
    </item>
    <item>
      <title>API Analytics</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/api-analytics/</link>
      <pubDate>Tue, 12 Mar 2013 13:11:57 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/api-analytics/</guid>
      <description>Similar to website analytics, API analytics focus on reliably reporting the metrics which are most useful to its stakeholders. There are a many ways of collecting, reporting, and consuming API analytics but all revolve around the industry–accepted norm that some form of analytics are crucial to any API program. The most basic metrics will track</description>
    </item>
    <item>
      <title>API Design and Documentation</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/api-design-and-documentation/</link>
      <pubDate>Tue, 12 Mar 2013 12:49:20 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/api-design-and-documentation/</guid>
      <description>Design At their core, developers want APIs for very straightforward, pragmatic ends. You should always design your APIs and document them with the goal of making it easier for developers to use them. Doing so results in greater adoption and a healthier, more successful API. The least efficient way to support developers would be to</description>
    </item>
    <item>
      <title>How to Make APIs—An Overview</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/how-to-make-apis-an-overview/</link>
      <pubDate>Tue, 12 Mar 2013 12:47:51 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/how-to-make-apis-an-overview/</guid>
      <description>After choosing a set of information or services to offer via API, some of your next steps are to plan and implement the API. You’ll still need to prepare documentation, tools, and other elements that make a complete package for the API, but at the center is the actual Web service itself. In many situations,</description>
    </item>
    <item>
      <title>Resources and Tools for APIs</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/resources-and-tools-for-apis/</link>
      <pubDate>Tue, 12 Mar 2013 12:41:05 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/resources-and-tools-for-apis/</guid>
      <description>Hosted API Tools Labs.Data.gov is a repository of shared services to prototype and provide developer resources to government agencies. Each tool uses Web services and lightweight, open source code to provide powerful functionality. Agencies are encouraged to improve any project and submit pull requests in order to share the improvements with others. API Standards Template With the open</description>
    </item>
    <item>
      <title>How to Get Started with APIs</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/how-to-get-started-with-apis/</link>
      <pubDate>Tue, 12 Mar 2013 12:28:11 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/how-to-get-started-with-apis/</guid>
      <description>Audit Research existing APIs Regardless of your agency’s level of progress in API production, your first step is to create a developer hub that links to any of your agency’s existing APIs. This can help identify current efforts and connect you with others in your agency already working on APIs. Follow up with a deeper</description>
    </item>
    <item>
      <title>API Basics</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/api-basics/</link>
      <pubDate>Tue, 12 Mar 2013 12:24:59 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/api-basics/</guid>
      <description>Common Technical Choices Protocol API protocol is the set of rules that govern how an API functions. The protocol outlines the structure and definitions of the API. The two common forms are REST and SOAP. REST is the dominant choice for API protocol because it uses the http protocol that powers the Web. REST supports more</description>
    </item>
    <item>
      <title>Benefits of APIs</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/benefits-of-apis/</link>
      <pubDate>Tue, 12 Mar 2013 12:19:48 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2013/03/12/benefits-of-apis/</guid>
      <description>Understanding the benefits of API production allows you to coordinate with system owners and other stakeholders to modernize the agency’s systems and unlock the sizable potential. Here are just some of these opportunities. Efficiency Providing API access allows for content to be created once and automatically published or made available to many channels. Your agency’s</description>
    </item>
    <item>
      <title>Case Study: How DOL Created Software Development Kits (SDKs)</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/11/19/case-study-how-dol-created-software-development-kits-sdks/</link>
      <pubDate>Mon, 19 Nov 2012 01:16:23 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/11/19/case-study-how-dol-created-software-development-kits-sdks/</guid>
      <description>What It Is The U.S. Department of Labor sought to go beyond merely making data available to developers and take ease of use of the data to the next level by giving developers tools that would make using DOL’s data easier. The target audience was not just experienced developers, but even those who may be</description>
    </item>
    <item>
      <title>Case Study: How GSA Launched Social Media Registry</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/11/19/case-study-how-gsa-launched-social-media-registry/</link>
      <pubDate>Mon, 19 Nov 2012 01:14:12 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/11/19/case-study-how-gsa-launched-social-media-registry/</guid>
      <description>In September, the General Services Administration (GSA) launched a registry of all federally-managed social media accounts. We want to explain a little of the history behind the registry and talk about a few things that make it a truly remarkable innovation from GSA. Before I start, I want to emphasize when I say “we” from</description>
    </item>
    <item>
      <title>Introduction to APIs</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/07/26/introduction-to-apis/</link>
      <pubDate>Thu, 26 Jul 2012 09:56:58 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/07/26/introduction-to-apis/</guid>
      <description>There’s an easier way to get content and data into the hands of citizens. Application Programming Interfaces, or APIs, are web services that allow people to more easily consume content and data in multiple ways–via mobile devices, mobile apps, innovative mash-ups, and much more. Simply put, “APIs are a better way to get government information</description>
    </item>
  </channel>
</rss>
