|
2 | 2 |
|
3 | 3 | Please note that this project is released with a [Contributor Code of Conduct](CODE-OF-CONDUCT.md). By participating in this project you agree to abide by its terms. |
4 | 4 |
|
5 | | - |
6 | 5 | ## Table of Contents |
7 | 6 |
|
8 | 7 | - [Adding to This List](#adding-to-this-list) |
9 | 8 | - [Updating Your Pull Request](#updating-your-pull-request) |
10 | 9 |
|
11 | | - |
12 | 10 | ## Adding to This List |
13 | 11 |
|
14 | 12 | Please ensure your pull request adheres to the following guidelines: |
15 | 13 |
|
16 | | -* Search open and closed PRs to avoid duplicate suggestions. |
17 | | -* Only submit CSS tips that you think would be useful to others. This implies each tip has enough succinct content to describe why it's useful. |
18 | | -* Add your tip at the bottom of the [README](https://github.com/AllThingsSmitty/css-protips/blob/master/README.md) document. Add a link to your tip at the bottom of the table of contents. |
19 | | -* Use [title-case](https://titlecaseconverter.com/). |
20 | | -* Code formatting should follow standard [CSSLint](http://www.csslint.net) default settings, including: |
21 | | - * Indent with two spaces |
22 | | - * Use shorthand, e.g., `margin: 10px 10px 5px;` |
23 | | - * Use double quotes, e.g., `background: url("logo.svg");` |
24 | | - * Sort properties alphabetically |
25 | | -* Make sure your text editor is set to remove trailing whitespace. |
26 | | -* Check your spelling and grammar. |
27 | | -* The PR should have a useful title. |
| 14 | +- Search open and closed PRs to avoid duplicate suggestions. |
| 15 | +- Only submit CSS tips that you think would be useful to others. This implies each tip has enough succinct content to describe why it's useful. |
| 16 | +- Add your tip at the bottom of the [README](https://github.com/AllThingsSmitty/css-protips/blob/master/README.md) document. Add a link to your tip at the bottom of the table of contents. |
| 17 | +- Use [title-case](https://titlecaseconverter.com/). |
| 18 | +- Code formatting should follow standard [CSSLint](http://www.csslint.net) default settings, including: |
| 19 | + - Indent with two spaces |
| 20 | + - Use shorthand, e.g., `margin: 10px 10px 0.5rem;` |
| 21 | + - Use double quotes, e.g., `background: url("logo.svg");` |
| 22 | + - Use leading zeros with numberic values, e.g., `padding: 0.75rem;` |
| 23 | + - Sort properties alphabetically |
| 24 | + - **Avoid letting your code formatter format other section of the README file.** |
| 25 | +- Make sure your text editor is set to remove trailing whitespace. |
| 26 | +- Check your spelling and grammar. |
| 27 | +- The PR should have a useful title. |
28 | 28 |
|
29 | 29 | Thank you for your suggestions! |
30 | 30 |
|
31 | | - |
32 | 31 | ## Updating Your Pull Request |
33 | 32 |
|
34 | | -Sometimes a maintainer will ask you to edit your pull request before it's included. This is normally due to spelling errors or because your PR didn't match the above guidelines guidelines. [This write-up](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) covers the different ways you can change a pull request. |
| 33 | +Sometimes a maintainer will ask you to edit your pull request before it's included. This is normally due to spelling errors or because your PR didn't match the above guidelines guidelines. [This write-up](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) covers the different ways you can change a pull request. |
0 commit comments