Sorry for the very late reply on this. I feel like this is a pretty plausible way to grow our contributor-oriented content without some of the downsides of wikis (given the review process and clear scope that you outlined).
That said, some of the topics you outlined at the top seem user-focused/like they should go on the main site (or other documentation venues):
- platform building instructions, musl, android, mipsel, ios, etc, cross compiles
- tiers and support levels
- user groups / meetups
- lists of links to ides, libraries, other tooling etc.
- collections of videos, talks, blog posts
- bibliography / references
- high-profile projects?
- profiling tips
- lists of interesting tools to use on/with rust
And a couple were a bit ambiguous (not sure if the “hacks” here are for hacking on rustc itself, or just for using Rust):
- testing hacks
- debugging hacks
Can you elaborate on why these topics seemed like a good match for the dungeon, given that they seem of interest to the user community?
Maybe a different way of asking this is: is the split primarily about audience (user vs contrib)? I could imagine that we host some user-oriented content in the dungeon as a kind of pipelining/maturation process (for stuff that’s still changing rapidly, or where we want to iterate for a while before going fully public).