fix: add first-child rule and add back h1 styles w/ docs #181
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is automatically deployed with Now. Latest deployment for this branch: https://gatsby-theme-carbon-git-fork-vpicone-markdown-fix.carbon-design-system.now.sh |
jendowns
reviewed
Jun 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This reverts the style changes to the
h1tag fromv1.2.0in favor of a much more flexible approach to preserving the lead space of content containers. Instead of limiting the starting components, the first child of each page's content container will have it's margin-top removed.For most pages, we recommend starting with a
PageDescriptionfollowed byAnchorLinksif the content is long enough.Note: The title located in each page header is an
h1. Some resources suggest you should only have a singleh1per page, while others indicate it doesn't matter. As a rule, we recommend usingh2s as section headings for a consistent hierarchy in your markdown.