나만의 기술 블로그 웹사이트를 만든 이유.

Why I Built My Own Technical Blog Website

I wanted a place to write about software engineering, projects I’m building, and things I learn along the way.

There are plenty of existing blogging platforms, but building my own gave me something those platforms couldn’t: complete control.

Why Build It Myself?

The main reasons were pretty simple:

• Full control over the design
• No platform limitations
• A project I could actually use
• Freedom to experiment with new technology
• A permanent home for my technical writing

I also wanted the site to feel like my website, rather than another profile hosted on somebody else’s platform.

Sometimes the best reason to build something is simply because you want to understand how it works.

The Technical Side

The site uses tools I already enjoy working with, including:

• TypeScript
• React
• PostgreSQL
• Express
• Drizzle ORM

Having my own backend also means I can build features exactly how I want instead of adapting everything around a blogging platform’s API.

For example, creating a post can eventually be as simple as:

const post = await createPost({
  title: "Why I Built My Own Technical Blog Website",
  published: true,
});

Enter fullscreen mode Exit fullscreen mode

Things I Want to Add

Some ideas I have for the site:

1. Better code syntax highlighting
2. Search
3. Tags and categories
4. Draft posts
5. Reading time
6. RSS support

Current Progress

Feature Status Blog posts Done Markdown Done Tags In Progress Search Planned RSS Planned

A few things still need work:

• [x] Render Markdown
• [x] Create posts
• [ ] Add search
• [ ] Add RSS
• [ ] Improve SEO

Was Building It Worth It?

For me id say, yes.

Using something like Medium or Dev.to would have been faster, but that wasn’t really the point.

I wanted to build something I could keep improving, learn from, and actually call my own.

You can find more of my projects on GitHub.