<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>migration on Publishing House</title>
    <link>https://publishinghouse.org/tags/migration/</link>
    <description>Recent content in migration on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/migration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating from WordPress to Hugo: A Practical Walkthrough</title>
      <link>https://publishinghouse.org/migrating-from-wordpress-to-hugo-a-practical-walkthrough/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/migrating-from-wordpress-to-hugo-a-practical-walkthrough/</guid>
      <description>Migrating a WordPress site to Hugo is one of the most common transitions in publishing infrastructure. The reasons vary — performance, hosting cost, maintenance overhead, security exposure — but the path through the migration is broadly the same regardless of why you are making the move. This is a practical walkthrough of what the process actually involves.
What You Are Gaining and What You Are Giving Up Before starting, be clear about the tradeoffs.</description>
    </item>
    
  </channel>
</rss>
