<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pandoc on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/tags/pandoc/</link><description>Recent content in Pandoc on Incredible Technology, Incredibly Simple</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://damianflynn.com/tags/pandoc/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure DevOps Wiki to a Corporate PDF</title><link>https://damianflynn.com/posts/from-azure-devops-wiki-to-a-corporate-pdf/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/from-azure-devops-wiki-to-a-corporate-pdf/</guid><description>&lt;p&gt;The project documentation is in good shape. The team has been maintaining an Azure DevOps wiki, the architecture pages link to the detailed design, and the deployment instructions sit alongside the decisions that explain them.&lt;/p&gt;
&lt;p&gt;Then comes the handover request: “Can you send us the design document as a PDF? Please use the company template.”&lt;/p&gt;
&lt;p&gt;That is a reasonable request. The recipient might not have access to Azure DevOps. An architecture board may need a fixed version to review, or the customer may need to file the document in a records system. A wiki is useful for the people doing the work; a controlled document is useful for the people accepting it.&lt;/p&gt;</description></item></channel></rss>