<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tooling on Pauls Blog</title><link>https://prule.github.io/pauls-blog/tags/tooling/</link><description>Recent content in Tooling on Pauls Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://prule.github.io/pauls-blog/tags/tooling/index.xml" rel="self" type="application/rss+xml"/><item><title>Markdown is for the Web, AsciiDoc is for the Docs (and CVs)</title><link>https://prule.github.io/pauls-blog/post/coding/2026/asciidoc-ftw/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://prule.github.io/pauls-blog/post/coding/2026/asciidoc-ftw/</guid><description>&lt;p&gt;We all love Markdown. It&amp;rsquo;s the lingua franca of the modern developer—the default choice for READMEs, GitHub comments, and even this blog. But recently, I hit a wall with it while trying to polish my CV.&lt;/p&gt;
&lt;p&gt;Markdown is fantastic for &lt;strong&gt;structure&lt;/strong&gt;, but it’s historically weak on &lt;strong&gt;presentation&lt;/strong&gt;, especially when it comes to converting to PDF.&lt;/p&gt;
&lt;h3 id="the-problem-with-markdown-pdfs"&gt;The Problem with Markdown PDFs&lt;/h3&gt;
&lt;p&gt;When you want to convert a Markdown file to a professional-looking PDF, you usually have two choices:&lt;/p&gt;</description></item></channel></rss>