Styling: decide on title case or sentence case and use everywhere

[danicahelb]

We are sometimes using title case and sometimes using sentence case. We need to be consistent with what case is being applied.

For variable labels (in variable trees, visualizations, & subset modal headers) we should ALWAYS use the exact format indicated in the .owl file. This seems to be OK currently.

For buttons, Mike had suggested using Title Case

Case discrepancies I am currently aware of (there are likely others...)

1. Entity names in the diagram are in sentence case, but are in title case in the subsetting results buttons

   

2. Sentence case in "Show all filters" vs title case in "Share Analysis"

   

3. Title case in "Unnamed Analysis" vs sentence case in "Unnamed Visualization"

   

4. Visualization picker names are sometimes in title case and sometimes in sentence case

   

[steve-fischer-200]

while i definitely agree with this... a quick survey of the vaunted Amazon.com reveals that they have this same inconsistency all over.

[asizemore]

See discussion in #1257

Long story short, i think that as we start to have more biological terms populate headings and other elements it will be easier to use sentence case since it should change the original text less. Often biology terms have weird capitalization rules (rRNA, gene names, protein names, etc), so if we try to capitalize the first of each word we'll end up with a long list of dont-capitalize-me and ignore-that-im-in-all-caps words if we go with title case

[dmfalke]

I think part of the problem we currently have is that we are using CSS text transforms in several places. I don't think we should ever use CSS text transforms. Perhaps that should be the scope of this issue?

[asizemore]

That works for me!

[bobular]

All-caps appeared in the SAM...

[danicahelb]

@bobular I think the all-caps issue you reported belongs in a new ticket. I made this one: https://github.com/VEuPathDB/web-eda/issues/1683