Consider using sentence case instead of title case in UI elements

[rmol]

Description

It was pointed out (thanks @ekcnl) during translation for 1.8.0 that the button label Yes, Delete Selected Source Accounts looks odd.

We use a mix of ALL CAPS and Title Case for button labels. Title case looks all right for Shorter Labels, but Can Start Looking Eccentric When Longer.

The Material Design guidelines, to which we've referred in some recent design discussions, suggest either all caps or sentence case. We may not want to pick one or the other exclusively: we sometimes use mixed case for safe options like Cancel and all caps for irrevocable actions like DELETE. Or perhaps we should indicate danger with other cues, as long labels would also look odd and heavy in all caps. But in any event, sentence case generally works better than title case, and I think we should consider switching.

@ninavizz @zenmonkeykstop

[AO-LocLab]

It is also the case for " Yes, Delete Source Account".

[eloquence]

I'm not in favor of making this change for 1.8.0. All buttons in the source list of the Journalist Interface ("Select All", "Select None", "Files and Messages" in the deletion flow, etc.) currently use title case. We should not selectively change it here, but rather agree on style guidelines, and then consistently apply them. We should reserve that discussion for 1.9.0 or later, IMO.

[ninavizz]

We use a mix of ALL CAPS and Title Case for button labels. Title case looks all right for Shorter Labels, but Can Start Looking Eccentric When Longer.

You make me giggle in the best of ways sometimes, John. :)

I totally agree with everyone on this thread. It's emerged over quite a period, that an absence of clear Style Guidelines has contributed to ongoing friction that would be really nice to alleviate by taking the time to commit to making some.

Likewise, all the web UIs are horribly inconsistent; which I am as guilty of, as anyone, for wanting to implement best practices on spots where code is being modified—while leaving it well enough alone, elsewhere. I like the idea of doing a styleguide across a few sprints, then implementing its rules, in another sprint.