Skip to content
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

Make strings consistent, lower vs. Upper case #6210

Closed
Presskopp opened this issue Apr 16, 2018 · 14 comments
Closed

Make strings consistent, lower vs. Upper case #6210

Presskopp opened this issue Apr 16, 2018 · 14 comments
Labels
Needs Copy Review Needs review of user-facing copy (language, phrasing) [Status] Needs More Info Follow-up required in order to be actionable. [Type] Copy Issues or PRs that need copy editing assistance

Comments

@Presskopp
Copy link
Contributor

I can't remember if I brought this up before somewhere. I made a list a long time ago and just found out it's still immanent:

lower vs Upper case:

block(s) vs. Block(s)

strings are there 2 times:
Convert to blocks vs. Convert to Blocks
Editor toolbar vs. Editor Toolbar
Featured image vs. Featured Image

audio vs. Audio
embed vs. Embed
image vs. Image

Not sure, could be false positives in here

@Soean Soean added the [Type] Copy Issues or PRs that need copy editing assistance label Apr 17, 2018
@karmatosed
Copy link
Member

karmatosed commented Apr 17, 2018

As casing depends on context, could you perhaps provide a little more insight into each of these? For example, where do you see them in the interface? Having a list would of ones to work through would be great.

@Soean Soean added the [Status] Needs More Info Follow-up required in order to be actionable. label Apr 18, 2018
@Presskopp
Copy link
Contributor Author

Presskopp commented Apr 18, 2018

I found these translating and not in backend. I'll see what I can do, but can't promise anything, sorry.

@Soean
Copy link
Member

Soean commented May 22, 2018

  1. Fix Toolbar to Top

bildschirmfoto 2018-05-22 um 22 20 13

  1. Pin to toolbar / Unpin from toolbar

bildschirmfoto 2018-05-22 um 22 23 22

  1. Editor Toolbar / Editor toolbar

bildschirmfoto 2018-05-22 um 22 26 08

  1. Block Toolbar

bildschirmfoto 2018-05-22 um 22 36 19

@Soean
Copy link
Member

Soean commented May 22, 2018

  1. Convert to Blocks

bildschirmfoto 2018-05-22 um 22 46 03

  1. Convert to blocks

bildschirmfoto 2018-05-22 um 22 44 07

@Soean
Copy link
Member

Soean commented May 22, 2018

Featured image / Featured Image
bildschirmfoto 2018-05-22 um 22 54 51

@Soean Soean removed the [Status] Needs More Info Follow-up required in order to be actionable. label May 22, 2018
@Soean Soean added the Needs Copy Review Needs review of user-facing copy (language, phrasing) label May 23, 2018
@kristastevens
Copy link

kristastevens commented May 23, 2018

Thanks so much for the ping!

Per the brand guide, we default to sentence case for text, including headings and buttons. I recently had a conversation with @mattmiklic to mine his historical memory as someone deeply involved in design from the early days of WP.com, and he confirms this. Anything that isn't, such as the instances noted above, "Fix Toolbar to Top," "Convert to Blocks" plus all the menu items and buttons, "Show Block Settings," etc., should be in sentence case, e.g., "Fix toolbar to top." "Edit as HTML" is correct as it is.

@chrisvanpatten
Copy link
Member

It would be great to have that documentation available on .org, since this is a .org project and not a .com project :)

@aduth
Copy link
Member

aduth commented Jun 11, 2018

Previously: #4325

@karmatosed
Copy link
Member

@chrisvanpatten there is a style guide for writing due to be worked on for WCEU so totally something we can then have included.

@aduth
Copy link
Member

aduth commented Jun 25, 2018

@chrisvanpatten there is a style guide for writing due to be worked on for WCEU so totally something we can then have included.

@karmatosed Did this happen?

@karmatosed
Copy link
Member

The style guide for writing didn't happen. Let's see about getting that done sooner over later. I'll work on that thanks for reminder.

@Soean
Copy link
Member

Soean commented Jul 9, 2018

Copy guidelines were merged in #7588

@aduth
Copy link
Member

aduth commented Jul 9, 2018

Can this issue be closed then? What actionable tasks remain?

@aduth aduth added the [Status] Needs More Info Follow-up required in order to be actionable. label Jul 9, 2018
@mtias
Copy link
Member

mtias commented Jul 19, 2018

Closing. If there are remaining things to address let's open specific issues.

@mtias mtias closed this as completed Jul 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Copy Review Needs review of user-facing copy (language, phrasing) [Status] Needs More Info Follow-up required in order to be actionable. [Type] Copy Issues or PRs that need copy editing assistance
Projects
None yet
Development

No branches or pull requests

7 participants