ref(css): Shrink h4 to differentiate it from h3
#1675
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.
As @rhcarvalho correctly points out here, actual headings have many advantages over text made to look like a heading by bolding it and putting it on its own line.
In markdown, it's the difference between
#### Dogs Ruleand**Dogs Rule**. In HTML it means anchor links, consistent styling, and better accessibility (vs. lack of all of those things).So, a clear win for headings, right? It would be, except that with our current CSS, it's next to impossible to tell an
h4(#### Dogs Rule) from anh3(### Dogs Rule), because the difference is only a 4% reduction in size. Since usingh4s breaks the document's visual hierarchy, folks in many cases choose to use the fake heading in spite of its drawbacks, because it is visually distinct from anh3.This PR shrinks the size of
h4s so that you get the look of the fake heading, with all of the advantages of the real one.