Continuing the discussion from:
Y’all probably know that I’m not a huge fan of having the Guide Post articles on the forum.
Having static code examples hosted in a separate location from the challenges is a recipe for out of date example code.
Also, there just aren’t a lot of good tools to make a PR type workflow for approving modifications or updates to the solutions.
Honestly, if I was creating this Guide Post stuff from scratch, I’d host it in a website deployed from a Git repo where users and mods could make PRs to improve or update solutions and could create issues to flag out of date or confusing solutions.
With more modern tools, it is possible to test these solutions regularly and automatically against the curriculum and flag issues with out of date code. I’ve done a lot of work professionally with that sort of thing for Julia, Rust, and Python and would be interested in a project to do something similar here. It’s a fair bit of work, but it provides better quality documentation and user manual/guides with a more robust review process that ultimately results in less work down the road.
We get a better product out the other end with easier maintenance and transparency, and its an example to our campers of modern best practices for code examples in documentation.