Adobe Captivate Distributed Development using GitHub or other source control systems

[mobcdi]

Is there any recommended configuration to allow distributed development using GitHub or other source control systems?

I'm not looking for multiple users to work on the same captivate project file at the same time but would like to be able to check out a base project and access other common assets, develop a new topic and update the central repository/source control with the published output, the project file and all associated assets in case someone else on the geographically dispersed team wants to use it as a starting point for their project or needs to correct something and re-publish.

From reading some posts captivate wasn't suited to working on network drives, is this still the case? 

[Lilybiri]

Yes, no networked drives, still the case.

[mobcdi]

So how woulds teams usually work on captivate projects with possibly multiple deliverables and numerous assets common to the projects.

Is source control in use much?

[Lilybiri]

Since I a mostly work 'solo', just have some simple tips: keep commonly used assets in separate CP-files. The Library of any project can be opened as external Library in any other project. Maybe you are aware of that, but most CP-users totally ignore that functionality. Good structured libraries can save a lot of time. Custom themes, theme color palettes and Preferences are very easily shared as well. Notes and captions can be used/shared using the XML or Word export/import. Just a couple of ideas.