<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hugo on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/hugo/</link>
    <description>Recent content in Hugo on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 05 May 2026 16:00:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/hugo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Prompt OpenClaw, HermesAgent, Codex, Claude, Gemini, OpenCode, and Droid to Write Articles and Publish WeChat Drafts</title>
      <link>https://blog.margrop.net/en/post/agent-prompt-wechat-draft-automation/</link>
      <pubDate>Tue, 05 May 2026 16:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/agent-prompt-wechat-draft-automation/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;If you want an agent such as OpenClaw, HermesAgent, Codex, Claude, Gemini, OpenCode, or Droid to write an article, prepare a Hugo blog post, convert the Chinese version into WeChat-compatible HTML, preview it, fix layout issues, and create a WeChat Official Account draft, the prompt cannot simply say &amp;ldquo;write and publish an article.&amp;rdquo; A useful prompt must define the goal, source material, paths, account constraints, fixed-IP requirements, conversion steps, preview checks, failure recovery, privacy boundaries, and final verification evidence.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;This post describes a reusable prompting pattern for article automation. It explains how to prepare the WeChat draft API, why a Linux machine with a fixed public IP is often required, how to tell an agent to try local API access first and then fall back to a fixed-egress host, how to use a Markdown-to-WeChat-HTML converter, and how to make the agent check for invisible white text, strange indentation, broken images, and accidental leaks before declaring the job done.&lt;/p&gt;&#xA;&lt;p&gt;All examples are privacy-safe. They use placeholders rather than real secrets, private IP addresses, hostnames, repository URLs, tokens, cookies, or personal paths. Replace placeholders with your own values only in a protected runtime environment, never in a public article, public repository, or screenshot.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Gitalk Broken After Migration from Gridea to Hugo: Complete Troubleshooting and Fix Log</title>
      <link>https://blog.margrop.net/en/post/gitalk-migration-from-gridea-to-hugo-complete-fix/</link>
      <pubDate>Sun, 01 Mar 2026 09:30:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/gitalk-migration-from-gridea-to-hugo-complete-fix/</guid>
      <description>&lt;h1 id=&#34;background&#34;&gt;Background&lt;/h1&gt;&#xA;&lt;p&gt;After migrating the blog entirely from &lt;code&gt;Gridea&lt;/code&gt; to &lt;code&gt;Hugo&lt;/code&gt;, pages load normally, but the comment section &lt;code&gt;Gitalk&lt;/code&gt; appears to be malfunctioning:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;No obvious errors are reported on the page, but the comment section doesn&amp;rsquo;t load or display historical comments.&lt;/li&gt;&#xA;&lt;li&gt;Historical articles are not associated with their original issues.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;This article documents a complete troubleshooting and fix process for future reference when migrating similar sites.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Completely Migrate Gridea to Hugo (Including Pitfalls and Fixes)</title>
      <link>https://blog.margrop.net/en/post/how-to-migrate-gridea-to-hugo-completely/</link>
      <pubDate>Sat, 28 Feb 2026 21:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/how-to-migrate-gridea-to-hugo-completely/</guid>
      <description>&lt;p&gt;I recently migrated my blog from &lt;code&gt;Gridea&lt;/code&gt; to &lt;code&gt;Hugo&lt;/code&gt;. It might seem like a simple &amp;ldquo;static blog framework switch&amp;rdquo;, but there are quite a few pitfalls.&#xA;This post documents the entire process in full, especially those issues you only discover after migration.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
