<?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 Liquid Stack</title><link>https://liquid-stack.pages.dev/tags/markdown/</link><description>Recent content in Markdown on Liquid Stack</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>My Blog</copyright><lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://liquid-stack.pages.dev/tags/markdown/index.xml" rel="self" type="application/rss+xml"/><item><title>A Guide to Hugo Shortcodes</title><link>https://liquid-stack.pages.dev/p/using-shortcodes/</link><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><guid>https://liquid-stack.pages.dev/p/using-shortcodes/</guid><description>&lt;p&gt;Shortcodes are Hugo’s way to insert reusable structures into Markdown, making them useful for callouts, embeds, and repeated layouts.&lt;/p&gt;
&lt;h2 id="start-with-existing-shortcodes"&gt;Start with existing Shortcodes
&lt;/h2&gt;&lt;p&gt;Browse &lt;code&gt;layouts/shortcodes/&lt;/code&gt; to see what the theme already provides. Reuse existing components before adding one-off HTML for a single article.&lt;/p&gt;
&lt;h2 id="when-to-use-one"&gt;When to use one
&lt;/h2&gt;&lt;p&gt;Use a Shortcode when content needs a fixed structure, recurs across posts, or must render as HTML. Keep ordinary paragraphs, lists, and code blocks in Markdown.&lt;/p&gt;
&lt;h2 id="test-the-result"&gt;Test the result
&lt;/h2&gt;&lt;p&gt;Preview the post on desktop and mobile after adding a Shortcode. If it uses an image, video, or external URL, check the resource path and its failure state too.&lt;/p&gt;</description></item><item><title>Start Writing: Markdown and Bilingual Posts</title><link>https://liquid-stack.pages.dev/p/writing-markdown-and-bilingual-posts/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://liquid-stack.pages.dev/p/writing-markdown-and-bilingual-posts/</guid><description>&lt;p&gt;Liquid Stack uses Hugo’s multilingual content structure: Chinese and English versions of one post live in the same directory.&lt;/p&gt;
&lt;h2 id="create-a-post-directory"&gt;Create a post directory
&lt;/h2&gt;&lt;p&gt;Create &lt;code&gt;index.md&lt;/code&gt; and &lt;code&gt;index.zh.md&lt;/code&gt; under &lt;code&gt;content/post/your-slug/&lt;/code&gt;. Give both files the same &lt;code&gt;slug&lt;/code&gt; so the language switcher recognises them as translations of one post.&lt;/p&gt;
&lt;h2 id="write-useful-front-matter"&gt;Write useful front matter
&lt;/h2&gt;&lt;p&gt;Every post should have a title, description, date, category, and tags. Localise the title and description for each audience rather than translating word by word; keep product names, commands, and code unchanged.&lt;/p&gt;
&lt;h2 id="keep-it-maintainable"&gt;Keep it maintainable
&lt;/h2&gt;&lt;p&gt;Store images in &lt;code&gt;static/img/your-slug/&lt;/code&gt; and use site-absolute paths such as &lt;code&gt;/img/your-slug/featured.png&lt;/code&gt;. Before release, check links, images, and categories in both languages.&lt;/p&gt;</description></item></channel></rss>