Voting starts in March for the Drupal Association Board election.
Note: This is issue is part ofand is only meant for planning and governance sign-offs. Work will happen in child issues of this plan.
Target version: Drupal 8.2
The proposal here is to just rename and drop-in Workbench Moderation an experimental module into core.
The purpose of this is to:
- Embrace what has already become a popular workflow module for D8 (aGov, Lightning, Deploy module etc are already using it)
- Uncovering bugs in core with forward revisions, while in experimental state
- Get early feedback on the functionality by end-users
Proposed module name: Content Moderation (
For the very first iteration the Workbench Moderation module itself serves as the initial prototype.
Required sign-off before commit
|Product manager||Needs work||Pending some resolution to new UX debt introduced by numerous state transitions (eitheror ), and a default way to view content in different moderation states (e.g. adjustments to the existing admin/content view or separate moderation tab, etc.)|
|Release manager||Needs work||Pending data integrity issues introduced by uninstallation:and the security impact review|
Required before stable release
- Save button scalability - This is here because while the existing pattern and problem is already there before this module, the additional options make it worse.
- Make sure exposed filter for workflow states is a drop-down, not a text field.
- Optimize transition screen to be easier to tell at a glance what is happening there (maybe re-incorporate —> arrows from D7?), and reduce visual clutter (e.g. remove machine_name field, since that’s visible in Edit).
- Figure out how to visually indicate the current state of a node (e.g. “Needs review”) beyond just published/unpublished. (Use the D7 yellow box pattern?)
- Ensure it is not possible for moderation states + entity status to get out of sync:
- A stable Workflows module -
- Usability test of entire feature since it’s a 90% feature. This will likely uncover all kinds of other things (e.g. does the tabs pattern work, vs. the yellow box thing in D7?).
Move menu item to admin/config/ instead of admin/structure/
- Make the names of permissions the descriptions of permissions instead (which are a lot more clear), and remove the descriptions to help cut down on visual clutter.
- Tagging off the above, do we need "human readable" versions of state transitions at all? Then we wouldn't need to provide a UI for it that we subsequently need to fix.
- Consolidate the two admin screens to one admin screen with two tabs, ala D7, so that the admin link is immediately useful.
- On the edit state transition screen, remove the colon from "From/To draft" so the star doesn’t look weird.
- Explore duplicating state transition permissions here as well, since they're very related to the task at hand.
- Explore much fancier user interfaces for defining states/transitions; e.g. Mautic, the-graph, Mulesoft, Concrete 5 -
Won’t-have (for this feature)
- “My workbench” dashboard from D7.
- Workbench Access-like gargantuan permission matrix.
- A full-blown translation workflow.
Other related discussions
A product manager needs to sign-off on this plan as the above phases are required as part of a planned initiative.
A framework manager needs to sign-off on this plan as the above phases introduces major API additions (archive and purge).
A release manager needs to sign-off on this plan as the above phases have impact on shippability.
The sub-system maintainers for the Entity API needs to sign-off on this plan as it significantly impacts the Entity API.
|#34||Screen Shot 2016-06-27 at 11.41.24 AM.png||74.05 KB||webchick|
|#10||Screen Shot 2016-06-27 at 11.35.59 AM.png||56.34 KB||webchick|
|#10||Screen Shot 2016-06-27 at 11.34.32 AM.png||102.11 KB||webchick|
|#10||Screen Shot 2016-06-27 at 12.05.37 PM.png||82.26 KB||webchick|