Documentation Backlog

[robojumper]

I went through all past issues and tagged labelled them when I determined that they need documentation. First of all, every issue that made changes to base game code (and did not fix a HL bug) has one of the three labels needs-docs, de-private/const, doc-one-line-fix. Here's what they mean:

• needs-docs: This issue needs a full documentation page.
• de-private/const: Unspectacular change that only de-((private|protected)write?|const)-s a variable). Could possibly be merged into one page.
• doc-one-line-fix: A bug fix that can be described in a single line, does not need example code nor "how to use" docs and should probably also be merged into one page with a big list.

I've applied the labels to my best judgement, but it's possible to upgrade/downgrade the labels ("this deserves a full documentation page because...") later (when reviewing the PR that adds documentation, for example). We won't miss any issues because all issues that should be documented in any form have one of the labels.

Note that the docs script will need special handling for the consolidated pages.

[robojumper]

Prefer the links in this issue for a list of issues to document, as clicking the colorful GitHub labels will take you to a search page that only shows open, not closed issues.

[pledbrook]

I'm confused. The links in the issue description seem to take me to exactly the same page as clicking on the labels. By the way, mad respect for labelling all the issues!