add studio cli to whats new modal #1213
Conversation
| image: studioIllustration, | ||
| title: __( 'Introducing Studio by WordPress.com CLI' ), | ||
| description: __( | ||
| 'Run commands and manage preview sites from your terminal! Use the `studio` command and create, list, update, and delete preview sites with our new CLI tool.' |
There was a problem hiding this comment.
What do you think about making this copy slightly shorter so that it fully fits on the modal without being cut off? Something like Run studio command in your terminal to create, list, update, and delete preview sites with our new CLI tool. perhaps? or something similar?
There was a problem hiding this comment.
@katinthehatsite @ivan-ottinger, I'm a little concerned about forcefully limiting the line count. From a design perspective, it makes sense as a rule of thumb, but translations can change the length of the string, and it looks odd when the text gets cut off. How difficult would it be to adapt the height dynamically?
| @@ -58,6 +58,14 @@ export default function WhatsNewModal( { showModal, onClose }: WhatsNewModalProp | |||
| 'Discover the latest updates in Studio! Explore exciting new features designed to enhance your experience.' | |||
| ), | |||
| }, | |||
| { | |||
| image: studioIllustration, | |||
| title: __( 'Introducing Studio by WordPress.com CLI' ), | |||
There was a problem hiding this comment.
Should we flip the wording a bit? Or maybe we could skip WordPress.com here?
| title: __( 'Introducing Studio by WordPress.com CLI' ), | |
| title: __( 'Introducing Studio CLI by WordPress.com' ), |
There was a problem hiding this comment.
I think it should be consistent with the CLI.
Should we adjust the wording in both places?
There was a problem hiding this comment.
In this context, I agree with Wojtek that we can skip "by WordPress.com"
| description: __( | ||
| 'Run studio command in your terminal to create, list, update, and delete preview sites with our new CLI tool.' | ||
| ), | ||
| learnMoreUrl: 'https://wordpress.com/blog/2025/04/01/studio-cli/', |
There was a problem hiding this comment.
There won't be a blog post for this release (see Marketing in pesfPa-1pM-p2)
There was a problem hiding this comment.
We will need a Learn more link, though, so let's target a support doc instead.
| @@ -58,6 +58,14 @@ export default function WhatsNewModal( { showModal, onClose }: WhatsNewModalProp | |||
| 'Discover the latest updates in Studio! Explore exciting new features designed to enhance your experience.' | |||
| ), | |||
| }, | |||
| { | |||
| image: studioIllustration, | |||
| title: __( 'Introducing Studio by WordPress.com CLI' ), | |||
There was a problem hiding this comment.
In this context, I agree with Wojtek that we can skip "by WordPress.com"
| description: __( | ||
| 'Run studio command in your terminal to create, list, update, and delete preview sites with our new CLI tool.' | ||
| ), |
There was a problem hiding this comment.
| description: __( | |
| 'Run studio command in your terminal to create, list, update, and delete preview sites with our new CLI tool.' | |
| ), | |
| description: sprintf( | |
| /* translators: %s is the name of the Studio CLI command ("studio") */ | |
| __( | |
| 'Run the %s command in your terminal to create, list, update, and delete preview sites with our new CLI tool.' | |
| ), | |
| '<code>studio</code>' | |
| ), |
Adding a <code> wrapper around "studio" is just a suggestion, but regarding the phrasing, I would definitely add a "the" before "studio command".
There was a problem hiding this comment.
We could also go back to your original approach of using backticks around the studio command name, @bcotrim. It looks better with a <code> wrapper, though.
Related issues
Proposed Changes
Testing Instructions
npm startPre-merge Checklist