<?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 Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/markdown/</link>
    <description>Recent content in Markdown on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 10 Jun 2026 10:00:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/markdown/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Markdown Throne Falls: When AI Agents Step Out of the Chat Box, HTML Becomes the New Answer</title>
      <link>https://blog.margrop.net/en/post/markdown-throne-falls-ai-agent-html-output/</link>
      <pubDate>Wed, 10 Jun 2026 10:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/markdown-throne-falls-ai-agent-html-output/</guid>
      <description>If 2023 was the &amp;ldquo;chatbox era&amp;rdquo; of ChatGPT and Markdown, then 2026 is heralding the arrival of a new phase: AI no longer merely &amp;ldquo;answers&amp;rdquo; you—it is set to &amp;ldquo;take over&amp;rdquo; your interface. As Agents begin directly controlling browsers, operating SaaS, and building interactive application prototypes, Markdown—long the de facto standard for LLM output, that elegant format prized for its simplicity, readability, and token-friendliness—is rapidly revealing its fatal shortcoming as the &amp;ldquo;last mile.</description>
    </item>
    <item>
      <title>A Very Practical Trick: Export Yuque Documents to Markdown Without a Membership</title>
      <link>https://blog.margrop.net/en/post/yuque-url-export-markdown-without-member/</link>
      <pubDate>Fri, 06 Mar 2026 16:56:43 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/yuque-url-export-markdown-without-member/</guid>
      <description>&lt;p&gt;Many people use Yuque for technical notes, product documentation, or reading notes. But when it is time to move that content into a blog system such as Hugo, Hexo, or Jekyll, or sync it into a Git repository, the most annoying step is usually getting clean Markdown. If you have run into that problem, here is a small trick I have used for a long time: &lt;strong&gt;no paid membership, no plugin, just append a URL suffix and you get the full Markdown body directly&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://blog.margrop.net/post-images/yuque-markdown-url-trick.svg&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>One-click Installation of swagger2markup via Brew and Generating Markdown Documentation</title>
      <link>https://blog.margrop.net/en/post/brew-install-swagger2markup-and-generate-markdown/</link>
      <pubDate>Tue, 25 Jan 2022 21:43:39 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/brew-install-swagger2markup-and-generate-markdown/</guid>
      <description>&lt;h1 id=&#34;1-one-click-installation&#34;&gt;1. One-click Installation&lt;/h1&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;brew install swagger2markup-cli&#xA;&lt;/code&gt;&lt;/pre&gt;</description>
    </item>
  </channel>
</rss>
