If you have told us (or privately thought) Documentation isn't working: You are correct. It isn't. Yet. Since early on in the private beta of Documentation, we’ve used a simple, rigid structure: Tags => Topics => Examples + optional sections At the time, users wondered if this was the right s...

Turning some of my comments into an answer: My gut says leave it as StackExchange.Programmers forever (especially now that it's becoming clearer to me that the main problem is user confusion, in which case, documentation). Is that mapping expensive / risky for future maintenance on SE's end? One...

Just a thought: What if, instead of T-SQL, you instead documented a few SE things as part of the initial experiment? E.g. the SEDE schema, the API, the StackExchange JS object. Not to mention the public dumps could use some documentation, this could help with the issues in that thread too by givi...