Je suis tombé là-dessus récemment et je suis d’accord pour dire que ce n’est pas idéal. Je pense que la solution la plus simple que nous puissions adopter pour l’instant est de créer un brouillon contenant le contenu du post rejeté et de lier l’utilisateur à celui-ci afin qu’il puisse le modifier et le publier à nouveau.
J’ai ouvert une PR pour mettre à jour ce comportement :
main ← ux-requested-changes-draft
opened 09:39PM - 01 Apr 26 UTC
Currently when a post is queued for review, and the reviewer requests edits — we… send a message to the poster that looks like this...
>
> Hi username,
>
> We’ve reviewed your post in [example topic](#) and have some feedback for you.
>
> Reason: Does not meet posting guidelines
>
> Feedback: Moderator feedback goes here
>
> You can edit your original post below and re-submit to make the suggested changes.
> ___
> this is the original post content
> ___
> Thanks,
> Sitename Moderators
The problem with this is that "you can edit your original post below" isn't actually true — it's just the content of the post so you can copy and paste it into the composer and try again.
This change creates a new draft of the rejected content and links to the posting user's drafts, so they can more easily edit it and resubmit. This is a clearer flow than the current message.
The new message looks like this
> Hi username,
>
> We’ve reviewed your post in [example topic](#) and have some feedback for you.
>
> Reason: Does not meet posting guidelines
>
> Feedback: Moderator feedback goes here
>
> A draft has been saved with your original content. You can find it in your [drafts](/my/activity/drafts), make the suggested changes, and resubmit.
>
> > this is the original post content
>
> Thanks,
> Sitename Moderators
1 « J'aime »
