Commit graph respondage_vanilla/variants/build.php
Author SHA1 Message Date
dd8714b6a0 feat(variants): copy per-client assets (fonts/css/images) automatically in build.php
The definitions dir (private variants repo) now has a standard layout per
client: <client>.json + <client>/files/... + <client>/css/variant.css.
build.php copies <client>/ into the generated theme folder, so a
client-specific font or css is part of the variant by default.
README updated accordingly.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-11-16 21:09:02 +01:00
80a3d4a079 feat(variants): thin client themes on one shared code base
Architecture: a client theme extends this mother theme via <extends> and
contains only a generated config.xml + its own files/ (logos). LimeSurvey
inherits all views/css/js/images from the mother, so changes here apply to
every variant immediately.

- variants/<client>.json holds ONLY the house-style values (colors, fonts,
  font sizes/weights/colors, logo files, logotopmargin, custom fonts).
- variants/build.php generates ../<client>/config.xml from the mother
  config.xml + the json: only those values are replaced, <extends> is set,
  <engine> is emptied except <optionspage>. Unknown option keys fail the
  build loudly, so drift is caught at build time.
- Client definitions (variants/<client>.json) are gitignored (see .gitignore)
  and live in a PRIVATE variants repo or locally; build.php reads them from
  there via its 2nd argument or RESPONDAGE_VARIANTS_DIR.
- README.md: "Client variants" workflow.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-11-16 19:51:19 +01:00