<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Markup on demo.theme.tadg.ie</title><link>https://demo.theme.tadg.ie/tags/markup/</link><description>Recent content in Markup on demo.theme.tadg.ie</description><generator>Hugo</generator><language>en-GB-oed</language><copyright>© Taḋg Paul — Apache License 2.0</copyright><lastBuildDate>Sat, 15 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://demo.theme.tadg.ie/tags/markup/index.xml" rel="self" type="application/rss+xml"/><item><title>Writing posts in Org-mode</title><link>https://demo.theme.tadg.ie/journal/writing-in-org/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate><guid>https://demo.theme.tadg.ie/journal/writing-in-org/</guid><description>&lt;p&gt;
This whole page is an &lt;code class="verbatim"&gt;.org&lt;/code&gt; file. Hugo renders Org-mode natively — no plugin, no preprocessor. For text that isn&amp;#39;t simple Markdown, Org gives you semantic blocks that Markdown lacks: verse, quote, centred content, source code with arbitrary language, examples, and raw HTML, all without shortcodes.&lt;/p&gt;
&lt;p&gt;
A common misconception is that Hugo&amp;#39;s Org support is &amp;#34;limited&amp;#34;. That refers to the Emacs Org-mode ecosystem — agenda, literate programming, mobile sync, the whole catalogue. As a &lt;em&gt;markup format&lt;/em&gt; for static web content, Hugo&amp;#39;s Org implementation is more featureful than its Markdown implementation. Most theme shortcodes exist to paper over Markdown&amp;#39;s gaps.&lt;/p&gt;</description></item></channel></rss>