1. Introduction:

I finally did the thing every developer eventually does: I built my own blog.

But I didn't just "install" a blog. I built an engine. Most people today pick a platform that works like a pre-furnished apartment - you move in, but you can’t move the walls. I wanted a workshop where I own the foundation, the wiring, and the blueprint.

This blog is built from scratch - Svelte 5 on the frontend, Rust on the backend. This post kicks off a devlog series documenting how I’m designing, building, and inevitably refactoring a platform I own end-to-end.

2. Why Build a Blog in 2025?

There are roughly a million excellent ways to publish words on the internet. So why add another?

So why add another?

Because for me, this is not just a place to host text. It is a Playground without Constraints.

When you use existing tools, you eventually hit a ceiling. You want to try a new interaction, a custom layout, or a weird idea that doesn't fit into a standard "post" format, and you find yourself fighting the tool instead of building the feature.

By building this from scratch, I’ve removed the middleman. If I want to experiment with a specific logic or a complex visual experience, I don't have to check if a plugin supports it. I just build it.

More importantly, this is about Ownership. I wanted a long-lived project where I get to think about the "Why" behind the architecture -not just shipping a feature and moving on, but understanding how the whole machine breathes in the real world.

3. What this series is about

I’m not planning to follow a strict textbook here. Instead, this devlog will be a look under the hood at the problems I’m solving as they come up. Here’s a taste of what might appear in the feed (though definitely not in this exact order - ( ❛ᴗ❛ ) ):

• System Design & Repo Layout: How to organize a multi-language stack (Frontend + Backend) to ensure the code remains modular, maintainable, and easy to refactor as the engine evolves.
• The Content Engine: This is where the magic happens. I’ll be diving into Content Management - moving beyond just "saving files" to building a Custom Markdown pipeline that can actually handle the weird and interactive features I have planned.
• The Logic of Communication: Designing the Internal Bridge. This focuses on the "why" and "how" of the stack’s handshake - making sure the different layers talk to each other securely and efficiently behind the scenes.
• ...

4. The Goal

The ultimate goal of this blog is to share whatever I’m working on - from raw ideas to polished solutions - across the entire spectrum of my interests. I want to document the "how" and the "why" so the solutions are out there for anyone else who might need them.

More soon.