Problem/Motivation
Content moderation is planned to ship (like Workbench moderation) with Draft, Needs review, Published, and archived.
Are these the best defaults? Is it too many? or too few?
Proposed resolution
Have the following default configuration:
States:
- Draft
- Published (set to "default" and "published")
- Archived (set to "default" and not "published")
Transitions:
- Draft->Published
- Draft->Draft
- Pub->Draft
- Published->Published
- Published->Archived
- Archived->Draft
- Archived->Published
That gives both forward revisions (drafts) and not-delete-but-hide (archive/unpublish) capabilities. Site owners can of course expand that list to add review states as appropriate for their case.
See #2755073: WI: Content Moderation module roadmap (comments #11 - #19) for additional previous discussion.
Comments
Comment #2
Bojhan CreditAttribution: Bojhan as a volunteer and commentedIf we manage to fix the UI before 8 July, this should not be needed. See #2757349: WI: Deal with scalability issues in the UI
Comment #3
webchickIn the parent issue, Crell proposed:
States:
- Draft
- Published
- Archived
Transitions:
- Draft->Pub
- Draft->Draft
- Pub->Draft
- Pub->Pub
- Pub->Archived
- Archived->Draft
Talked to @Bojhan and both he and I agree this sets a nice compromise of being a functional starting point for 80% of websites, while reducing the horror of checkboxes and table rows in a few key screens.
Comment #4
webchickAlso I think we can attempt to come up with solutions to both this issue (plan A) and #2757349: WI: Deal with scalability issues in the UI (plan B) in parallel. Unpostponing.
Comment #5
Dries CreditAttribution: Dries commented+1 to the states and transitions proposed by Angie in #3.
It might be worth adding 'Archived -> Published' though.
Comment #6
Crell CreditAttribution: Crell at Platform.sh commentedI'm obviously on board with #3. :-) That's the bare minimum I think we can have and still have a meaningful system. I'm not against adding Archived->Published if we don't want to force people to go through Draft to get there. No strong preference.
Comment #7
amateescu CreditAttribution: amateescu for Pfizer, Inc. commentedGiven that we have an approved direction and a patch in #2757349-42: WI: Deal with scalability issues in the UI, do we still want to restrict the states and transitions to the ones decided upon here?
Comment #8
Crell CreditAttribution: Crell at Platform.sh commentedI don't think that patch impacts the discussion here at all. It makes the transition list UI better and more scalable, but we still need to define the default states.
That said, I'm going to be brave and say that the list from #3 is acceptable since no one has objected. Updating the summary and setting to RTBC. Maintainers, slap back if appropriate (but be gentle, please). :-) I included Archived->Published per Dries request, but don't feel strongly about it.
Comment #9
amateescu CreditAttribution: amateescu for Pfizer, Inc. commentedOk then, I committed a patch to the working branch of content_moderation and will post a new one in the main issue, so I'm going to call this issue fixed.