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

Capitalisation of Titles on home page #62

Open
jenniferlin15 opened this issue Oct 7, 2014 · 5 comments
Open

Capitalisation of Titles on home page #62

jenniferlin15 opened this issue Oct 7, 2014 · 5 comments
Labels

Comments

@jenniferlin15
Copy link

The capitalisation of titles is really inconsistent throughout the entire site. We have examples such as:

  • Find Specific Articles
  • Publication date
  • Explore sample reports
  • Search all Articles
  • Upload File
  • Funder name or funding number
  • Top Tweets
  • Most bookmarked
  • Edit List

Wow.. it's all over the place. We need to standardize capitalisation across the board. Most of the titles have all words capitalised and for simplicity sake, let's just go with that.

@jure
Copy link
Contributor

jure commented Oct 7, 2014

So "Funder Name Or Funding Number"? or "Funder Name or Funding Number"?

@jenniferlin15
Copy link
Author

Funder Name or Funding Number

[let's not capitalise prepositions: and, or, the, a, etc. that said, "all" is not a preposition - i looked this up.]

@jure
Copy link
Contributor

jure commented Oct 14, 2014

TL;DR: The consensus is that title-style capitalization is used for titles, and sentence-style for all other UI elements.

I've never thought of this aspect, so I'm trying to find some best practices when it comes to UI text capitalization.

One really good example is the comprehensive Microsoft style guide: http://msdn.microsoft.com/en-us/library/dn742478.aspx

This is what it says about capitalization of UI text:

Capitalization

Use title-style capitalization for titles, sentence-style capitalization for all other UI elements. Doing so is more appropriate for the Windows tone.
Exception: For legacy applications, you may use title-style capitalization for command buttons, menus, and column headings if necessary to avoid mixing capitalization styles.
image
image

Some more references here: http://ux.stackexchange.com/questions/28172/what-are-some-reference-works-for-capitalization-in-ui-text

As far as capitalization itself is concerned, these rules cover it:

Title-Style Capitalization

Capitalize every word except the following:

  • Articles ("a," "an," and "the")
  • Coordinating conjunctions ("and," "but," "for," "nor," and "or")
  • Prepositions of four or fewer letters ("with", "of," and "for")
  • The word "to" in an infinitive phrase (for example, "How to Set Up Your Computer")
  • Case-sensitive programming terms and object names (for example, "A fancy cluster")
  • Always capitalize the first and last words, regardless of their parts of speech (for example, "The Text to Look For").

Sentence-Style Capitalization

  • Always capitalize the first word of a new sentence. Proper nouns and capitalized object names maintain their usual capitalization. Rewrite sentences that start with a case-sensitive lowercase word, such as an object name.
  • Do not capitalize the word following a colon unless the word is a proper noun, or the text following the colon or dash is a complete sentence.

@jure
Copy link
Contributor

jure commented Oct 14, 2014

Google seems to be even more on the lower-case side of things: https://www.google.com/advanced_search

image

Not a big fan of this, I think that Microsoft's approach looks cleaner.

@jenniferlin15
Copy link
Author

I'm fine going with either, just want consistency. The current rendering is mostly all caps across titles and UX elements. I say mostly since it's not equally applied, hence the ticket. If you'd like to move to Microsoft approach, that works for me but we'll have to do a global audit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants