<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>tools on Brian McCrory</title><link>https://brian.jazzofjapan.com/tools/</link><description>Recent content in tools on Brian McCrory</description><generator>Hugo</generator><language>en-US</language><copyright>© Brian McCrory</copyright><lastBuildDate>Fri, 10 Apr 2026 10:49:40 -0700</lastBuildDate><atom:link href="https://brian.jazzofjapan.com/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Jekyll to Hugo migration</title><link>https://brian.jazzofjapan.com/jekyll-to-hugo-migration/</link><pubDate>Sat, 15 Mar 2025 00:00:00 +0000</pubDate><guid>https://brian.jazzofjapan.com/jekyll-to-hugo-migration/</guid><description>&lt;div id="outline-container-headline-1" class="outline-2"&gt;
&lt;h2 id="headline-1"&gt;
March 2025
&lt;/h2&gt;
&lt;div id="outline-text-headline-1" class="outline-text-2"&gt;
&lt;p&gt;
Jekyll had become too slow as a convenient solution for editing Markdown files on my laptop. With hundreds of articles, thousands of media files (images, audio) files, and several data files, the reloading of the site after a file changed had become extremely slow. Each time a page changed (each time I changed and saved a file in my editor), there was a lag of about 60-120 seconds before Jekyll could reload the page with my changes. This made the writing process very burdensome for certain tasks. It seemed that slowness of Jekyll was a common frustration with Jekyll and large sites.&lt;/p&gt;</description></item></channel></rss>