<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Markdown on BareProxy.com</title>
    <link>https://bareproxy.com/tags/markdown/</link>
    <description>Recent content in Markdown on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/markdown/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Markdown Serving Plugin: Markdown Files Rendered to HTML With No Build Step</title>
      <link>https://bareproxy.com/bareproxy-markdown-serving-plugin-markdown-files-rendered-to-html-with-no-build-step/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-markdown-serving-plugin-markdown-files-rendered-to-html-with-no-build-step/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Status: planned, number 12 of 21 in BareProxy&amp;rsquo;s build order.&lt;/strong&gt; The plugins are built easiest first, and this one is about two days of coding: a Markdown library, a template and a cache. It comes after the Bot challenges plugin. This post describes what it will do, and it will be updated as it is built.&lt;/p&gt;&#xA;&lt;p&gt;A lot of writing already lives as Markdown: documentation, notes, a project&amp;rsquo;s README, a small blog. Putting it on the web usually means a static site generator, a build step, and a folder of output that has to be kept in sync with the source. For a handful of pages that&amp;rsquo;s more machinery than the job needs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
