@danbjoseph mentioned here that a rough outline/structure would help with addressing the repo count question and I think it would be helpful for all these great questions @wonderchook is asking, too.
@adammichaelwood what do you think of doing a little bit of outline/structure iteration as an input to some of these discussions? I think the challenge with the current documentation is the lack of "glue" between the different parts. There are a number of different ways those connections could be established and those might affect the desired tooling. For example, I can imagine a structure in which the Collect widgets are documented alongside the XLSForm syntax that produces them. Alternately (or additionally?) I can imagine a Collect user guide that is targeted at someone who trains enumerators and doesn't write forms. That narrative could be entirely separate from the form building guide. In the later case, maybe something more approachable like gitbooks is the right tool for the purely user-facing component.
@wonderchook, to answer your question about current translation efforts, there are about 140 people involved in ongoing translations of Collect. Some languages are more active than others but I'm sure many would be interested in translating documentation.
That said, I'm not entirely sure what docs would be high-value to translate. My experience is that many organizations want training guides that relate to their specific forms so there may not be a ton of value to translating user-facing documentation. It may be the case that, for example, translating the XLSForm spec would be highest value.