Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Note: This is issue is part of #2721129: Workflow Initiative and is only meant for planning and governance sign-offs. Work will happen in child issues of this plan.
Target version: Drupal 8.4
This phase will introduce the UI to create, manage and switch between multiple workspaces. It will also introduce a basic permissions model for viewing and editing content within a workspace based on the existing Entity Access API.
Most current prototypes, see comment #22.
For the initiative phase concerning the underlying API, see #2732071: WI: Workspace module roadmap
What is a workspace?
A workspace is a copy of the live site, that exists in parallel to the live site. Use a workspace when you want to prepare multiple new content items, that you want to go live at the same time, in a controlled manner.
A typical scenario can look like this:
Contrib references
See Workspace module for the current Drupal 8 implementation in contrib.
See CPS for a similar implementation in Drupal 7.
Sign-offs needed
Product manager
A product manager needs to sign-off on this plan because there's significant changes to Drupal's content workflow experience.
Release manager
A release manager needs to sign off because the scope and impact of the work are significant for core.
Sign-offs given
- Product manager - pending
- Release manager - pending
| Comment | File | Size | Author |
|---|---|---|---|
| #21 | workspace-scenario.png | 483.3 KB | dixon_ |
| #21 | workspace-concept.png | 364.05 KB | dixon_ |
| #13 | switcher UI compare.png | 76.35 KB | jojototh |
| #8 | ScreenFlow.gif | 2.65 MB | jojototh |
Comments
Comment #2
dixon_Comment #3
catchComment #4
timmillwoodComment #5
dixon_This plan still needs some work before it's ready to be reviewed by stakeholders.
Comment #7
dixon_Comment #8
jojototh CreditAttribution: jojototh at Pfizer, Inc. commentedLink to a prototype using "classic Drupal approach": https://marvelapp.com/1gb0ccb/screen/16998329
And here is an alternative using the outside-in approach:
Comment #9
dixon_Here's a YouTube recoding of the Drupal UX meeting where these prototypes were discussed: https://youtu.be/hf8AovBZflo
Comment #10
dixon_Simplified and updated the issue summary.
Comment #11
dixon_Removed links from the issue summary that has already been covered elsewhere.
Comment #12
jojototh CreditAttribution: jojototh at Pfizer, Inc. commentedHere is a prototype for the workspace updating and deployment process.
In this version everything is happening in the outside tray to visually help users understand that they are working with something which is outside their current workspace.
Features:
- updating workspace
- deploying workspace
- checking for conflicts
- conflict resolution
- previewing local/remote versions and changes
Prototype: https://marvelapp.com/14g1785
Comment #13
jojototh CreditAttribution: jojototh at Pfizer, Inc. commentedAttaching updated switcher UI, simplified and cleaned up to bring attention to the main CTA - Update & Deploy
Comment #15
dixon_Comment #16
dixon_Comment #17
jojototh CreditAttribution: jojototh at Pfizer, Inc. commentedUpdated prototype: https://marvelapp.com/1j46d6d/screen/25603635
Comment #18
dixon_Comment #19
dixon_Comment #20
dixon_Comment #21
dixon_Comment #22
dixon_Latest prototype from @jojototh: https://marvelapp.com/2db8i71/screen/26798746
Comment #23
dixon_Comment #24
Bojhan CreditAttribution: Bojhan as a volunteer and commentedWe discussed this on the product management call with Dries, Webchick, Yoroy, Bojhan, Gabor, Dick and Jojozef.
Overall the feedback was very positive, the concept aligns well with identified user needs (surveyed by Dries, and empirical evidence through customer visits by participants of the call). The execution so far, has been stellar involving the UX team through several reviews iterating on the design and testing with users (at Pfizer). This led to the entire product team giving thumbs up, to proceeding to the next phase.
The next phase is to detail and work out the plan for getting this into core. From our call we identified two challenges that need to be tackled for this to go in:
while a common scenario will be that a site has only a few workspaces (1/2) and thus the design should work well in this case. Given the size of the UI concept, user validation reduces the risk of implementing a UI that doesn't work and/or endless UI discussion as implementation details are hashed out.
Dick also raised the issue that the timeline for getting this to a mature state, might stretch the policy set for Experimental Modules. This will be adressed by release managers in #2721129: Workflow Initiative
A few additional notes from the call:
Comment #26
Bojhan CreditAttribution: Bojhan as a volunteer and commentedWe reviewed this on our product management call. We are wondering if there any updates, looking forward to this going into core.
Removing the tag for now.
Comment #27
timmillwoodWe've been working a lot in contrib on workspace module to build a 2.x version which will be the version we look to move into core. There are a number of issues we're working on which are highlighted in #2916089: [meta] Workspace 8.x-2.x.
This will then be used to generate a patch for #2784921: Add Workspaces experimental module.
Comment #29
amateescu CreditAttribution: amateescu for Pfizer, Inc. commentedAdding the full Workspace UI (WI Phase G2) has been folded into Phase G1, since the full UI is a beta blocker for including Workspaces in Drupal core 8.6, so marking this issue as duplicate of #2732071: WI: Workspace module roadmap.
Just for reference, the implementation issue for the full Workspace UI is #2949991: Add workspace UI in top dialog.
Comment #30
xjmUntagging since it was merged.
Such a pretty diagram!