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

Checkout: Thank You: Update support section in footer with new copy #3755

Merged
merged 10 commits into from
Mar 8, 2016

Conversation

stephanethomas
Copy link
Contributor

This pull request addresses part of #2484 by updating the footer of the Thank You page with a new copy for the support section:

screenshot

Testing instructions

  1. Run git checkout update/thank-you-footer and start your server
  2. Purchase any type of product
  3. Check that the footer of the Thank You page displays as expected for large viewports
  4. Check that the footer of the Thank You page displays as expected for small viewports
  5. Purchase a Jetpack plan
  6. Check that clicking on buttons now redirects you on the Jetpack site
  7. Check that the support section displays correctly in the app components doc

Additional notes

I wasn't able to align vertically the gravatar, especially since there is a difference of placement for the buttons depending on the size of the viewport.

Reviews

  • Code
  • Product

@stephanethomas stephanethomas added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. [Feature] Checkout The checkout screen and process for purchases made on WordPress.com. labels Mar 3, 2016
@stephanethomas stephanethomas self-assigned this Mar 3, 2016
@stephanethomas stephanethomas added this to the Amber: Sprint milestone Mar 3, 2016
@fabianapsimoes
Copy link
Contributor

The mockup has a lot more vertical padding.

Mockup:
screenshot-cloud githubusercontent com 2016-03-03 14-57-24

Implemented:
screenshot-calypso localhost 3000 2016-03-03 15-01-27

Should we maybe have a smaller gravatar for mobile? cc @mikeshelton1503

Mockup:
screenshot-github com 2016-03-03 15-00-03

Implemented:
screen shot 2016-03-03 at 14 59 13

@fabianapsimoes fabianapsimoes added [Status] Needs Author Reply and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Mar 3, 2016
@stephanethomas stephanethomas force-pushed the update/thank-you-footer branch 2 times, most recently from 9cede83 to 57df7eb Compare March 3, 2016 15:26
@stephanethomas
Copy link
Contributor Author

I added more padding and also made sure the gravatar's size is consistent with the size of gridicons.

@stephanethomas stephanethomas added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. and removed [Status] Needs Author Reply labels Mar 3, 2016
@stephanethomas stephanethomas force-pushed the update/thank-you-footer branch from 57df7eb to 8f2a871 Compare March 3, 2016 15:28
}

.checkout-thank-you__footer-content {
margin: 16px auto;
margin-left: auto;
margin-right: auto;
Copy link
Member

Choose a reason for hiding this comment

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

Why not write this margin: 0 auto; and save a line?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because in that case you're also resetting top and bottom margins. Moreover when it's explicit like this you don't have to think about it (and my old brain likes that), and it will be compiled as a single property/line by SASS anyway.

Copy link
Contributor

Choose a reason for hiding this comment

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

it will be compiled as a single property/line by SASS anyway.

That's cool. I didn't know this.

}
);
return (
<a className="button" href={ url } target={ target }>
Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think about using <Button /> for this? I assume you intended to use it, because it is imported at the top, but never used.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, I started with <Button /> but switched to a simple anchor because I assumed that this component couldn't allow me to manage the target attribute. Looks like I was plain wrong.

@drewblaisdell
Copy link
Contributor

I had a couple minor notes which I addressed in a commit that I pushed onto this branch. Feel free to squash it in with your commits, or delete it if I missed something. Otherwise, the code LGTM. 👍

@@ -51,13 +69,27 @@ const CheckoutThankYouFooter = React.createClass( {
return (
<Card className="checkout-thank-you__footer">
<div className="checkout-thank-you__footer-content">
{ this.renderGravatar() }
Copy link
Member

Choose a reason for hiding this comment

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

This has become a nice component. Can we turn it into an app-component we can reuse outside of thank you pages? Thinking something like SupportFromHappiness that we can render in devdocs/app-components, on the /plans page, etc.

(It would also help clean up the thank-you stylesheet.)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure thing.

Copy link
Member

Choose a reason for hiding this comment

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

Thanks :)

@mtias mtias added [Status] Needs Author Reply and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Mar 3, 2016
@stephanethomas stephanethomas force-pushed the update/thank-you-footer branch 2 times, most recently from 4a792e0 to 4025f7b Compare March 4, 2016 12:29
@stephanethomas stephanethomas added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. and removed [Status] Needs Author Reply labels Mar 4, 2016
@stephanethomas
Copy link
Contributor Author

Thank you everyone for your feedback! I've made the suggested changes and this pull request is now ready for a last look.

@fabianapsimoes
Copy link
Contributor

I think we need placeholders for this section:

screenshot-calypso localhost 3000 2016-03-04 14-05-27

Especially because it shows the WordPress.com footer first even if you've just purchased a Jetpack product.

@fabianapsimoes
Copy link
Contributor

I still think we need placeholders, since the URL changes depending on the product we're loading. Having the HE not change is nice, but the main issue is around the URL. Especially in cases such as the one Drew described, in which the page can take a while to fully load, there is a risk the user will click that button and be taken to the wrong support site.

@fabianapsimoes fabianapsimoes added [Status] Needs Author Reply and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Mar 7, 2016
@mikeshelton1503
Copy link
Contributor

I agree with @fabianapsimoes, let's go with placeholders. It eliminates the risk of a user going to the wrong place.

@stephanethomas stephanethomas force-pushed the update/thank-you-footer branch 2 times, most recently from b860f4b to 6276965 Compare March 7, 2016 20:20
@stephanethomas
Copy link
Contributor Author

I've rebased, updated existing placeholders to better match the expected layout of the Thank You page and finally added placeholders for the support section. Let me know what you think of it.

@stephanethomas stephanethomas added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. and removed [Status] Needs Author Reply labels Mar 7, 2016
@drewblaisdell
Copy link
Contributor

👍

@stephanethomas stephanethomas force-pushed the update/thank-you-footer branch from 6276965 to 15b6e36 Compare March 8, 2016 09:22
@scruffian
Copy link
Member

Product 👍

@scruffian scruffian added [Status] Ready to Merge and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Mar 8, 2016
scruffian added a commit that referenced this pull request Mar 8, 2016
Checkout: Thank You: Update support section in footer with new copy
@scruffian scruffian merged commit 27ca11e into master Mar 8, 2016
@scruffian scruffian deleted the update/thank-you-footer branch March 8, 2016 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Checkout The checkout screen and process for purchases made on WordPress.com. [Type] Task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants