<?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/melody-kramer/</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/melody-kramer/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The User-Centered Redesign of IdentityTheft.gov</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/06/01/the-user-centered-redesign-of-identitytheft-gov/</link>
      <pubDate>Wed, 01 Jun 2016 14:30:14 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/06/01/the-user-centered-redesign-of-identitytheft-gov/</guid>
      <description>I first came across the redesigned IdentityTheft.gov on Reddit, of all places. Someone had posted a link to the Federal Trade Commission’s (FTC) newly redesigned site and wrote: I hope this never happens to any of you as the entire thing can be really stressful. The identitytheft.gov website is a true breath of fresh air…You</description>
    </item>
    <item>
      <title>Tips for Adapting analytics.usa.gov from Tennessee, Boulder, and Philadelphia</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/01/07/tips-for-adapting-analytics-usa-gov-from-tennessee-boulder-and-philadelphia/</link>
      <pubDate>Thu, 07 Jan 2016 13:19:21 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/01/07/tips-for-adapting-analytics-usa-gov-from-tennessee-boulder-and-philadelphia/</guid>
      <description>When we launched analytics.usa.gov with the Digital Analytics Program, the U.S. Digital Service, and the White House last March, we purposefully made it very easy to adapt and wrote language on the website to let people know they could use the code without restriction: This open source project is in the public domain, which means</description>
    </item>
    <item>
      <title>Announcing the Agile BPA Awards: A Conversation About the Process</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/09/01/announcing-the-agile-bpa-awards-a-conversation-about-the-process/</link>
      <pubDate>Tue, 01 Sep 2015 11:10:59 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/09/01/announcing-the-agile-bpa-awards-a-conversation-about-the-process/</guid>
      <description>In January, 18F Consulting announced a new kind of process for vendors to compete for software acquisition contracts. The Agile Blanket Purchase Agreement (BPA) process would be open to existing vendors on Schedule 70, and require vendors to submit a working prototype based on a public dataset—and then show their work in a publicly available</description>
    </item>
    <item>
      <title>18F’s Style Guide for Open Source Project Documentation</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/08/03/18fs-style-guide-for-open-source-project-documentation/</link>
      <pubDate>Mon, 03 Aug 2015 10:00:04 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2015/08/03/18fs-style-guide-for-open-source-project-documentation/</guid>
      <description>We routinely publish our best practices in the 18F Guides, and today we’re happy to launch a new one: the 18F Open Source Style Guide. The Open Source Style Guide is a comprehensive handbook for writing clear, accessible, and user-friendly documentation so that</description>
    </item>
  </channel>
</rss>
