Embracing Hugo: Why I Chose Independence Over Audience and Centralization

Table of Contents

Embracing Hugo: Why I Chose Independence Over Audience and Centralization

Some time ago, I started to write study outputs or things I liked on Dev.to, but for reasons I can’t quite pinpoint, I eventually stopped. Now, as a personal goal, I’ve decided to revisit that habit. However, it began with some questions: Should I continue using Dev.to? Is centralization on platforms like Dev.to the purpose of the internet, rather than personal blogs? Do I prioritize having an audience over hosting my own blog?

With these questions in mind and some free time, I opted for Hugo to host my own personal blog.

What is Hugo?

Hugo is a high-performance static site generator designed to simplify the process of creating websites. Utilizing markdown for content creation and a powerful templating system, Hugo swiftly transforms your content and templates into a complete, static website.

Why Host My Own Blog?

No Lock-In: Owning My Content, Anywhere, Anytime

One of my biggest concerns with platforms like Dev.to and Medium was the risk of lock-in. Entrusting my content to a third-party platform meant relinquishing control over its fate. What if the platform changed its policies? What if it shut down unexpectedly?

I can host my website anywhere, migrate it effortlessly, and rest easy knowing that my content is mine to control. For example, I started the first version using GitHub Pages, then I switched to Netlify. I still use centralized platforms, but I can switch anytime.

I believe that information should be free. It’s unacceptable to see someone paying to read content that is intended to be free. Of course, there’s a difference between selling content/courses that you build with this purpose and blog posts that used to be free on Medium.

What Am I Losing?

Great Dev.to Community

The Dev.to community stands as a shining example of inclusivity, collaboration, and support within the realm of tech and programming. With its welcoming atmosphere and dedication to fostering meaningful discussions, the possibility to navigate between the same content using tags is fantastic. I’m considering adding a pipeline step to sync my posts here with Dev.to, but at another time.

Audience

Of course, it’s important to acknowledge the trade-offs. By opting for Hugo, I accept the reality of a potentially smaller audience. Unlike platforms like Dev.to and Medium, which boast vast communities and built-in discoverability.

It made me think about what my goal is here. For now, the answer is to write about things that I like. If it can help someone else, I’ll be happy; if not, I’ll be happy too, because I’m enjoying writing.

Final thoughts

In embracing Hugo for my personal blog, I’ve reclaimed control over my content while acknowledging the trade-offs of a potentially smaller audience. Through this journey, I prioritize the joy of writing and the freedom to share what I love, irrespective of reach.