Hi Dave, the templates in the CMS as well as the pages have an internal versioning in the CMS itself. This is most often used in development. There is no built in moving changes from one system to another but there are external tools like http://www.erminas.de/en/web/products/cms-sync-tool.html that make it possible to move changes to attributes, elements, and single lines in templates e.g. from development to testing or production.
The CSS/JS and additional external files are different. Some users keep them in the CMS to have a single point for the project where all files are. This could be either a template (including versioning) or a file in the file system / asset folder. Others keep those files at an external place like a git repository and move them manually or by any automatism to the servers that deliver the content. HTH as a little overview. Please feel free to ask anything in addition. As you are new to the CMS and are familiar with .NET development maybe the SmartAPI (http://www.smartapi.de/en/homepage/) for programmatic access to the CMS could be interesting for you as well. Best, Hilmar On Monday, June 1, 2015 at 5:22:20 PM UTC+2, David Hutson wrote: > > Hi Everyone, > > I am a complete newbie to Reddot Cms but I would like to find out how > people manage source control / release management with Reddot Cms. I have > inherited a site in version 11.1 and I am use to managing changes with git > and nuget packaged deployments and powershell. I would appreciate any > advice on how people control and deploy changes. I'm hoping that there is > maybe a commandline way of packaging up changes to then deploy to another > instance. > > thanks > > Dave > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/d/optout.
