I kind of think a new site for just CR might be better. IMO, 1) you need new close reasons, and most of the existing ones shouldn't be used (e.g., dupe close shouldn't happen), 2) research effort should probably not be a downvote reason (otherwise it might turn into "-1 because you didn't read / don't agree with Joe's blog about code style"), 3) CRs shouldn't generally be required to be useful for future visitors, though they might end up being useful.

@jrh I would agree that a site of its own would be ideal, when we can gather the user base for it. Which we can't currently, we can't even gather enough for general programming Q&A. We shouldn't open up ghost town communities, so the idea is to host code review as a category here for now, then let it spawn off into a community of its own when/if it gets enough users to support it.

@‭jrh‭ As for close reasons, maybe we should bring that up on general meta as a feature request and discuss a close vote mechanism that gives category-specific reasons? So that when you close vote a post in the Code review category, you get Code review-specific close reasons only.

Right now close reasons are per-community, not per-community-per-category. We could adopt a convention like "[CR] reason" and "[Q&A] reason" for the ones that are unique to a category, until category-specific reasons are possible.