<?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/jonathan-hooper/</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/jonathan-hooper/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Federalist Is out of Beta and Open for Business</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2017/06/05/federalist-is-out-of-beta-and-open-for-business/</link>
      <pubDate>Mon, 05 Jun 2017 11:00:17 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2017/06/05/federalist-is-out-of-beta-and-open-for-business/</guid>
      <description>If you’re a program manager or a federal web developer you’ve probably been given a seemingly simple task: Create a basic website as part of a new initiative at your agency. The hardest part is often not crafting the content or designing the prototype, but getting the security and privacy compliance in order to launch</description>
    </item>
  </channel>
</rss>
