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>
This commit is contained in:
Tammo ter Hark 2026-11-16 19:51:19 +01:00
commit 80a3d4a079

6
.gitignore vendored Normal file
View file

@ -0,0 +1,6 @@
# Client variant definitions contain confidential house-style values (client
# names, colors, fonts, logo files). They are NOT kept in this public repo:
# store them in the private variants repository or locally, and point
# variants/build.php at that folder (2nd CLI argument or RESPONDAGE_VARIANTS_DIR).
variants/*.json
variants/README.internal.md