Wordpress-ios: Make NoResultsViews consistent in terms of including trailing period in titles

Created on 2 Jul 2019  路  7Comments  路  Source: wordpress-mobile/WordPress-iOS

As noted in #11997, and expanded by @yaelirub in this comment: https://github.com/wordpress-mobile/WordPress-iOS/issues/11997#issuecomment-506560583 we're incredibly inconsistent when it comes to including trailing periods in No Results Views messages.

We should decide on one style and update it across all the screens.

Samples

| Location | Screenshot |
|--------|-------|
| Notifications | |
| Pages | |
| Posts | |
| Site | |
| Reader | |
| Quick Start | |
| Comments | |
| Media Library | |
| Menus | |
| Activities | |
| Domain Credit | |
| People | |

1 Offline Support [Pri] Low [Type] Enhancement good first issue

Most helpful comment

I'd consider that a headline in this context, yes.

For other screens with long "headlines," specifically the Add a Site and Domain Credit screens, I'd want to see a shorter headline with no punctuation; right now there are full sentences acting as headlines.

REL the button capitalization, it's all the buttons that say Create a Page, Create a Post, Create a Tag -- page, post, and tag aren't proper nouns and wouldn't normally be capitalized in regular text, so they wouldn't be capitalized on buttons, either.

All 7 comments

We need to look at some guidelines.

@yaelirub I assumed the decision was already made by https://github.com/wordpress-mobile/WordPress-iOS/issues/11997#issuecomment-506047116:

No punctuation on buttons, naturally, though I feel like our sentences here need terminal punctuation. Also, button text is sentence case per the brand guide.

I guess I may have misunderstood. How do we proceed with this then?

I gathered a big sample of the NoResultsViews and updated the description with screenshots. 鈽濓笍 I stopped here because it looked counterproductive to continue. 馃槃

Observation

Most of them do not have terminal punctuations. Some have periods and exclamation marks. Should we change all of them to have terminal punctuations?

I'll request input from Editorial. I'm sure they can answer this question better than me. 馃槄

Okay! So:

  • Buttons are sentence case, so there are some that need to have capital letters removed.

  • For things like "No comments yet," it depends on whether these are regular copy or headlines. If they're copy, they should all have terminal punctuation. If they're headlines, none of them should have terminal punctuation except for a few with exclamation points. I'm assuming these function like headlines, so I'd say no terminal punctuation. For the few that are longer full sentences, like domain credits, I'd re-do the screen to make them shorter and more in line with the others.

  • Everything between the headline and the button is regular text and gets normal punctuation, including terminal punctuation.

Thank you for the response, @michelleweber.

In the case of search results like this:

Is that still considered as a headline?

Buttons are sentence case, so there are some that need to have capital letters removed.

Would you be able to point out some of them so I can understand more? 馃檪 Thank you!

Moving this to _Ready for Dev_. But note that it's a low priority issue. I think we can request for copy review for each piece we work on.

I'd consider that a headline in this context, yes.

For other screens with long "headlines," specifically the Add a Site and Domain Credit screens, I'd want to see a shorter headline with no punctuation; right now there are full sentences acting as headlines.

REL the button capitalization, it's all the buttons that say Create a Page, Create a Post, Create a Tag -- page, post, and tag aren't proper nouns and wouldn't normally be capitalized in regular text, so they wouldn't be capitalized on buttons, either.

Was this page helpful?
0 / 5 - 0 ratings