Post History

Articles can be made closable in configuration (does not require a code change), *but* it's a global, network-wide change, so we'd need to make sure that doesn't have negative consequences for any of our communities.

The down-side is that currently there is *one* set of close reasons per community (not even per category -- per community).  Some of the close reasons, which assume questions, don't make sense for articles.  Some do.  There'd be some user confusion unless we can rewrite the set of (default) close reasons so that the set makes sense in all places where one sees the list.

It seems like it would (eventually) be possible to configure close reasons per community *per post type*, and that would solve this problem.  I have an idea for how that would work in the user interface, and if I understand the code correctly (I might not!) this seems possible to implement.  But I don't know if it's that straightforward or how long it would take for somebody to make that change.

To summarize: we could make articles closable on the network today, and they'd have the same set of close reasons as questions do.  Some day in the vague unspecified future, we might be able to have close reasons that apply to only one post type (question or article).  Making articles closable affects all articles on all communities.  Should we throw that switch now and hope to clean up the reasons later, or should we wait?

I am aware of one case where being able to close articles specifically as duplicates would be very helpful (the Code Golf sandbox).