-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
[Design Proposal]Capitalization guidelines for consistency #12343
Comments
Thanks for the detailed proposal and the reasoning! I believe Superset will greatly benefit from more guidelines like this. Maybe we could even develop our own design system! Do you think it makes sense to add following exception to the proposal as well?
|
+1. no more forcing upper case in the product.. |
@ktmud yes - totally agree with user inputs appearing exactly as they were inputted |
Guidelines added to |
Apply capitalization guidelines defined in #12343 Use sentence casing for most places.
Update capitalization guideline to exempt user inputs from cap transformation. Based on the discussion here: #12343 (comment) cc @mihir174
Update capitalization guideline to exempt user inputs from cap transformation. Based on the discussion here: #12343 (comment) cc @mihir174
Moved to Design Guidelines page on the Wiki, so I'll call this issue Closed. |
Update capitalization guideline to exempt user inputs from cap transformation. Based on the discussion here: apache/superset#12343 (comment) cc @mihir174
Update capitalization guideline to exempt user inputs from cap transformation. Based on the discussion here: apache#12343 (comment) cc @mihir174
Update capitalization guideline to exempt user inputs from cap transformation. Based on the discussion here: apache#12343 (comment) cc @mihir174
This design proposal aims to make text consistently capitalized across the product, to address issues like #12023
Here are the guidelines @Steejay and I developed, based on design systems from Google, IBM and Atlassian.
Sentence case
Use sentence-case capitalization for everything in the UI (except these **).
Sentence case is predominantly lowercase. Capitalize only the initial character of the first word, and other words that require capitalization, like:
Sentence case vs. Title case:
Title case: "A Dog Takes a Walk in Paris"
Sentence case: "A dog takes a walk in Paris"
Why sentence case?
How to refer to UI elements
When writing about a UI element, use the same capitalization as used in the UI.
For example, if an input field is labeled “Name” then you refer to this as the “Name input field”. Similarly, if a button has the label “Save” in it, then it is correct to refer to the “Save button”.
Where a product page is titled “Settings”, you refer to this in writing as follows:
“Edit your personal information on the Settings page”.
Often a product page will have the same title as the objects it contains. In this case, refer to the page as it appears in the UI, and the objects as common nouns:
**Exceptions to sentence case:
The text was updated successfully, but these errors were encountered: