My Workflow

I did not start out trying to build anything custom.

At the beginning, I just wanted a simple way to publish content on my website. Something fast, something clean, something that would not get in the way. Naturally, I ended up using a CMS. In my case, it was Decap, which works directly with Git.

It worked fine. I could write posts, upload content, and everything synced with my repository. But after using it for a while, I realized something.

The experience did not feel like mine.

The interface, the workflow, even the way content was structured, it all felt generic. It was designed to work for everyone, which also meant it was not really optimized for how I personally like to work.

That is when I decided to change things.

Instead of replacing the CMS, I kept it as the core system but built my own layer on top of it. A custom admin panel that fits exactly what I need. No unnecessary options, no confusing layouts, just a focused interface for blogs, projects, and media.

At first, it was rough.

Some parts did not sync properly. Sometimes content would not show up as expected. There were moments where things just stopped working and I had to dig through everything to figure out why.

But that process taught me more than using a ready made solution ever could.

Now the system feels natural.

I can open my panel, write something, and publish it without thinking about the backend. Everything is still powered by Git, but the experience is fully controlled by me.

That was the goal from the beginning.

Not to replace existing tools, but to shape them into something that actually fits how I work.

And in the end, that made all the difference.