We plan to use Scroll Versions for managing our end-user documentation for our software products. Eventually we expect to have 5,000+ topics. In a typical release maybe only 10-15% of these topics will be updated. Between releases we may have small day-to-day updates to fix minor issues, like correcting typos.
One of the key decisions we have to make before we begin is whether to organise the documentation into separate spaces, say a space for each product which seems to be a common approach, or whether to create one single space for everything.
To help us make this decision I would like some advice about how Scroll Versions performs with very large documentation sets.
Assuming we’ll have 5,000 plus topics, I would like to know if Scroll Versions is stable and capable of managing such a high volume of documentation or whether you recommend that we break the documentation up into separate spaces.
Secondly, if only 10% of topics have been changed in a particular version, when we go to publish that version does Scroll Versions process all 5,000 topics during the publishing process or just the 10% of topics that have changed?
Please let me have your thoughts/recommendations on what you think would work best — a single, large space or multiple smaller spaces — or is the plugin capable of dealing equally well with either of these options?
Please sign in to leave a comment.