The Procrastination Ends Here

Hey there, fellow tech enthusiasts! 👋

So, I’ve finally done it. After what feels like eons of procrastination and an eternity of putting it off, I’ve finally taken the plunge into the world of static blogging. As a fresh graduate with a shiny new Bachelor’s degree in Computer Science and a few months to kill before diving into my Master’s, I figured it was high time to scratch that persistent itch. It’s been on my to-do list for ages, sitting there, staring at me, probably judging me a little. But here we are – procrastination: 0, me: 1.

“The secret of getting ahead is getting started.” - Mark Twain

The “What If” Phase

Initially, my JavaScript-averse brain considered the path of least resistance:

1npx create-react-app my-awesome-blog

But something held me back. It’s not like I’m head over heels for JavaScript or anything. Quite the opposite, actually. But I’ll admit, it has its moments. The npm plugin ecosystem is pretty clever, and hey, I’d be the only one using it anyway, right?

Maybe it was the allure of trying something new, or perhaps it was the voice of reason whispering, “Do you really need a full-blown React app for a simple blog?” Or maybe it was just the caffeine talking.

The Great SSG Hunt

So, I embarked on a journey through the land of Static Site Generators (SSGs). My first stop? The GitHub repositories of my fellow developer friends. You know, for “research purposes.”

Jekyll: The OG of SSG’s (maybe?)

Many were using Jekyll, and I must admit, that hacker theme had me seriously tempted. It was like the cool kid on the block. But something felt… off. Maybe it was the Ruby ecosystem, or perhaps it was just my insatiable curiosity pushing me to explore further.

Gatsby: Close, but No Cigar

Next up on my SSG speed-dating adventure was Gatsby. While it’s undoubtedly powerful, the available themes didn’t quite tickle my fancy. Let’s just say they weren’t really my cup of Java (see what I did there?). The search continued.

Hugo: Love at First Site (Generator)

Finally, I stumbled upon Hugo, and it was love at first sight. The theme I’m currently using (which you’re feasting your eyes on right now) immediately clicked. It was like finding the last piece of a puzzle I didn’t even know I was solving.

Setting it up was a breeze, with only a few minor hiccups that were easily resolved with some good old-fashioned tinkering:

1brew install hugo
2hugo new site my-awesome-blog
3cd my-awesome-blog
4git init
5cd themes
6git clone https://gitlab.com/gabmus/hugo-ficurinia.git
7# Edit config.toml
8hugo new posts/hello-world.md

Honestly it’s that simple. And here we are. I’d like to give a huge shoutout to Gabriel Musco for creating this awesome Ficurinia theme. It’s licensed for use under GNU AGPLv3, and I’m incredibly grateful for the work put into it.

The Great SSG Debate: Build or Adopt?

Here’s a plot twist for you: while I’m using Hugo for this blog, my main site is powered by a custom-built npx cra. Why the split personality, you ask? Well, it’s complicated. Like my relationship with semicolons (just kidding), it’s all about striking a balance between creative freedom and practical efficiency.

The Case for Ready-Made SSGs

Existing static site generators are like Swiss Army knives for web developers:

1. They’re easy: All those decisions you don’t want to make? Someone else already made them. Just read the docs and tweak.
2. Plugin paradise: Need a feature? There’s probably a plugin for that.
3. Markdown madness: Most use standard Markdown, making it easy to hop between SSGs if you’re feeling adventurous.

The DIY Dream

Building your own SSG is like making a sandwich from scratch. And I mean really from scratch – like growing the wheat yourself:

1. Learning galore: Ever wondered how RSS feeds work? You’re about to find out!
2. Control freak’s dream: Every decision is yours. It’s like being the benevolent dictator of your own little web kingdom.
3. Future-proof content: With a focus on standard Markdown or json, your content is ready for whatever the future holds.

The Verdict

So, should you build your own SSG or adopt an existing one? As with most things in tech, it depends on your goals.

If you want to focus purely on writing and content creation, an existing SSG like Hugo, Jekyll, or Gatsby might be your best bet. It’s like taking a high-speed train to Blogville.

However, if you’re itching for a deep dive into web technologies and don’t mind a steeper learning curve, building your own SSG can be an incredibly rewarding experience.

Me? I’m playing both sides. Custom SSG for my main site, Hugo for this blog. Because why choose when you can have your cake and eat someone else’s too? Taking both the pills.

Wrapping Up on the SSG …

So there you have it, folks. My journey from procrastination to publication, from “maybe someday” to “holy crap, I have a blog with actual content.”

What’s Coming Up on This Blog?

Honestly? I have no clue. It’s like opening a mystery box, but I’m the one putting stuff in it. I’ve got some mind-blowing tech and software I’m itching to talk about (seriously, I tried this thing the other day that had me going “OMG! This is next level!”).

I also recently acquired a Raspberry Pi 5, so expect some tinkering tales from that front. But hey, who knows? I might end up blogging about everything under the sun. The beauty of having your own corner of the internet, right?

I should mention that this is my first time blogging and writing about tech stuff. While the ideas and experiences shared here are entirely my own, I’ve utilized AI-assisted tools for language enhancement. Specifically, I’ve employed AI writing assistants and Grammarly to refine grammar and improve sentence structure. However, it’s important to note that these tools have been used solely for linguistic refinement and not for content generation. The thoughts, opinions, and insights expressed in this blog are the product of my personal experiences and intellectual efforts.