In the previous post, we discussed the challenges of migrating content from Obsidian to Hugo. Now, let’s dive into the automation that makes this transition seamless.

The core of this automation is a custom Rust script that processes Markdown files from my Obsidian vault and converts them into Hugo-compatible blog posts. This script ensures that the migration process is efficient, structured, and repeatable. In this post, we’ll explore the high-level architecture and workflow of the script, breaking down its key stages.

Front matter is the backbone of content organization in static site generators like Hugo. If you’re migrating from Obsidian—a popular note-taking tool that also uses front matter—you might encounter challenges aligning your existing metadata with Hugo’s expected format. This post explores these challenges, the key differences between Obsidian’s and Hugo’s front matter structures, and strategies for mapping custom fields effectively.

Creating this blog involved using modern static site generation tools, cloud deployment services, and a personal automation setup to streamline content management. In this article, I’ll guide you through the process, from the foundation of the blog to the automated workflows that keep it running efficiently.

I have moved my blog to a new platform! While my previous WordPress blog served its purpose, I felt some limitations that led me to make this change.

What’s New?

• My previous blog functioned as an almost complete CV, resume, and portfolio.
• This new blog will fully showcase what I can do and what I have done in a more structured way.
• The new platform gives me more flexibility to present my work in a way that better reflects my skills and expertise.
• There are no comment or like features on this blog, ensuring a distraction-free browsing experience.
• If you’d like to reach out, you can contact me via email or LinkedIn.

Why the Change?

I wanted a space that truly represents my professional journey without unnecessary distractions. The previous platform had some constraints that made it harder to display my work exactly how I wanted. With this new blog, I have more control over the layout, presentation, and overall experience.