Use System fonts for sphinx documentation #2084
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change(s)
This PR changes the sphinx font choices to use the system fonts where possible.
This used to not be supported well, but has recently become supported well enough that various frameworks and sites like Bootstrap have adopted it.
For the most part, this lets the user+OS vendor have more control over the legibility of the text, allowing for better variable weights and respects any legibility choices the user may have made.
If those are not specified, or supported, they fall back to the previous font choices that Read the Docs used.
Fixes Issue(s)
This fixes a few minor issues I was seeing:
Certain font sizes and weights weren't rendering differently enough than other fonts. e.g the H3 and H4 styling had very similar visual weights due to the font being picked up.
The USD header image text was rendering as serif for me, even though the CSS expected san-serif. This fixes that
Missing semicolon after calc in
.usd-title-image-outer
. I'm not sure what was meant to be calc'd here...but this at least fixes the syntax error.