Gutenberg: Make strings consistent, lower vs. Upper case

Created on 16 Apr 2018  路  14Comments  路  Source: WordPress/gutenberg

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

Needs Copy Review [Status] Needs More Info [Type] Copy

Most helpful comment

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

All 14 comments

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.

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

  1. Fix Toolbar to Top
    bildschirmfoto 2018-05-22 um 22 20 13

  2. 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

  1. Convert to Blocks
    bildschirmfoto 2018-05-22 um 22 46 03

  2. Convert to blocks

bildschirmfoto 2018-05-22 um 22 44 07

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

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.

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

Previously: #4325

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

@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?

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.

Copy guidelines were merged in #7588

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

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

Was this page helpful?
0 / 5 - 0 ratings