A component content management system (CCMS) is a component-based database that stores individual topics for lots of doc projects. Writers grab the topics they need and integrate those topics into their documentation. The CCMS system facilitates re-use of content, so the same component (topic) can be re-used as needed in other doc projects in the organization.
For example, if the documentation for Widget X appears in Products 1, 2, and 3, then you write and translate the Widget X documentation one time, and all the other product doc sets include it in their outputs. You don’t copy and paste the same documentation three times (tripling translation costs and leading to all kinds of inconsistencies when Widget X gets updated).
Most CCMSs cost upwards of $50k per year and require content to be in DITA. If you want to avoid using a CCMS, could you use version control with tools like Github or Bitbucket to achieve a similar result?
Sure, you could put all your topics into a github repo, and then each writer could clone and pull the repo to their own system. But then you end up with a long list of topics on your local machine. Suppose you want only 100 of 1,000 topics? How do you avoid including the other 900 in your individual project? If using a static site generator, how do you filter out those files you don’t want?
I’m interested to know if anyone has strategies for implementing the same strategies as a CCMS but with version control and static site generators. This post by Eliot Kimber gives me hope that it’s possible, but I’m not quite sure how to execute it with Jekyll.