57eae599

By: Lucien Huber <im@lcnbr.ch>

add documentation quality review and improvement plan

User request: Can we make a useful addition to the docs? Make a thorough critical review and add a plan to improve

Follow-up request: looking at the plan, we should 1. emphasize making python, and cli reference better, clearer and less visually janky and more thorough (even if it is autogenerated)  . The point about main and docs is a bit moot since this docs branch is just to prepare a pr. afterwards onlly main is authoritative. I also agree that the manuals, and examples are way too shallow, and that we should integrate all the docs..

Follow-up request: also make sure the developper docs / architecture is not outdated
GitHub
Time to Start Worker time Duration Time to finish Idle
Config 2s 12s 12s 14s 2s
Eval 11s 1m03s 1m03s 1m14s 0s
Build 1m07s 3h31m29s - - 5s
Test 16m46s 12m33s - - 0s
Deploy - - - - 203h11m12s
Suite 2s 3h45m19s - - 203h11m20s

Timeline

Config Eval Build Test Failed Retried Compressed gap
0s1m2m3m4m5m6m7m8m9m10m11m12m13m14m15m16m17m18m19m20m21m22m23m24m25m26m27m28m29m30m31m32m33m34m35m36m37m38m39m40m41m42m