"Nudge" mockup (discussion)

My experience with "nudges" is that they should not be editable but allow text to be added before and after the "nudge."

Visually a "nudge" should standout. Below is example of the only nudge that I am currently using the Webform issue queue.

The Webform module's issue queue is for bugs, feature requests, and planning. Please post general support questions to Drupal Answers. You can also ask questions or help answer questions on the #webform channel on Drupal Slack.

I also include this "nudge" on the Webform's module create an issue page.

Here is the list of all the Webform nudges.

Maybe a "nudge" could be inserted using a token. ([nudge: help], [nudge: inclusion], etc...)

I like @jrockowitz suggestion for the nudges to visually stand out. This will bring awareness around certain behaviors and perhaps illicit good behavior through example.

Nudges should be editable, but only when posted by a user and not anonymously. I think if posted from a shared account, the nudges should always read the same.

+1 to @jrockowitz and @volkswagenchick's suggestion of a visually distinguishable nudge. I would go as far as to say that if the nudges can be posted only by a subset of users (such as maintainers), the nudges should appear separate in the comment flow (similar to how we have automated issue transitions right now).

For nudges to not be editable, they have to be minimal and generic and they should mostly point to resources rather than trying to say a mouthful. I am leaning towards having them uneditable; editing opens up a can of worms around how much deviation should be allowed from the original nudge text and if it starts becoming unhelpful to everyone involved, especially to whom we intend to help.

Further, I would want the ability to select multiple nudges. For example, a nudge can cater to both a cultural difference to respond to a personal attack. Someone able to create a nudge will select all that apply so that there is only one message that goes out (which would not escalate the situation as much as multiple nudges), and all the relevant links are included.

Lastly, while I prefer nudges to not be editable, I would like a field to describe the nudge with an example. For example, if a user selects "Personal attack", they could also write quote from the offender's text to describe why it is a personal attack.

Testing the copy paste from the webform module

Values and principles

As a member of the Drupal community, in the Webform issue queue, we want to uphold the behaviors expected in the below values and principles. Impact gives purpose Build software that everyone can use Foster a learning environment Decisions should be collaborative Everyone has something to contribute Choose to lead Embrace change Every person is welcome; every behavior is not Be constructively honest, and relentlessly optimistic Seek first to understand, then to be understood Be sure to have fun

As per CWG slack conversation

Transcript from CWG internal slack:

ultimike
I think we’re close on the 5 initial nudges.
We are looking for a designer to help.
Once we finalize the nudges and design, we’ll do a blog post to announce the (manual) pilot program.

Neil Drumm
We can probably keep it simple for design. Nudges shouldn’t have much more visual importance than the (productive parts) of the discussion.

Donna Bungard
What about an icon like this to go in a box as shown.
[file attached]

aburrows
maybe a druaplicon

Adding attributions to those who contributed.

Tagging for design

Thanks @ultimike for these samples.

Initial feedback.

• Links should be underlined. The blue on lt green does not meet color contrast standards for accessibility. (3.82:1 ratio).
• I think the background should be free of images for accessibility as well.

I think the Druplicon will be an appropriate image.

This is now deployed and looks like:

With code:

<div class="nudge"><p>This discussion appears to discourage contribution from some participants by assuming a level of education or exposure to information. This can discourage folks that are new to a conversation from asking for help or getting involved. Consider providing the new contributor with links to help them learn the topic or concept.</p>
<p>For more information, please refer to <a href="https://www.drupal.org/about/values-and-principles#foster-a-learning-environment">Drupal’s Values and Principles #3</a> of fostering a learning environment: long-term contributors should be role models by admitting their own shortcomings and mistakes, being vulnerable, and by giving others the same respect that was once given to them or <a  href="https://jvns.ca/blog/2017/04/27/no-feigning-surprise">this article about not feigning surprise</a>.</p>
<p><a href="https://www.drupal.org/about/values-and-principles#be-constructively-honest-and-relentlessly-optimistic">Principle #9</a> can also be useful here: be constructively honest, and relentlessly optimistic. You can be optimistic and supportive by giving suggestions for how to improve their contributions.  By being helpful, you encourage people to accept feedback and act on it.</p>
<p>This comment is provided as a service (currently being tested) of the Drupal Community Health Team as part of a project to encourage all participants to engage in positive discourse. For more information, please visit <a  href="https://www.drupal.org/project/drupal_cwg/issues/3129687">the meta issue for this project</a>.</p></div>

This made a little incremental progress on #3080422: Links inside surrounding text fail WCAG Use-of-Color in Bluecheese theme, now all help and status messages underline links instead of bolding them. I also made some small changes to the colors and margins to align the nudge styling with other messages & help in the theme.

(I edited #29 to use the regular filtered HTML text format instead of full HTML. Inline styles and one-off style tags always cause problems in the long run, and this conflicted right away.)

The templates are located in this issue: https://www.drupal.org/project/drupal_cwg/issues/3193832