<?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/brian-dunbar/</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/brian-dunbar/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How NASA Chose a New Content Management System</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/11/21/how-nasa-chose-a-new-content-management-system/</link>
      <pubDate>Wed, 21 Nov 2012 13:21:29 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2012/11/21/how-nasa-chose-a-new-content-management-system/</guid>
      <description>A case study on how NASA is choosing a new enterprise content management system (CMS). The Challenge NASA.gov needs a new enterprise CMS. They’re facing issues such as software obsolescence, inconsistent website governance, and a large amount of unstructured content stored in flat HTML files. Their current system is almost a decade old, and the</description>
    </item>
  </channel>
</rss>
