<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>效率工具 on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/%E6%95%88%E7%8E%87%E5%B7%A5%E5%85%B7/</link>
    <description>Recent content in 效率工具 on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 06 Mar 2026 16:56:43 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/%E6%95%88%E7%8E%87%E5%B7%A5%E5%85%B7/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
