An important note to keep in mind - the changes I'm planning for should be copy-related only. While there may be some concerns about the current state of the close modal or the post notices, those are out of scope for my current project.

I'd like to think that these are about 90% there. From my current set of feedback these are significantly better than the current text and I'm really excited for y'all to see them. Do note, these aren't final and set in stone, so I'm open to suggestions, concerns, and other feedback - but it'd be really helpful if you can be clear about what I can do to improve them. Also, please try to focus on discussing one close reason per answer for voting and comment-replying purposes.

1. Close modal

   • Inform close voters of when to use the close reason. While many active reviewers already know this, we want to give enough info that new voters and flaggers understand these reasons, too.
   • Help voters differentiate between close reasons, particularly in the case of "needs detail" and "needs focus".

2. Asker post notice

   • Inform the asker why their question was closed and give them action items to improve it. Emphasize that this isn't a permanent state if they work to improve the question.
   • Incentivize improving the question by explaining why it is necessary (i.e. if you fix it, you will get a better answer).
   • Link to guidance where it exists.
   • Remove any guidance that suggests asking a new question from all close reasons.

3. Public post notice

   • Inform viewers why the question was closed
   • Give guidance on how to help improve the question or what to do if the closure seems to be unnecessary (either due to error or the question being improved).

4. Overall

   • These close reasons need to be applicable network-wide (within reason - yes, I know duplicate closure doesn't really happen on Code Review).
   • Help unify the usage of close reasons a bit.
   • If available, link to help guidance.

1. Ensure that people understood that a question needed to be out of scope before it could be closed for migration - "better suited to site X" is not a reason to close if it's otherwise on topic.
2. Ensure that people understand that they should not (as we say) "migrate crap".

An important note to keep in mind – the changes I'm planning for should be copy-related only. While there may be some concerns about the current state of the close modal or the post notices, those are out of scope for my current project.

I'd like to think that these are about 90% there. From my current set of feedback these are significantly better than the current text and I'm really excited for y'all to see them. Do note, these aren't final and set in stone, so I'm open to suggestions, concerns, and other feedback – but it'd be really helpful if you can be clear about what I can do to improve them. Also, please try to focus on discussing one close reason per answer for voting and comment-replying purposes.

1. Close modal

   • Inform close voters of when to use the close reason. While many active reviewers already know this, we want to give enough info that new voters and flaggers understand these reasons, too.
   • Help voters differentiate between close reasons, particularly in the case of "needs detail" and "needs focus".

2. Asker post notice

   • Inform the asker why their question was closed and give them action items to improve it. Emphasize that this isn't a permanent state if they work to improve the question.
   • Incentivize improving the question by explaining why it is necessary (i.e. if you fix it, you will get a better answer).
   • Link to guidance where it exists.
   • Remove any guidance that suggests asking a new question from all close reasons.

3. Public post notice

   • Inform viewers why the question was closed
   • Give guidance on how to help improve the question or what to do if the closure seems to be unnecessary (either due to error or the question being improved).

4. Overall

   • These close reasons need to be applicable network-wide (within reason – yes, I know duplicate closure doesn't really happen on Code Review).
   • Help unify the usage of close reasons a bit.
   • If available, link to help guidance.

1. Ensure that people understood that a question needed to be out of scope before it could be closed for migration – "better suited to site X" is not a reason to close if it's otherwise on topic.
2. Ensure that people understand that they should not (as we say) "migrate crap".