Lubinik did not start as a framework. I did not sit down one morning with a clean architecture diagram and a perfect plan for themes, plugins, addons, child themes, support plugins, generators, and design packs.
It started from a much less polished place: I was annoyed at WordPress.
I did not love Gutenberg. I had spent some time finding peace with Oxygen because it let me build WordPress sites without feeling trapped by the editor. But eventually that started to annoy me too. I am still a developer. I like understanding what is happening under the hood. I like touching the code, breaking things, debugging them, and slowly making a system make sense.
The first real goal was simple: build a theme for a BnB site. Nothing philosophical. Nothing grand. Just a real site with real content, rooms, local information, galleries, calendars, and the usual pile of practical details that always look smaller before you start.
At the same time, AI coding tools were becoming useful enough to experiment with. So the project became two things at once: a way to build a real WordPress theme, and a way to learn what AI could actually help with when the work was not just a toy example.
The framework appeared later
The first version was not elegant. It was a working thing. It had the BnB model, the templates, the admin fields, the frontend logic, the styles, the galleries, the calendars, and a lot of decisions that were still too close together.
But that is how Lubinik started becoming visible. Not as an idea first, but as a series of practical questions.
Which parts am I rebuilding every time?
Which parts belong to this site only?
Which parts should never have been in the same file?
That is still the most honest description of Lubinik: a personal WordPress framework that grew because I kept listening to the problems each project created.
