<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Markdown on Artem Demchyshyn</title><link>https://demchaav.github.io/blog/tags/markdown/</link><description>Recent content in Markdown on Artem Demchyshyn</description><image><title>Artem Demchyshyn</title><url>https://demchaav.github.io/blog/images/og-default.png</url><link>https://demchaav.github.io/blog/images/og-default.png</link></image><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Sat, 04 Jul 2026 10:05:00 +0100</lastBuildDate><atom:link href="https://demchaav.github.io/blog/tags/markdown/index.xml" rel="self" type="application/rss+xml"/><item><title>A Big Markdown File Should Become a PDF You Can Navigate</title><link>https://demchaav.github.io/blog/posts/markdown-navigable-pdf/</link><pubDate>Sat, 04 Jul 2026 10:05:00 +0100</pubDate><guid>https://demchaav.github.io/blog/posts/markdown-navigable-pdf/</guid><description>Convert a long Markdown document to PDF and it becomes something you move around in: a clickable bookmark outline, working [text](#heading) jumps, a page-numbered contents, bidirectional footnotes. Why that&amp;#39;s the part most converters skip, and how it all falls out of a single idea — name an anchor now, let the engine bind it to a page after layout.</description></item></channel></rss>