-
Notifications
You must be signed in to change notification settings - Fork 14
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
Redesign: agree capital letter conventions #234
Comments
Prefer To Capitalise Each Word In Headings ... |
@markwilliamfirth - are you happy with this convention? This is what I have executed so far for both buttons and headings. If you're happy then please test and close the issue 😄 |
@Cleop I would say we should use the following convention for titles/buttons: Always capitalise:
Do not capitalise:
Examples: |
Thanks @markwilliamfirth - think there was a typo on:
What was that bullet meant to read as? |
@Cleop I've updated 👍 |
food for thought @markwilliamfirth @nelsonic https://medium.com/@jsaito/making-a-case-for-letter-case-19d09f653c98 |
@harrygfox thanks for the link! Yes - this could change in future. Ultimately this is a branding decision and may well change! dwyl is written in lowercase, as lowercase often appears friendlier, but this is still under review dwyl/hq#249 it might make sense to move to sentence case in future if it's decided that we'll maintain the lowercase branding of our company name. For now I think this convention is a good start, as the key issue here is agreeing on consistency and conventions. This should be reviewed again when we assess our overall brand guidelines 👍 |
Closing as this has been agreed |
For the site redesign we need to agree a convention for capital letters in titles / buttons.
As a starting point I would say that as a minimum the first letter of the first word of a button should be capitalised ie.
After this should all words be capitalised or just the first?
This example should either have all caps or just the first:
The same goes for titles...
The text was updated successfully, but these errors were encountered: