Need a plan to handle WiX documentation when there are significant schema changes

[barnson]

Encountered at: wixtoolset/wix@HEAD

Detail:
A lot of the new non-reference doc on https://wixtoolset.org/docs/ will deal well handling multiple (mostly-compatible) versions of WiX. That is not true of the schema and API reference doc, even for (mostly-compatible) versions of WiX, mostly because we generate them; the schema doc comes from the .xsd schema files and the API doc from built assemblies. Two obvious options:

• Version the reference doc (e.g., https://wixtoolset.org/docs/api/v5/wixtoolset.data/accessmodifier/). Biggest downside is that Docusaurus (v2, at least) would almost certainly choke.
• Build them from v5 and annotate version-specific schema and API (e.g., Introduced in v5). That works well for additions (e.g., the new attributes available to naked files) but falls apart quickly for bigger changes. That means eventually we have to version anyway.

[BryanCrotaz]

Look at EmberJS docs for a really user friendly way to do this with all versions in one site and a drop-down at the top to choose the version. It is built by an open source docs builder that you could probably use.