-
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
Add upsell to Advanced Tools tab #96609
base: trunk
Are you sure you want to change the base?
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
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 |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~87 bytes removed 📉 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~8167 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. 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. |
client/sites/tools/controller.tsx
Outdated
@@ -50,6 +51,11 @@ export function ToolsSidebar() { | |||
); | |||
} | |||
|
|||
export function advancedTools( context: PageJSContext, next: () => void ) { | |||
context.primary = <HostingFeatures />; |
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 also move/rename client/hosting/hosting-features/components
=> client/sites/components/hosting-features
? This way, when we clean up later, we don't need to touch the old location anymore.
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.
fixed in 2e41f39
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.
Ah, can we drop /tools/
from the patch, i.e. move it up one level, under client/sites/
? The subtab upsells might need to extract some shared utils from it. Hosting features are across tabs/subtabs, not just tools
.
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 subtab upsells might need to extract some shared utils from it.
See: #96660
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.
Moved here 5d023b7
@@ -97,7 +98,7 @@ const DotcomPreviewPane = ( { | |||
<HostingFeaturesIcon /> | |||
</span> | |||
), | |||
enabled: isSimpleSite || isPlanExpired, | |||
enabled: areHostingFeaturesSupported( site ), |
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.
I believe this should be
enabled: areHostingFeaturesSupported( site ), | |
enabled: ( isSimpleSite || isPlanExpired ) && ! config.isEnabled( 'untangling/hosting-menu' ), |
because we want to still show this when the feature flag is not enabled.
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.
fixed in 6c57e7f
enabled: | ||
areHostingFeaturesSupported( site ) && config.isEnabled( 'untangling/hosting-menu' ), | ||
! areHostingFeaturesSupported( site ) && config.isEnabled( 'untangling/hosting-menu' ), |
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.
Oh, I think there is a small misunderstanding here. We still want to show the original Advanced Tools
tab when the hosting features are supported, so we should add the tab instead of modifying this.
So there will be two tabs configured:
Advanced Tools
=> original, shown whereareHostingFeaturesSupported( site )
Advanced Tools
=> the new one, containing upsell, shown where! areHostingFeaturesSupported( site )
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 clarification. Introduced new tab here 6c57e7f
4ae4e46
to
6c57e7f
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.
Nicely done, thanks 👍
Found a small issue, we can follow-up later: https://github.com/Automattic/dotcom-forge/issues/9938 |
Fixes: https://github.com/Automattic/dotcom-forge/issues/9866
Proposed Changes
/sites/tools/:site
Why are these changes being made?
Testing Instructions
Pre-merge Checklist