🇺🇸United States @worldlinemine

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

xjm → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

larowlan → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

At the request/suggestion of @smustgrave in the Drupal Slack #UX channel the UX group discussed this issue while gathered today and we considered the latest patch. In general we agree and confirm the patch is an improvement in useability though we need to work on some specific recommendations for the text of labels and the URLs for better consistency. We will be addressing this issue further at our meeting next Friday so please feel free to join us with any suggestions or concerns.

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

xjm → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

See this comment I left regarding today's discussion about gathering information on Drupalisms.
Comment #10 📌 Locate drupalisms that might create confusion among users Active

We discussed this issue at the Drupal Usability Meeting 2023-09-15 📌 Drupal Usability Meeting 2023-09-15 Fixed .

Housekeeping:

1. Deadline for collecting general opinions and suggestions on this topic will be through October 31st, 2023.
2. Temporary spreadsheet for aggregating comments and external discussions can be found here: Google Sheet - Temp
3. Governance of this temporary document will be performed by several community members who are actively participating in the weekly Drupal Usability Meetings. (They will edit and update the document as needed).
4. We plan to hold a Birds of a Feather session at Drupal Con Lille 2023 and encourage anyone interested in attending the con to please consider sharing their opinions at this session.

It is important to note that we are attempting to manage scope on this issue. We are primarily focused on Drupalisms as they pertain to the Card Sorting exercise performed in relation to the Admin Menu. During the opinion gathering phase of this issue we may add any reasonable suggestions to the spreadsheet for consideration; however, our focus will continue to be on the Admin Menu.

We do not expect to have any direct recommendations on changes to core. Instead, this information may be a good starting place for future discussions intended to see more specific action in that domain.

Thank you everyone for your comments thus far! Please keep them coming.

benjifisher → credited worldlinemine → .

Usability review

We discussed this issue at 📌 Drupal Usability Meeting 2023-09-08 Fixed . That issue will have a link to a recording of the meeting.

For the record, the attendees at today's usability meeting were @AaronMcHale, @Emma Horrell, @benjifisher, @rkoller, @simohell, and @worldlinemine.

1. Switch the message type to info from its current type of warning
2. The long sentence should be moved to the bottom of the proposed Info message.
3. The list of overrides (and possibly the long sentence) should be placed in a collapsed detail element.
4. Remove line of text describing the "config file".
5. Add a link to https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-... →
   1. There might be a better link source or new documentation as opposed to the API documentation but for now adding the suggested link would be an improvement.
   2. Test the link both inside and outside the details element.
6. Use the translated label, not the value (for example - “Site name” instead of “name”).

Suggested format for the message would resemble the following example -

This form contains values that have been overridden:

• The value for "Site Name" has been overridden. 'Drush Site-Install' has been changed to 'Druverride'.

Changes to these values can still be saved, but the overridden values will take precedence.

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

Today we discuss this issue for 15 minutes at the weekly community UX meeting. The hope is to continue to discuss it at future meetings as well as to socialize the issue and solicit more feedback from a variety of users (potential as well as different roles/skill levels).

It's important to note that this issue is not focused/intended to result in "altering or changing" any language. Its goal is to build/collect a list of terms that have anecdotally been referred to during casual conversation while working on Drupal issues/sites in the past.

Anyone who has terms to suggest should please feel free to leave comments including those terms. We'll collect them and work to share them with the broader community and use them in the context of the Admin Menu organization.

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

benjifisher → credited worldlinemine → .

chrisfromredfin → credited worldlinemine → .