RH 2019 Classic - What files need to be tracked in (external) source control system?

If others are pushing and pulling, make sure you communicate any changes being pushed regarding the constantly changing variable files and output templates (like output pathways, output file names etc).  We usually discard those files in our branches to avoid a collision.  

Essentially you put the whole project in source control with the exception of the files mentioned on my site. The idea is you can later pull out a complete version of your project.

The exceptions stated are ones that are unique to each user and/or that RoboHelp will build.

The SSL content is different. Many argue that it can be rebuilt by pulling the source files so why add to the volume stored. A possible snag is that way down the line, changes in RoboHelp may mean that the output may not be 100% the same. For example, a skin may have changed in some way, whether or not that matters will depend on the scenario.

A worse scenario would be if the project was created in a Classic version of RoboHelp and years later the output had to be recreated. At that point only the new UI might be available and the output was with a webhelp skin. Webhelp skins change to responsive skins in the new UI so the old output could not be recreated. The content would be there but not the appearance. This is perhaps an unlikely scenario but that's for you to decide. 

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

There are arguments for and against. I'll reply in more detail in the morning. 

________________________________________________________
My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

See https://www.grainge.org/pages/snippets/snippets.htm#sourcecontrol