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.We're getting many issues regarding UX and UI changes in Drupal 8 issue queue, for example the proposals to support mobile.
I would like to propose that we nail this down here and now and rigidly enforce this workflow bar extreme mitigating circumstances.
Proposed workflow:
If the the issue requires a UI change:
1. Provide a clear explanation of the issue with supporting screenshots.
2. Tag the issue with "needs design review".
3. Wait for UX feeback, proposals and mockups etc. If this does not come in a timely manner we can move forward and propose design solutions - in this case tag the issue with "needs design".
4. Based on UX proposals etc we move to a design phase and work on comps/design proposals etc.
5. Once the design is settled we can start implementing it with code/patches.
In essence this means we start with UX feedback, get the design worked out then write some patches. Jumping to code solution is not the right workflow for UI changes.
We need to document this somewhere also - probably in http://drupal.org/contribute/development somewhere so we have something to refer contributors to when first getting involved.
Comments
Comment #1
Jeff Burnz CreditAttribution: Jeff Burnz commentedops, typo in title...
...and I opened a docs issue to get some docs rolling for this in our main contributors guide, since there is nothing there for design or UX at all: http://drupal.org/node/1150710
Comment #2
Bojhan CreditAttribution: Bojhan commentedComment #3
JohnAlbinIndeed. Trying to re-work Drupal's admin forms to be more responsive is going to take a lot of coordination.
Comment #16
smustgrave CreditAttribution: smustgrave at Mobomo commentedIf this is referring to the admin theme there is https://www.drupal.org/project/drupal/issues/3066007
But the new frontend theme olivero was written with mobile in mind. So think this can be closed.