-
Notifications
You must be signed in to change notification settings - Fork 800
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
Plans: Add Single Product Jetpack Backup #14018
Plans: Add Single Product Jetpack Backup #14018
Conversation
This is an automated check which relies on |
Note to reviewers: differences between this PR and #13766:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @robertf4, nice work! This appears to work well in my testing.
I really appreciate all the great progress here, but I still think this PR could be split to some more PRs - especially all the presentational components that this PR is introducing.
I've also left some suggestions, questions and feedback, let me know what you think.
); | ||
} | ||
|
||
export function PlanPriceDisplay( props ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we implement all of those components in their own PRs? I'm concerned that when they're in those big PRs they can be overlooked. I'm happy to help with reviewing all those PRs and whetever else you might need.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
onChange={ onChange } | ||
/> | ||
</div> | ||
<div className="plan-radio-button__plan-name">{ planName }</div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
None of these are currently usable enough - they should all be labels, so when I click on them, we select the corresponding radio buttons.
<div className="plan-radio-button__plan-name">{ planName }</div> | ||
<div className="plan-radio-button__plan-price"> | ||
{ planPrice && | ||
__( '%(currencySymbol)s%(planPrice)s /year', { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of those components aren't prepared for monthly support. Others seem to be prepared for that. I find this pretty confusing - are we planning to have monthly product support? If not, should we omit any monthly
mention in this PR? If yes, should we implement it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only time monthly is currently used is for calculating the larger price as monthly * 12
. It is necessary to display the larger price correctly, but I am not using monthly
for anything else.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks good to me. I have a few notes though:
Different typefaces and composition between adjacent elements
Top headings are using system fonts, the bottom is using Roboto.
Not enough room for elements to breathe
In particular, there's no room between the backups box and the monthly/yearly toggle.
Monthly/Yearly toggle doesn't affect Jetpack Backup pricing
Different currency displayed in product/plans
Different price formatting: /year
vs per year
Page looks too pyramid-like, with no balance at the top
Plans are not displayed on mobile but single products are, making the headline a bit confusing
cc @eeeeevon13
ea23c3f
to
5319df0
Compare
906af0f
to
b3543e1
Compare
b3543e1
to
1d13019
Compare
1d13019
to
09c8d67
Compare
09c8d67
to
01cc0ab
Compare
Co-Authored-By: Marin Atanasov <8436925+tyxla@users.noreply.github.com>
…n__single-product
195f8df
to
6715027
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. Currency management may need to be revisited as discussed in #14060, but that can be done in a future PR 👍
Feel free to merge that one!
Further issues to be addressed in followup PRs
Changes proposed in this Pull Request:
This PR adds a card to the Plans page to sell Jetpack Backup.
Current development:
Figma design:
Is this a new feature or does it add/remove features to an existing part of Jetpack?
See the P2 here for the design of this PR: p1HpG7-7MK-p2 (specifically the part titled "WP Admin Desktop")
See the P2 here for the overall MT: p1HpG7-7ET-p2
Testing instructions:
Proposed changelog entry for your changes: