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 opt-in for users to share diagnostic information #4651

Closed
westonruter opened this issue May 4, 2020 · 8 comments
Closed

Add opt-in for users to share diagnostic information #4651

westonruter opened this issue May 4, 2020 · 8 comments
Labels
Blocked Groomed P1 Medium priority UX WS:UX Work stream for UX/Front-end

Comments

@westonruter
Copy link
Member

Feature description

In order to start building up a database of themes and plugins which are AMP-compatible, we need to get user consent to share that information. Sharing validation errors with amp-wp.org will be very useful not only to discover themes/plugins which are unintentionally AMP-compatible so in that they only make changes to the admin or they only output AMP-compatible markup on the frontend, but will also reveal issues with themes/plugins which we thought were AMP-compatible but actually aren't (and we should report the issue to the theme/plugin author or take down the entry from the ecosystem page).

Once we have the database, we can do much more to direct users to install themes/plugins which are AMP-compatible: #2313 (comment)

Site Kit exposes this as the following setting:

image


Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

@amedina amedina added the P1 Medium priority label May 13, 2020
@kmyram kmyram added the WS:UX Work stream for UX/Front-end label May 15, 2020
@jwold
Copy link
Collaborator

jwold commented Aug 5, 2020

Should we add this as a checkmark in the onboarding wizard?

@westonruter
Copy link
Member Author

Yes we should.

@amedina
Copy link
Member

amedina commented Aug 5, 2020

Since we must provide details on what will be shared, etc., one possibility is to add a full step to the onboarding flow, similar to what is done in plugins like Yoast.
Screen Shot 2020-08-05 at 1 11 40 PM

We need to think this feature thoroughly.

@jwold
Copy link
Collaborator

jwold commented Feb 9, 2021

Took an initial stab at what this could look like.

Data

Figma link.

@westonruter
Copy link
Member Author

I like that. However, I think we'd want to lean toward “anonymized” rather than “anonymous”. Some of the validation data and site health data will not be anonymous. But any usage of it would be anonymized. Tricky balance.

@westonruter
Copy link
Member Author

We'll also need to design this for the settings screen.

@jwold
Copy link
Collaborator

jwold commented Feb 10, 2021

Good point. I'm thinking something like this:

Screen Shot 2021-02-10 at 2 49 59 PM

@westonruter westonruter added this to the v2.2 milestone Feb 12, 2021
@westonruter westonruter removed this from the v2.2 milestone Jun 18, 2021
@westonruter
Copy link
Member Author

We will restrict this user opt-in to sharing site details when opening a support request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked Groomed P1 Medium priority UX WS:UX Work stream for UX/Front-end
Projects
None yet
Development

No branches or pull requests

4 participants