<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Digital History on Roy Rosenzweig Center for History and New Media</title><link>https://rrchnm.org/tags/digital-history/</link><description>Recent content in Digital History on Roy Rosenzweig Center for History and New Media</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rrchnm.org/tags/digital-history/index.xml" rel="self" type="application/rss+xml"/><item><title>Agents and APIs: Sustaining Projects by Rebuilding Them</title><link>https://rrchnm.org/blog/agents-and-apis/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://rrchnm.org/blog/agents-and-apis/</guid><description>&lt;p&gt;RRCHNM has been in the business of producing digital history for over thirty years now, and because of this we have developed hundreds of projects on a variety of now-old web software and systems. Five years ago, when I joined RRCHNM, we decided to shift and consolidate our tech stack towards tools and software that would allow us a bit more creativity in the projects we were developing as well as provide easier ways to sustain projects over time. That resulted in a shift in our technical expertise, leading us to prefer the Python-based web framework &lt;a href="https://www.djangoproject.com/"&gt;Django&lt;/a&gt; or the static site generator &lt;a href="https://gohugo.io/"&gt;Hugo&lt;/a&gt; for projects while reaching for WordPress, Drupal, and Omeka would be used sparingly.&lt;/p&gt;</description></item></channel></rss>