Documentation Strategy

Side note

Open question what is in scope of rusEFI wiki and what is out of scope.

• A of Nov 2022 the best cost/benefit ratio is to work on TunerStudio layout and TunerStudio field tooltips and help articles which are embedded into "Help" of specific dialogs.
• Andrey does not believe in text documentation on wiki
• Content problem versus infrastructure/structure problem like https://github.com/rusefi/rusefi_documentation/issues/250 and https://github.com/rusefi/rusefi_documentation/issues/168
• We are probably not trying to teach people how to tune HP Academy does that better

If we still hope to untangle the mess of four Wikis

As of April, 2020 the strategy is to move from MediaWiki https://rusefi.com/wiki/ to https://github.com/rusefi/rusefi/wiki/

A full list of (Legacy) mediawiki pages is available at https://rusefi.com/wiki/index.php?title=Special:AllPages

Arguments for github:

1. Access control
2. Better change review process
3. Better history and version control management

Arguments against github

1. Weird workflow with two separate git repositories
2. Weird inconsistency of markup language between two git repositories

Arguments for mediawiki:

1. ?