-
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
Plugins update manager: Add translation #88300
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~90 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. |
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.
@JanaMW27 When you get a chance, could you review my copy suggestions?
title="Plugin updates manager" | ||
subtitle="Effortlessly schedule plugin auto-updates with built-in rollback logic." | ||
title={ translate( 'Plugin updates manager' ) } | ||
subtitle={ translate( 'Schedule automatic plugin updates' ) } |
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.
Set up automated schedules so plugins update when you want them to.
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.
This copy was reviewed and approved by the copywriting team. Why it needs to be changed?
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 think there's an opportunity to be more descriptive in some of these places
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 also think that there is a space to be more specific, but I would leave it for the next PRs since I'm going to deploy this one.
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.
@bogiii Could I ask you to hold off if we plan to make changes to translation strings? We should avoid sending strings to translation (and pay for those translations) when there's a good chance they'll get changed again
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.
Ouch. I've deployed it.
I wanted to avoid resolving future conflicts and deployed it.
@@ -68,7 +70,7 @@ export const PluginsUpdateManager = ( props: Props ) => { | |||
onClick={ onCreateNewSchedule } | |||
disabled={ ! canCreateSchedules } | |||
> | |||
Create a new schedule | |||
{ translate( 'Set up a new schedule' ) } |
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 simplify this to "Create new schedule"? Or "Add new schedule" to align it with "Add new post"?
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.
It used to be "Create a new schedule", but the copy was reviewed and changed to be "Set up a new schedule".
@JanaMW27, what do you think?
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.
Both copies sound good to me. Maybe "set up" is more aligned with the user action? I dunno, both work for me.
f692c06
to
d11b19c
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.
LGTM. Great work. 🚢
c3c562d
to
4d8f6f5
Compare
* Revert "Revert "Plugins update manager: Add translation (#88300)" (#88373)" This reverts commit f070f10. * Apply first batch of suggestions from code review Props @provenself * Update subtitle wording * Add trailing period. * Remove unnecessary info text. This is now covered in empty state. * Fix curly quote --------- Co-authored-by: Konstantin Obenland <[email protected]>
* Translate PluginsUpdateManager component * Translate ScheduleCreate component * Translate ScheduleEdit component * Update copy of PluginsUpdateManager * Translate ScheduleList component * Translate ScheduleListEmpty component * Translate ScheduleListTable component * Translate ScheduleListCards component * Translate ScheduleForm component * Translate ScheduleForm constants and helpers * Remove unused validateName function * Reuse the same translation * Update copy
* Revert "Revert "Plugins update manager: Add translation (#88300)" (#88373)" This reverts commit f070f10. * Apply first batch of suggestions from code review Props @provenself * Update subtitle wording * Add trailing period. * Remove unnecessary info text. This is now covered in empty state. * Fix curly quote --------- Co-authored-by: Konstantin Obenland <[email protected]>
Related to #87896
Proposed Changes
Testing Instructions
/plugins/scheduled-updates/{ATOMIC_SITE}
Pre-merge Checklist