The Resume addon is not finished, and that is useful to admit.
It points toward an idea I still like: modeling resume data inside WordPress as structured content. Resumes, sections, entries, templates, outputs, skills, entry types. A CV as content, not only as a file.
But the current addon also exposes a bigger architecture question: what happens when one site needs more than one Lubinik addon?
Most Lubinik sites so far have had one main domain addon. A BnB site uses the BnB addon. A shelter site uses Shelter. A professional site uses Freelance. A comics site uses Comics. The Lubinik presentation site uses Showcase.
Resume is different because it could reasonably live beside another addon. A professional site might use Freelance for projects and services, then Resume for CV data and downloadable outputs.
The core is close, but not fully there
The core plugin already has some entity-type ideas. But parts of the shortcode manager, registry, filters, admin UI, and template ownership still behave like there is one main addon in charge.
That does not mean the whole system is wrong. It means multi-addon support should become a deliberate future evolution, not an accidental side effect.
The Resume addon may become the pressure test for that. Not now, not rushed, but eventually. It is exactly the kind of secondary domain layer that could prove whether Lubinik can support multiple addons without turning the admin into a noisy mixed list.
