KampányMűvek / 13 September 2026
The Engine and each site finally got separate lifecycles
KampányMűvek became a real platform when the shared Engine, generators and QA moved into their own repository, leaving each site with only its own content, templates, images and site-specific checks.
Situation
As long as shared developer tooling and client-specific site source evolve in the same history, every Engine fix turns into a site-by-site copying exercise. That may look manageable with only a few sites, but it quickly creates drift: the same generator starts living in several slightly different copies, and the source of truth becomes unclear.
Approach
We separated the shared generators, consent runtime, QA, build tooling and lifecycle tooling into the `kampanymuvek-engine` repository. Sites now use a pinned Engine artifact while content, templates, visual assets and site-specific contracts remain local. A dedicated `site-upgrade` path was added so changing Engine versions is an explicit, controlled operation.
Outcome
The Engine can now evolve and be versioned independently, while each site repository shows much more clearly what actually belongs to that site. A platform fix no longer has to be copied manually into five places; it can be propagated through an explicit upgrade process.