-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Remove copy for managing a block's style variations #48367
Remove copy for managing a block's style variations #48367
Conversation
The copy in question was: "Manage style variations, saved block appearence presets." There's a typo (appearence should be appearance), and grammar — but I think we can do better all around. It's not clear where "block appearance presets" came from, but it seems like a fancier way to say "style variations". Together we came to the best copy for this issue, considering accessibility. I also made the copy translatable. Props richtabor, ndiego, ntsekouras. Fixes WordPress#48050.
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @tomdevisser! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
packages/edit-site/src/components/global-styles/screen-variations.js
Outdated
Show resolved
Hide resolved
packages/edit-site/src/components/global-styles/screen-variations.js
Outdated
Show resolved
Hide resolved
packages/edit-site/src/components/global-styles/screen-variations.js
Outdated
Show resolved
Hide resolved
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.
Thank you @tomdevisser ! Code wise this is good to go.
Let's get a confirmation for the updated copy and land. --cc @ndiego @richtabor @jameskoster
Possibly a radical idea, but do we need this copy at all? It seems a bit repetitive and unhelpful. |
That was my first comment on the issue #48050 (comment) , but wasn't agreed upon. So this seems like a good compromise, at least for now. 🙂 |
I'll defer to @richtabor since he's probably thought about this in more detail. |
Yea, it's not particularly helpful. I'm fine with adapting this PR remove the help text. |
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.
Change of plans; let's just remove this text.
…com/tomdevisser/gutenberg into update/copy-manage-style-variations
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.
Agreed this is needless copy, better to remove. 👍
I just cherry-picked this PR to the wp/6.2 branch to get it included in the next release: c735ffb |
Co-authored-by: Nik Tsekouras <[email protected]>
What?
Resolves #48050.
I improved the copy and made it translatable.
Why?
The copy in question was: "Manage style variations, saved block appearence presets."
There's a typo (appearence should be appearance), and grammar — but I think we can do better all around. It's not clear where "block appearance presets" came from, but it seems like a fancier way to say "style variations".
Together we came to the best copy for this issue, considering accessibility.
Testing Instructions
Screenshots or screencast