Lubinik is not the thing I thought I was building at the beginning, because at the beginning I was not trying to build a framework at all.
I was trying to build a BnB theme, understand WordPress better, and use AI coding tools without giving up my own judgment.
Then the files got too long. The theme knew too much. The plugin carried too many specific assumptions. A child theme became messy enough to teach me what a cleaner child theme should be. A shelter site forced the BnB logic out of the core. A shortcode manager appeared because I wanted admin control without a visual builder. A scaffolder appeared because repeated addon setup should not depend on copy-paste or cheap AI labor forever.
Project by project, Lubinik became a system.
A framework as working memory
Now I think of Lubinik as working memory.
The parent theme remembers the generic site mechanics I do not want to rebuild. The core plugin remembers the shared plugin-side infrastructure. Addons remember the domain models that belong to specific site types. Child themes remember the visual identity and page shells of real sites. Support plugins remember how translation, SEO, and structured data should connect to the system. The scaffolder remembers the repeated structure well enough to generate it.
It is not a product I am trying to sell. It is not a public starter kit. It is a personal framework that grew from real projects, real refactors, real annoyances, and a lot of decisions that only made sense after I had built the wrong version first.
That is why this site exists: to document the project honestly while it keeps changing.
