History: A theme managed in Git

             # {{page}}

## Use case

- You have a [https://en.m.wikipedia.org/wiki/Development,_testing,_acceptance_and_production|Development-Testing-Acceptance-Production (DTAP)] workflow
- You have a custom theme (vs tweaks on a Tiki theme with some ((Custom CSS))
- Your theme evolves somewhat independently from the rest of the code development
- You care that the theme is up to date on instances beyond production

## Option 1

- Use ((Manager|#instance:checkout|php tiki-manager instance:checkout))
- Use branches to deal with major changes of the theme (Ex.: ((Bootstrap)) 4 vs 5)

## Option 2

If various Tiki instances on the same server, use symlinks to point to a shared directory which contains the theme. This directory can be managed by Git or just be files on disk.

## Related links

- ((Sync Dev-Prod Servers))
- ((dev:Divergent Preferences in Staging Development Production))
- ((System Configuration))