-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Update nav redesign overview plan card #90844
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~157 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~4961 bytes removed 📉 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~863 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
@lucasmendes-design just clarifying, are you referring to this blue? Just clarifying that the "Need more space?" link can remain blue. |
Yes, these ones you pointed out. Thanks, Dave. "Need more space" can remain blue. |
Notes: Fixed the blue color since it only happens (and currently in production) when it has been clicked and the link gets treated as a visited link. |
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.
On P2 sites (such as untangling
), it is showing as Free, even though the site's plan is P2+
.
I can't find a way to check if a site's plan is P2 Free or P2+, I'll hard code it as P2 plan as we're not letting people create new P2s. |
Also, I noticed the sites with a P2 plan for their I'll create an issue to see if we want to address the P2 situation as of now. Since for P2 sites, we should not show the Dev Tools tab either. |
On second thought, let's not handle the P2 case in this PR as there are many states for that as mentioned in the newly created issue: https://github.com/Automattic/dotcom-forge/issues/7278 cc: @fushar |
This reverts commit d94579c.
Sure, makes more sense this way! |
) } | ||
plain | ||
href={ | ||
isFreePlan ? `/add-ons/${ site?.slug }` : `/purchases/subscriptions/${ site?.slug }` |
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.
On sites with a paid plan, I think this should link to /purchases/subscriptions/:site/:planSubscriptionId
. That's what the "Manage plan" button does in wordpress.com/plans/:site:
? this.props.getManagePurchaseUrlFor( selectedSiteSlug, purchase.id ) |
Similarly, the button should be disabled for users who didn't make the purchase:
disabled={ ! userIsPurchaseOwner } |
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.
Thanks for the feedback, I've added the check for isOwner
.
It will directly hide the Manage button if ! isOwner
.
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.
@fushar Rendered Staging site and left the rest blank for now, @lucasmendes-design feel free to give feedback on this. We can implement it in a followup PR. |
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.
Works great!
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.
Tested the mentioned cases and it all worked great.
I think this is good to merge and we can fix any further issues (if any) in follow-up PRs 👍
Fixes https://github.com/Automattic/dotcom-forge/issues/7205
Proposed Changes
Free plan
Expired plan
Where each link/button goes
Other changes
Jetpack site ("Upgrade your plan" CTA will list Jetpack upgrades)
Legacy Creator/Business plan (no storage upsell)
Creator plan
Free plan
Expired legacy Creator/Business plan
Why are these changes being made?
Testing Instructions
Pre-merge Checklist