TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Customers that make their own docs From:Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 3 Mar 2021 08:58:17 +0000 (UTC)
GitHub Wiki is exactly what comes to mind for me. The files are in markdown -- most savvy customers should be able to handle that. It has a mechanism for keeping separate branches for different customers. You could merge your doc updates into their branches, for example. That would take a little coordination to go without any conflicts. But if you can declare certain markdown files off limits to them, then you can merge easily.Â
You can still own the files, and they issue pull requests for you to update their branches on the hub. Then you can merge your changes into their branches, and tell them to pull that back down. The point is, you can review the pull request for any compliance you're worried about. You can also do some formatting to make the WIKI look right.
I'm pretty sure you can get at the individual markdown files. Certainly with GitHub Pages you can. The point here is that if you have a DITA work flow, you should be able to process a book of markdown files into a PDF, and give it whatever branding you want. There might be other markdown-to-PDF solutions out there... I haven't looked into them.
The thing to avoid is a system that tries to erect a silo. AFAIK, Git is pretty good about that.
cud
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com
