How This Site Came to Be

Vibe coding · By Peter · 3 min read
How This Site Came to Be

Vibe coding is daring to follow an idea without knowing where it will end. It is creating without fear of erasure. A way of working where every version counts, even if it never remains online.

This site did not come into existence all at once.
It grew. Through doing. With trial, error, erasure, remaking — and above all: a lot of enjoyment.

In recent months, I have delved deeply into building. Not from a strict plan or an end goal, but from curiosity. What happens when you just go for it? When you create things without them needing to be “finished” immediately?

It turned out to be surprisingly much.

From Idea to Site — and Sometimes Back to Zero

In the past three months, I have created dozens of temporary projects. Small experiments, half-formed ideas, even complete sites. Sometimes I built an entire website in a day. Everything included. Only to completely remove it a few days later.

And that felt… good.

Not because it was a waste of time, but precisely because I learned so much from it. Every project — even the deleted versions — brought new insights, including how you should or should not guide an AI. About structure. About rhythm. About design. About what works and what doesn’t.

Letting go of “this must continue to exist” created space to play.

Vibe Coding: Building by Feel

Vibe coding is essentially: not too technical, not too rigid, but building by feel. Observing, adjusting, going live, changing again. Sometimes more intuitive than rational — and precisely for that reason surprisingly effective.

I do not have a classical coding background. For years, I sat next to developers, observed, contributed ideas, but wrote little myself. That perhaps made the step daunting, but also accessible: I had nothing to unlearn.

Why Replit Works So Well (for Now)

Replit played a significant role in this.
What makes the difference for me: everything is live immediately. You see what you are doing straight away. No complicated setup, no local detours. Building, observing, adjusting — in one flow.

Especially without heavy technical baggage, that is gold. It invites you to act. And yes, I notice I am slowly moving towards tools like Claude.ai, but Replit remains a favourite for now. The pace, the immediate result, the experimentation — it suits how I work now.

Learning by Watching (and a Lot of YouTube)

With a YouTube Pro account, a world opens up, somewhat addictively for years.
So many creators, so much explanation, so many clever tools and workflows being shared. Not academic, but practical. Just watching how someone else thinks, builds, solves.

That learning by watching — and then immediately trying it myself — has partly shaped this site.

Design Directly in HTML: Aura & Gemini

In recent weeks, something else has been added: designing directly in HTML.
With Aura, I have created an enormous number of designs in a short time. Not static images, but real layouts that work immediately in code. That accelerates the process enormously.

And Gemini proves surprisingly strong in this. Especially in thinking along about structure and visual logic. It sometimes feels as if design and technology truly come together there.

This Site as a Snapshot

This pb.nl site is therefore not an endpoint.
It is a snapshot. A place where everything I have learned along the way comes together. Where experiment and experience meet.

Perhaps it will change again tomorrow. Perhaps it will stay like this for a while.
But what is certain: it was built with attention, curiosity, and joy.

And that feels — just like in the past with Perfectly — actually the most important.

Peter
Peter
Creative Directors
Oprichters van Studio PB.NL met 20 jaar ervaring in fashion, e-commerce en AI-gedreven innovatie. Samen bouwen we aan de toekomst van creatieve technologie.