Changes for SR2022

[raccube]

Kit

• Introduction - Reference to IDE in first paragraph #222
• Simulator - Remove as we’re not shipping one for now #223
• IDE - Remove entire section #224
• New content for Programming section #225
• Batteries page: Where does the kit-support@ email address go? #247
• Brain Board Page: It’s an ODROID U3+ #245
• Servo Board: Add note about PLOD?
• WiFi: Needs removing or updating depending on whether we end up with that being shipped, regardless, there’s a reference to the forum so needs updating
• Programming: s/(sr.robot)/\13)/, also remove reference to IDE #227
• Python: 2.7 -> 3.9 #241
• Functions: could add some more depth here
• Libraries: update list of libraries
• SR Module: complete review of page #282
• Hide the Radio & Compass docs #234
• Motors: complete review of page #249
• Power: complete review of page (it’s r.power_board now too), also add individual output currents #235
• SR2022: Update Ruggeduino documentation #220
• SR2022: Custom Ruggeduino Firmware Update #221
• Servos: complete review for SR2022 #251
• Vision: complete review #219
• Markers: remove references to libkoki
• Generate SR2022 Marker PDFs #239
• Remove simulator from code editors #237
• Git repositories: remove as there is no IDE #226
• Troubleshooting: Update ref to sr.robot #264
• Update the interactive troubleshooter for SR2022 #268
• Tutorials / Basic Motor Control: Update Python code, and link to Python 2 tutorial at the bottom #284
• Create API cheatsheet #231
• Remove the user accounts information #242
• We need a page on environments for sr.Robot3
• Verbose Mode We don't think we need to document this for teams
• Debugger on robot
• Diagrams and pictures can be added to vision section; see SourceBots docs for example
• Add instructions for flashing SD cards #257

Game

• Update the rules
• Microgames #258

[trickeydan]

Some docs that will be helpful for updating the API section: https://static.trickey.io/sr-robot3-sphinx-test/

[PeterJCLaw]

Suggest that we break the remaining tasks out to their own issues and close this one? It's not clear to me that keeping this (otherwise year-specific) issue open is helping us, especially since the year is now underway without the proposed changes here.

[trickeydan]

We have completed SR2022. Copying outstanding to new issue