Jekyll 2026-09-14T00:59:46+00:00 https://1.jar.io/ Daniel Doubrovkine https://1.jar.io/ https://1.jar.io/2026/01/15/serving-markdown-for-ai-agents 2026-01-15T00:00:00+00:00 2026-01-15T00:00:00+00:00 Daniel Doubrovkine https://1.jar.io <p>Dries Buytaert recently wrote about <a href="https://dri.es/the-third-audience">The Third Audience</a>. For decades, websites have targeted two audiences: humans and search engines. AI agents are now the third audience, and most websites aren’t optimized for them yet.</p> <p>AI agents prefer clean, structured content over HTML. Markdown is ideal - it’s readable, semantic, and free of navigation chrome. So I made this blog serve its source markdown files alongside the HTML.</p> <h3 id="how-it-works">How It Works</h3> <p>For every post like <a href="/2026/01/15/serving-markdown-for-ai-agents.html">/2026/01/15/serving-markdown-for-ai-agents.html</a>, you can now fetch the source at <a href="/2026/01/15/serving-markdown-for-ai-agents.md">/2026/01/15/serving-markdown-for-ai-agents.md</a>.</p> <p>AI agents can discover this via a <code class="language-plaintext highlighter-rouge">&lt;link&gt;</code> tag in the HTML head:</p> <div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt">&lt;link</span> <span class="na">href=</span><span class="s">"serving-markdown-for-ai-agents.md"</span> <span class="na">type=</span><span class="s">"text/markdown"</span> <span class="na">rel=</span><span class="s">"alternate"</span> <span class="na">title=</span><span class="s">"Markdown"</span><span class="nt">&gt;</span> </code></pre></div></div> <h3 id="implementation">Implementation</h3> <p>Since this is a GitHub Pages blog, custom Jekyll plugins don’t work. Instead, I added a <a href="https://github.com/dblock/code.dblock.org/blob/gh-pages/.github/workflows/deploy.yml">GitHub Actions workflow</a> that builds Jekyll and copies the markdown source files to <code class="language-plaintext highlighter-rouge">_site</code> before deployment.</p> <p>The workflow extracts the date and slug from each post filename and copies it to the matching URL path with a <code class="language-plaintext highlighter-rouge">.md</code> extension.</p> <h3 id="should-you-do-this">Should You Do This?</h3> <p>Dries raises a valid concern: are we just making it easier for AI companies to use our content without sending traffic back? Perhaps. But AI agents are already crawling our sites. Giving them cleaner input might lead to better attribution and more accurate responses that reference our work.</p> <p>The web has always been about making information accessible. This is just the next evolution.</p> <p>Plus, we will soon all work for AI anyway, so might as well get on its good side.</p> <h3 id="meta">Meta</h3> <p>This entire feature was implemented by <a href="https://claude.ai">Claude</a>, and this post was written by it as well.</p> <ul> <li><a href="https://github.com/dblock/code.dblock.org/commit/6fab9f3">Added GitHub Actions workflow to deploy and serve markdown.</a></li> <li><a href="https://github.com/dblock/code.dblock.org/commit/45769b0">Use Ruby 3.4 in deploy workflow.</a></li> <li><a href="https://github.com/dblock/code.dblock.org/commit/e5cb737">Also serve page markdown files.</a></li> <li><a href="https://github.com/dblock/code.dblock.org/commit/fcff077">Added link rel alternate for markdown discovery.</a></li> <li><a href="https://github.com/dblock/code.dblock.org/commit/e5eede2">Moved markdown link to post layout.</a></li> <li><a href="https://github.com/dblock/code.dblock.org/commit/f6ae02a">Fixed markdown alternate URL to remove .html.</a></li> <li><a href="https://github.com/dblock/code.dblock.org/commit/5ef474c">Serving Markdown for AI Agents.</a></li> </ul> <p><a href="https://1.jar.io/2026/01/15/serving-markdown-for-ai-agents.html">Serving Markdown for AI Agents in Jekyll</a> was originally published by Daniel Doubrovkine at <a href="https://1.jar.io">1.dblock.BLOG | tech blog</a> on January 15, 2026.</p>