Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a "Feedback" link to Gutenberg #8725

Closed
wpscholar opened this issue Aug 8, 2018 · 6 comments
Closed

Add a "Feedback" link to Gutenberg #8725

wpscholar opened this issue Aug 8, 2018 · 6 comments
Labels
[Type] Enhancement A suggestion for improvement. [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable

Comments

@wpscholar
Copy link
Member

Is your feature request related to a problem? Please describe.
It is quite helpful when desiring feedback, to make the process as easy and fast as possible. At present, the user has to go to the WP site, find the plugin, go to support, and start a new topic.

Inspired by: https://wordpress.org/support/topic/gutenburg-provide-a-place-feedback-here-button/

Describe the solution you'd like
A simple "Feedback" button placed in the editor (say top right). I think it would make sense to link the "Feedback" button to the Gutenberg support form (https://wordpressdotorg.polldaddy.com/s/gutenberg-support) as this form can automatically create GitHub issues where appropriate. This would help to get feedback rapidly, including from those who might be less able, which means a broader sample of users is available for helping to make it as simple to use as possible.

@wpscholar wpscholar added [Type] Enhancement A suggestion for improvement. Needs Design Needs design efforts. Needs Dev Ready for, and needs developer efforts Needs Decision Needs a decision to be actionable or relevant [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable labels Aug 8, 2018
@karmatosed
Copy link
Member

karmatosed commented Aug 8, 2018

@wpscholar we have one as a link in the menu. I think over having it directly in the editor this works for now. Removing those links for decision, design and dev until we agree on way forward.

@karmatosed karmatosed removed Needs Decision Needs a decision to be actionable or relevant Needs Design Needs design efforts. Needs Dev Ready for, and needs developer efforts labels Aug 8, 2018
@karmatosed
Copy link
Member

For reference what we have now:

2018-08-08 at 18 59

@wpscholar
Copy link
Member Author

@karmatosed I think that is very easy to overlook... especially for new users who are trying to edit their own posts. At a minimum, should that be part of the onboarding tooltips?

@karmatosed
Copy link
Member

I wouldn't be against adding it to a Tip. I standby I don't think it needs to be as obvious as a button in the actual interface, whilst feedback is amazing not everyone wants or should be forced to do it.

@jaumecantarino
Copy link

This is a good and helpful improvement for gutenberg and it will help solving problems faster.

@aduth
Copy link
Member

aduth commented May 31, 2019

I had thought there was a separate issue for it (perhaps someone else is better at search than I am), but I think it would be nice to include some visual indication on the editor screen that the plugin is being used at all. Currently, it's easy to overlook whether you're running WordPress stable or the plugin version of the Gutenberg block editor.

As a point of reference, Automattic's Calypso project includes an "environment badge" in development environments:

https://github.com/Automattic/wp-calypso/tree/master/client/components/environment-badge

I can imagine a similar pattern being applied for Gutenberg, including development information, and support/feedback links.

@mtias mtias closed this as completed Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Enhancement A suggestion for improvement. [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable
Projects
None yet
Development

No branches or pull requests

5 participants