Problem/Motivation
Child issue of #2758623: [meta] Redesign workflow configuration page to better visually describe the flow.
Proposed resolution
In an effort to revamp the workflow configuration page to better visually describe the flow, the following design change was proposed:

This is an individual component of a larger design overhaul.
Remaining tasks
- Discuss and address any issues or blockers with implementing this.
- @see parent issue for user testing of the whole design.
User interface changes
As pictured.
API changes
TBD.
Data model changes
TBD.
| Comment | File | Size | Author |
|---|---|---|---|
| create-new-workflow_png.png | 38.84 KB | sam152 |
Comments
Comment #2
ifrikAccording to our UI standards, verticable tabs should be used for the settings that users can safely ignore (for example because it's metadata or because fields have good default settings), or if it's something like the Email settings on the user account page.
"Placing functionality which is part of a certain workflow within vertical tabs is discouraged, the user should be able to skip the vertical tabs.2
https://www.drupal.org/docs/develop/user-interface-standards/vertical-tabs
Obviously, we can disregard such standards, but then there should be a good reason for it.
Comment #3
sam152 commentedThere is another RTBC patch which opens the form in a modal instead. If the intention of this change was to bring all that information "closer" to the main form without losing context perhaps that will go some way to address the problem. #2830584: Use modals for creating, updating, and deleting workflows, with a new DialogFormTrait
We also have the issue that with this approach the transitions are not reorderable.
Putting as needs work until these kinds of questions are answered. In the meantime, no reason we can't work on the other improvements.
Comment #15
smustgrave commentedThank you for sharing your idea for improving Drupal.
We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!