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

Site Settings: separate reconnection and disconnection components in the JP Disconnect Flow. #17962

Conversation

AnnaMag
Copy link
Contributor

@AnnaMag AnnaMag commented Sep 8, 2017

Add Troubleshooting survey option to the Jetpack Disconnect UX.

Depends on: #17696

View:
/settings/disconnect-site/:site, where :site is a Jetpack or non-Atomic site.
For other sites the Flow redirects automatically to /settings/general:site.

To test:

Verify that the options are visible as shown below and, upon selection, redirect to an empty placeholder follow-up Card.

Visuals:
screen shot 2017-09-30 at 10 46 06

@matticbot matticbot added OSS Citizen [Size] XL Probably needs to be broken down into multiple smaller issues labels Sep 8, 2017
@AnnaMag AnnaMag self-assigned this Sep 8, 2017
@AnnaMag AnnaMag added [Feature] Site Settings All other general site settings. [Status] In Progress labels Sep 8, 2017
const textShareWhy =
translate( ' Would you mind sharing why you want to' + 'disconnect ' ) +
`${ siteSlug }` +
translate( ' from WordPress.com ' );
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! I've found a possible matching string that has already been translated 24 times:
translate( 'Updates from WordPress.com' ) ES Score: 9
See 2 additional suggestions in the PR translation status page

Help me improve these suggestions: react with 👎 if the suggestion doesn't make any sense, or with 👍 if it's a particularly good one (even if not implemented).

@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey-separate-reconnection branch from 5f50bb1 to 7df6641 Compare September 8, 2017 22:29
const textShareWhy =
translate( ' Would you mind sharing why you want to disconnect ' ) +
`${ siteSlug }` +
translate( ' from WordPress.com ' );
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! I've found a possible matching string that has already been translated 24 times:
translate( 'Updates from WordPress.com' ) ES Score: 9
See 2 additional suggestions in the PR translation status page

Help me improve these suggestions: react with 👎 if the suggestion doesn't make any sense, or with 👍 if it's a particularly good one (even if not implemented).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split translatable string is fixed.

@AnnaMag AnnaMag changed the title JP Disconnect UX: separate reconnection component from the main flow. Site Settings: separate reconnection and disconnection components in the JP Disconnect Flow. Sep 9, 2017
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey-separate-reconnection branch 2 times, most recently from 932e36a to a100c29 Compare September 9, 2017 09:35
<Card>
<h1>
{' '}
{ translate( 'Disconnection' ) }{' '}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! I've found a possible matching string that has already been translated 34 times:
translate( 'Disconnecting' ) ES Score: 11
See 2 additional suggestions in the PR translation status page

Help me improve these suggestions: react with 👎 if the suggestion doesn't make any sense, or with 👍 if it's a particularly good one (even if not implemented).

<Card>
<h3>
{' '}
{ translate( 'Reconnection' ) }{' '}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! I've found a possible matching string that has already been translated 22 times:
translate( 'Reconnecting…' ) ES Score: 13
See 2 additional suggestions in the PR translation status page

Help me improve these suggestions: react with 👎 if the suggestion doesn't make any sense, or with 👍 if it's a particularly good one (even if not implemented).

@AnnaMag AnnaMag requested a review from keoshi September 9, 2017 11:35
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey-separate-reconnection branch from a100c29 to 33ebcb3 Compare September 10, 2017 23:12
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey branch from 2d3b434 to 98c88d2 Compare September 10, 2017 23:15
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey-separate-reconnection branch from 33ebcb3 to 1fa5e6f Compare September 11, 2017 14:26
@keoshi
Copy link
Contributor

keoshi commented Sep 11, 2017

Here's an updated mock that includes the dropdown changes of #17696 but, more important, introduces reconnect and live chat options below the survey.

02-survey-step-with-options

cc @rickybanister and @folletto for review.

@folletto
Copy link
Contributor

Looks good to me :)

Just two small bits on the actions outside the box:

  1. They feel a bit unbalanced, as one is two lines and the other is just one line, also might be more evident due to the icon center-aligned but I'm not sure.
  2. The second one doesn't look tappable.

Maybe...

  • break "Chat with us" on a new line and color it?
  • underline both of the links

@rickybanister
Copy link

I used more of a clickable card for the 'chat with us' option here:

#18149

Not sure if that's the right way to go, but felt more 'clickable'

I like having these as alternative options though!

@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey branch 2 times, most recently from 53db3c5 to 29edd47 Compare September 29, 2017 12:26
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey-separate-reconnection branch 5 times, most recently from bcc19df to bcace66 Compare September 30, 2017 10:17
@AnnaMag AnnaMag removed the [Size] XL Probably needs to be broken down into multiple smaller issues label Sep 30, 2017
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey branch from e2ace66 to 5d59c4f Compare September 30, 2017 10:43
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey branch 2 times, most recently from dd86f83 to 8ab75bd Compare October 1, 2017 23:07
@AnnaMag AnnaMag force-pushed the update/site-settings-disconnect-site-survey-separate-reconnection branch from bcace66 to 3a7d664 Compare October 2, 2017 08:51
This adds an extra reason for the disconnection from WP, which is common
to all Plans: temporary disconnection to troubleshoot potential problems.
@rickybanister
Copy link

@keoshi as per my last comment, could we try separating your reconnect question to be a label, and then the link as a sort of borderless clickable card (for both the reconnect option and the contact support)?

So basically

Having problems with your site connection?
( ) Reconnect your site >
( ) Get help with your connection >

@keoshi
Copy link
Contributor

keoshi commented Oct 4, 2017

How do you feel about this?

02-survey-step-with-problem-options

@rickybanister
Copy link

I think that's nice.

The only feedback I'd have is that you kind of created a new pattern with the bold text in the card as a 'title' instead of using the sectionHeader pattern. What do you think?

@keoshi
Copy link
Contributor

keoshi commented Oct 4, 2017 via email

@rickybanister
Copy link

Makes sense, as long as we use the sectionHeader component when we build it we're good.

@ockham
Copy link
Contributor

ockham commented Oct 25, 2017

Superseded by #19158 and #18968.

@ockham ockham closed this Oct 25, 2017
@ockham ockham deleted the update/site-settings-disconnect-site-survey-separate-reconnection branch October 25, 2017 20:18
ockham added a commit that referenced this pull request Oct 27, 2017
Add a button to get help (either via HappyChat, or the contact form). Implement the mockup found at #17962 (comment). Note that I've opted to stick with that mockup instead of #17962 (comment), since it's more consistent with prior art, such as #18397.

This PR uses `jetpack-connect/happychat-button`, to which it adds an `onClick` prop in order to be able to pass the tracking event to it. It unifies some styling that was previously scattered across three different selectors, which ensures that the styling also works for this PR without having to add a fourth selector. (Bonus points for verifying that the styling still works for the other instances -- see testing instructions for #18397.)

It also fixes the `state/analytics` README which I consulted while writing this PR 🙂

Discussion about functionality (what each button is supposed to do) is at #17962 (comment).
rclations pushed a commit to rclations/wp-calypso that referenced this pull request Nov 15, 2017
…ttic#18968)

Add a button to get help (either via HappyChat, or the contact form). Implement the mockup found at Automattic#17962 (comment). Note that I've opted to stick with that mockup instead of Automattic#17962 (comment), since it's more consistent with prior art, such as Automattic#18397.

This PR uses `jetpack-connect/happychat-button`, to which it adds an `onClick` prop in order to be able to pass the tracking event to it. It unifies some styling that was previously scattered across three different selectors, which ensures that the styling also works for this PR without having to add a fourth selector. (Bonus points for verifying that the styling still works for the other instances -- see testing instructions for Automattic#18397.)

It also fixes the `state/analytics` README which I consulted while writing this PR 🙂

Discussion about functionality (what each button is supposed to do) is at Automattic#17962 (comment).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Site Settings All other general site settings. OSS Citizen
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants