primer/css
1
1
Fork 0
mirror of https://github.com/primer/css.git synced 2024-12-29 17:12:27 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #1212 from wbrijesh/patch-1

Browse Source 
Spelling correction
This commit is contained in:
simurai 2021-02-19 15:57:43 +09:00 committed by GitHub
commit 7a556a93b2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/getting-started/contributing.md
View File

@ -18,7 +18,7 @@ Decisions to add new components are made on a case-by-case basis, with help from
- If your design is difficult to compose with current styles, does this highlight problems with existing components (such as overly-specific components, or missing objects and utilities)?
- Is this a totally new pattern or should it be an extension of an existing component?
- How is this pattern being implemented currently - have you identified problems with it’s current implementation that can be improved with adding a new pattern?
- Is the desire for this new pattern a side-effect of lacking documentation or mis-understandings of use with current styles?
- Is the desire for this new pattern a side-effect of lacking documentation or misunderstanding of use with current styles?
- Are there special factors that need to be considered as to why the this pattern needs it’s own styles? Such legal issues, usability issues, or branding and trademarks?
- Is this something that would be better handled by other front-end code rather than CSS?
- Every new addition of CSS means we ask our users to download a larger CSS file, and we increase the maintenance work of our CSS framework. Does the convenience of adding these new styles outweigh those costs?