<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jason Heppler on Sustainable DH</title><link>https://sustainabledh.org/authors/jason-heppler/</link><description>Recent content in Jason Heppler on Sustainable DH</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Sep 2026 10:00:00 -0500</lastBuildDate><atom:link href="https://sustainabledh.org/authors/jason-heppler/index.xml" rel="self" type="application/rss+xml"/><item><title>"The Most [Undecipherable] Difficulties": Sustaining and Transcribing the Papers of the War Department</title><link>https://sustainabledh.org/blog/2026-09-28-pwd-transcriptions/</link><pubDate>Mon, 28 Sep 2026 10:00:00 -0500</pubDate><guid>https://sustainabledh.org/blog/2026-09-28-pwd-transcriptions/</guid><description>&lt;p&gt;One of the most complicated websites RRCHNM has been sustaining in recent years is the &lt;a href="https://wardepartmentpapers.org"&gt;Papers of the War Department&lt;/a&gt; (PWD), a crowdsourced transcription project to recover and make accessible the once-lost papers of the War Department whose offices burned to the ground in 1800. The project began with document collection and digitization efforts in the 1990s, but only became a website and an RRCHNM project two decades ago, in 2006.&lt;/p&gt;</description></item><item><title>Agents and APIs: Sustaining Projects by Rebuilding Them</title><link>https://sustainabledh.org/blog/2026-09-20-agents-apis/</link><pubDate>Mon, 21 Sep 2026 10:00:00 -0500</pubDate><guid>https://sustainabledh.org/blog/2026-09-20-agents-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><item><title>Building Static Search</title><link>https://sustainabledh.org/blog/building-static-search/</link><pubDate>Wed, 20 Aug 2025 10:29:07 -0500</pubDate><guid>https://sustainabledh.org/blog/building-static-search/</guid><description>&lt;p&gt;One of the nice features of a &lt;a href="https://en.wikipedia.org/wiki/Dynamic_web_page"&gt;dynamic website&lt;/a&gt;&amp;mdash;the kind of thing that&amp;rsquo;s often driven by databases&amp;mdash;is the ability to run a search feature. Search is a feature across the various content management systems we use (or once used) at RRCHNM &amp;ndash; Omeka, Drupal, and Wordpress. But once a site is flattened and no longer reliant on a database for serving content, the built-in ability of search goes away. For many of our sites, the loss of this feature can be dismaying to users. So, a goal this summer was to figure out a way to implement search on a static site.&lt;/p&gt;</description></item></channel></rss>