-
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
Woo Express Copy Updates: Plans page #74899
Comments
So regarding the subheading 'Discover what's available on Woo Express', Laura will take care of that on Monday. @that-mike-bal, Regarding the plan name 'Performance' and also the 'General features', that's already part of the layout, or are you referring to something else here? |
@markbiek and @nelsonec87, if we have cycles later today, this may be something worth picking up after we launch the Performance plan. Please feel free to add it to our board if we can get started on it today, otherwise we can work with the Ghidorah folks tomorrow to work out who can pick this up first. |
@Automattic/serenity is going to pick this update today. |
@that-mike-bal A couple of things I could use clarity on: Item 1Should the above copy be on just the plans page for sites already on Woo Express Performance or should it be changed on the Trial plans page as well? Item 2I'm also unsure what needs to change on the "General features" list. That copy appears to be the same as what you provided in that screenshot. The only difference is a slight change in the support copy for trial sites vs. upgraded sites (See #74789 for more details). |
Copy changes for mysite.wordpress.com/plans
Subtext under page title plans should read "Discover what's available on Woo Express"
The plan name should reflect "Performance"
The "General features" section should read as displayed in the screen shot/design
Note: @FlorianBru since this page will display all of the available Woo Express plan, I suggest we change the title subtext to "Discover what's available on Woo Express."
The text was updated successfully, but these errors were encountered: