Can we have a 'guide to wonderland' meta.
'Wonderland' is all our rules which mostly consists of lots of different rabbit holes.
When I started on Code Review I spent a good couple of months looking up and exploring various rabbit holes. Whilst it was nice to don the name Alice, it was a lot of work. Even now there are undiscovered rabbit holes, and I have to ask other people on the site for links to basic rules.
To me this screams that there's a massive problem. If I, one of the top 25 on CR main and 11 on meta, don't know the rules or how to find them, what hope do any of our users have?
Currently we have:
- Our close reasons.
A friendly and basic overview of our close reason meta thread.
- Our close reason meta thread.
This is the most in-depth explanation of our rules, but it lacks edge cases.
Also a lot of our rules are based off the wording in this and so I think changing it would lead to confusion.
- Our help center.
I don't use it much, and as far as I can tell provides no more information than our close reason meta thread does. It also doesn't have a history, making some meta posts confusing. And also is only editable by moderators.
The closest thing to what I'm requesting is the close reason meta thread, but a lot of different things rely on that thread, and I think this is sufficiently different.
When answering posts on meta I base my answers off of the close reason meta thread, and use other meta posts when it doesn't fulfill my needs. This has highlighted to me that it's hard to know what all the rules are on Code Review as they're all on meta, but not really in the same place. This means that it is easy for me to inaccurately say that something is on/off-topic as I forgot that a specific meta post exists.
At minimum I think we should create a 'guide to wonderland' post that lists all of our rules in categories, with their exceptions also listed.
We could do more in-depth things such as provide descriptions in the post, but I'm unsure what extent people would want this guide to be.
It should be noted that this post would need to be updated as time goes on, however since our close reasons don't change much it would be rare. It should be noted that determining if closure/reopening is correct or not wouldn't be in this list, but would be related.
Should we have a 'guide to wonderland'?
What should the content be? (A list/short descriptions)
I've produced a starting version we can build off. It's best if you preview the file in Stack Overflow. So answer this question and paste the raw file as the answer. But don't post it :)
I think it'd be good to get some feedback on if it's missing anything important.
Currently I think the sections under code and review type work pretty well. A couple of the leaf categories are quite large, like broken code and comparative review. This may be because we don't have an FAQ for these to close similar questions as duplicates of.
I'm not sure if I like how the format works for 'general' site policies.