Hi Syed,

A very wide question that is usually touched in training sessions. The key thing to remember is, that everything you track needs validation by you when you upgrade to the next version. So in 99% of the cases, you are way better of in tracking only the files you deliberately changed. So only the human-altered files and in turn the scripts you have to automate machine-altered files.

A training will explain

• CustomerSpecificFiles in InstallTool (potentially the InstallTool interactive option to track 'touched' standard files)
• CustomerSpecificFiles over ISHDeploy (Copy-ISHFile cmdlet)

As a history and vision statement, the following conference session could help... see Reducing Deployment Effort and Automating Business Processes with SDL Tridion Docs Dave De Meyer (SDL) on Vimeo ... this of course is not a training session. Another video in that third-party conference worthwhile mentioning for more technically oriented people is Understanding Tridion Docs components, architecture, and extensibility Kateryna Momot (SDL)- on Vimeo

And I hope somebody pointed you to the videos on https://community.sdl.com/product-groups/sdl-tridion-dx/tridion-docs/ as well.

Best wishes,
Dave

Thank you Dave! Looks like I have some homework to do. :-)