Merged
Conversation
…r the guides to utilize. [ref #3635]
Added an introductory sentence before the table of contents to explain the purpose and intended usage of the style guide.
Started editing this page, got through the Foundations and Grid Layouts sections. If any of the elaborations I made were inaccurate, let me know! I'm planning on getting further into this doc tomorrow.
…or guides footer. [ref #3635]
-Reviewed full document for typos, grammar, and clarity -Changed Color Palette subsection titles to include the word "color" for easy skim-ability. -Changed Icons subsection titles to include the word "icons" for easy skim-ability -Changed order of sections for "narrative" flow, moving from basics to text to colors to icons to images.
…sed build warnings. [ref #3635]
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
New Contributors
Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and while we'd love it if you write unit tests, but we're happy to review your pull request even if you don't write tests or complete all of the checklist items below! Thanks for making a pull request!
Related Issues
Pull Request Checklist