Changing Content Models
Challenges of Rolling Out Content Model Changes
As content requirements increase, content models must be updated. In legacy CMSs, the number of environments is typically limited e.g. to a single QA environment. This slows down teams working on content models, as model changes must now be coordinated to avoid cross-team interference during testing and roll-out.
Iterate Models Rapidly
No more fighting over who gets to use the QA environment for testing: Commitspark is based on Git branches that let you keep model changes separate as long as needed, be it for development, testing, or any other tasks your teams need to complete before release.
Legacy CMS
- Typically only a single environment is available where model changes can be tested
- Setting up new environments is slow and involves copying lots of data
- Content model and content entries in QA environment become stale
- Unrelated content model changes cannot be easily tested in parallel
- After QA is complete, any changes must be applied again in 1:1 to production environment
Commitspark
- Create as many separate branches as needed, to independently build & test changes
- Branches are light-weight and do not require copying data
- Any changes in production can be merged into development branches to stay in sync
- Changes can be independently tested per-branch at any time
- Merging a branch to production brings along all changes; no extra steps required