Re: Customers that make their own docs

[Paul Juska <paul -dot- juska -at- gmail -dot- com>]

This is a common problem with developers and code: ârebasingâ ones âfeature
branchâ off the âtrunkâ or âdevelopmentâ branch. Modern version management
tools, like GIT, facilitate this process by providing functions for
a) making formal commits (âpull requestsâ) to trunk, such that a developer
can subsequently b) play back (ârebaseâ) these commits against their own
âfeatureâ branch, highlighting potential conflicts along the way for the
developer to accept (ie. the new generic common code is valid and useful
for my branch), reject (ie. My branch contains superseding code specific to
my feature) or something in-between (ie. Update my feature branch with a
new snippet that takes the best of trunk and my own feature branch.)

 Many have explored and had success with using git and git-oriented tools
(like github) for managing and versioning non-code assets among teams
working collaboratively on the same asset, or subscribing to the same set
of underlying but evolving shared âlibrariesâ. In fact, I believe github
just announced a feature tailored to non-code users.

Atlassian has a great writeup on âGitFlow workflowâ - which is not just the
commands the tool offers, but how best to organize the teamâs workflow with
the tool to achieve delivery of multiple parallel âreleasesâ of the asset
in an optimized and traceable way.



On Tue, Mar 2, 2021 at 2:45 PM kafkascampi <kafkascampi -at- gmail -dot- com> wrote:

> Hi Techwr-l
>
> My company produces VR training, providing the system hardware, the
> software customers use to make their own training, plus an internet
> portal for tracking results etc.
>
> We have a central site for documentation and help, but some customers
> produce and manage their own docs and help based upon ours. I'm
> curious if anyone else has been in a similar setup and, if so, what
> tools you've seen for keeping docs in sync, besides just manually
> informing/ sharing updates with the customers. We do this now but at
> scale it would be a headache. I'm thinking some central system a la
> Salesforce or similar (but that can get expensive.) Or something that
> integrates into the customer's tools.
>
> Any ideas?
>
> thanks
>
> Chris
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | https://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as paul -dot- juska -at- gmail -dot- com -dot- 
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
> http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications?  Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions?  Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives