When we started Qysh Me, the first real decision was not what to write. It was what to build it on. Qysh Me means “how to” in Albanian, and the plan was a how-to portal for a language that had almost no useful content online. That is an ambitious content operation, and the platform had to serve the content, not the other way around.
We were a tiny team with no funding. So I made a decision I still stand by: we built on WordPress instead of writing something custom.
Why not build our own
It is tempting, especially when you are technical, to build your own system. It feels like control. In practice, for a content business, a custom CMS is a tax you pay forever. Every hour spent building an editor, a media library, or a comment system is an hour not spent creating the content that is the actual product.
WordPress had already solved all of that, and solved it better than we could have alone.
What WordPress gave us on day one
- A publishing workflow our writers could learn in an afternoon, not a manual
- A mature editor, media handling, and revision history for free
- Categories and tags to organize a growing library from the start
- A plugin ecosystem for SEO, caching, and forms, so we could add capability without writing it
- A theme layer that let us control the look without touching the core
The real lesson
Choosing WordPress was not a compromise, it was leverage. It let two people run something that looked and worked like a much bigger operation, because we spent our energy on content and audience instead of reinventing a CMS.
My recommendation to anyone starting a content-driven product: unless your core innovation is the publishing technology itself, do not build the publishing technology. Stand on a mature platform and put your scarce hours into the thing only you can make. For Qysh Me, that was Albanian-language knowledge, and WordPress is what freed us to focus on it.