This Community and the Wiki… but you knew those
Software I couldn’t work without:
Scripting is an interesting idea. I’ve frequently toyed with writing a gcode sender, specifically to include some high-level action building mechanism, but alas: time. Plus I think you need to be careful scripting CNC work. gcode is already far more deliberate than most people’s brains, hence the large learning curve. Personally I find intermediary black-boxes (like, ehem, CC) massively frustrating, as I have no idea what they are doing under the covers with my gcode.
To make scripting most viable, it would need to pair with a customer post-processor to (maybe) align with some new or custom gcode parameters with corresponding smart actions and that moves us away from gcode being a standard, universal language and into what I’ll call “Apple territory”.
Now, I’m not sure if you were actually looking for general meta feedback, but I’ve had this in my brain for a while so here goes…
The wiki is… a wiki, which I personally love. However the mediawiki search algorithm is a dumpster fire and rarely seems to find anything if you don’t have the exact page title (this isn’t unique to the Shapeoko wiki).
The Discourse search is far superior, so I’ve been coming here first for questions, the wiki second, then usually back here so that Will can link me to the wiki article I couldn’t find with the search in the first place. There are some mediawiki search plugins that claim to make it less horrible, but I’ve not tried them.
I’d love to see the discourse (community) site expanded and more of it’s features leveraged.
The Shapeoko forums… they’re a trove of knowledge, but again, hampered by mediocre search functionality. Plus, they seem far more focused on the S1/S2 generations than the new stuff, but maybe that’s just what I’ve run into.
Then there’s docs.carbide3d.com which is an interesting combination of excellent information and oddly outdated things and broken links. I actually really like the presentation of the information here (the S3 assembly instructions, for example)
If I were king I’d reduce the above down to two: A community resource and a formal KB. I think Discourse is a modern and superior platform to phpBB, so lock the old forums and funnel all new work to this space.
Take the current mediawiki and give it an organizational overhaul and combine the content from docs.carbide3d with it. Mediawiki should be flexible enough to lock down certain “official” entries away from the community to prevent trolls from changing the assembly docs and the like.
Daggon book right there… sorry I’m stuck in the airport thanks to lovely winter weather.