When I committed to building Wapka, I had a clear destination. I didn’t yet know the path.
I understood HTML and CSS. But servers, databases, deployment, SSL, DNS — these were all unknowns. So I did what made sense: I started learning.
Year one: building the foundation
The first year was discovery. PHP. Databases. How a web server handles requests. Shared hosting versus VPS. Each concept unlocked the next.
I built prototypes. Early ones were limited — simple subdomain routing, basic file uploads, a minimal database layer. Each prototype taught me something. Each limitation pointed to what needed to improve next.
This is the real process: constant iteration. Each version teaches you something. Over time, those lessons compound into competence.
By late 2018, I had a working prototype. It could register users, create sites, and serve pages. That was the foundation.
Year two: scaling to a platform
The second year was about making it production-grade.
I acquired domain alternatives — wapka.co, wapka.site, wapka.website — building the brand piece by piece. I rebuilt the core into a modular engine. Added the theming system. Expanded file management. Built the first version of the visual builder.
In 2020, wapka.org became available. The brand was unified. The platform was ready.
The insight
People ask what it takes to build something substantial without formal training.
It takes clarity of vision. Knowing exactly what you are building toward. It takes consistency — working month after month without immediate feedback. And it takes a genuine connection to what you are creating — a reason deeper than curiosity.
I had that reason. I was building for a community I understood because I had been part of it. Every feature I added was something I would have wanted myself.
Continue reading: How Wapka grew from zero to 100,000 sites → How I acquired domains when it seemed impossible →