↓Skip to main content

Migration to Hugo

··172 words·1 min
Table of Contents

Moving to Hugo #

I recently decided to migrate my technical blog to Hugo. The main reason for this change was the ability to manage all my posts using GitHub, leveraging version control for better document organization and management. As part of this migration, all articles needed to be converted into Markdown.

Previously, my blog was hosted on WordPress. While it served me well for years, I found it increasingly cumbersome for my needs. Running WordPress involves significant overhead, relying on Apache, PHP, and MySQL just to serve static content. In contrast, Hugo uses a lightweight binary to generate static HTML files from markdown, which can then be served by Apache or any other web server.

Both platforms have their advantages, but for me, reducing resource overhead and improving version control were decisive factors.

Switching to markdown brings additional benefits:

  • A standard format for all articles.
  • Easy output conversion to formats like PDF, Word, HTML, and more.

Looking ahead, I plan to share more detailed insights into my Hugo-based setup and its implementation.