├── .gitattributes
├── media
├── badge.ai
├── logo.ai
├── logo.png
├── logo.svg
└── badge.svg
├── create-list.md
├── code-of-conduct.md
├── awesome.md
├── contributing.md
└── readme.md
/.gitattributes:
--------------------------------------------------------------------------------
1 | * text=auto
2 | *.ai binary
3 | readme.md merge=union
4 |
--------------------------------------------------------------------------------
/media/badge.ai:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/yyx990803/awesome/HEAD/media/badge.ai
--------------------------------------------------------------------------------
/media/logo.ai:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/yyx990803/awesome/HEAD/media/logo.ai
--------------------------------------------------------------------------------
/media/logo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/yyx990803/awesome/HEAD/media/logo.png
--------------------------------------------------------------------------------
/create-list.md:
--------------------------------------------------------------------------------
1 | # Creating Your Own List
2 |
3 | - Read the [awesome manifesto](https://github.com/sindresorhus/awesome/blob/master/awesome.md) and ensure your list complies.
4 | - Search this list before making a new one, as yours may be a duplicate. If it is, try and contribute to the best one instead of making your own.
5 | - Your awesome list should have the [awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge), a [license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license), and [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines). Adding a [code of conduct](http://contributor-covenant.org/) is also strongly recommended.
6 | - Wait at least a couple of weeks after creating a list before submitting to this list to give it a chance to mature.
7 | - Make sure you read the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) before submitting a request for your list to be added here.
8 |
9 | Thanks for being awesome!
10 |
--------------------------------------------------------------------------------
/media/logo.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/code-of-conduct.md:
--------------------------------------------------------------------------------
1 | # Contributor Code of Conduct
2 |
3 | As contributors and maintainers of this project, and in the interest of
4 | fostering an open and welcoming community, we pledge to respect all people who
5 | contribute through reporting issues, posting feature requests, updating
6 | documentation, submitting pull requests or patches, and other activities.
7 |
8 | We are committed to making participation in this project a harassment-free
9 | experience for everyone, regardless of level of experience, gender, gender
10 | identity and expression, sexual orientation, disability, personal appearance,
11 | body size, race, ethnicity, age, religion, or nationality.
12 |
13 | Examples of unacceptable behavior by participants include:
14 |
15 | * The use of sexualized language or imagery
16 | * Personal attacks
17 | * Trolling or insulting/derogatory comments
18 | * Public or private harassment
19 | * Publishing other's private information, such as physical or electronic
20 | addresses, without explicit permission
21 | * Other unethical or unprofessional conduct
22 |
23 | Project maintainers have the right and responsibility to remove, edit, or
24 | reject comments, commits, code, wiki edits, issues, and other contributions
25 | that are not aligned to this Code of Conduct, or to ban temporarily or
26 | permanently any contributor for other behaviors that they deem inappropriate,
27 | threatening, offensive, or harmful.
28 |
29 | By adopting this Code of Conduct, project maintainers commit themselves to
30 | fairly and consistently applying these principles to every aspect of managing
31 | this project. Project maintainers who do not follow or enforce the Code of
32 | Conduct may be permanently removed from the project team.
33 |
34 | This Code of Conduct applies both within project spaces and in public spaces
35 | when an individual is representing the project or its community.
36 |
37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
38 | reported by contacting a project maintainer at sindresorhus@gmail.com. All
39 | complaints will be reviewed and investigated and will result in a response that
40 | is deemed necessary and appropriate to the circumstances. Maintainers are
41 | obligated to maintain confidentiality with regard to the reporter of an
42 | incident.
43 |
44 |
45 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
46 | version 1.3.0, available at
47 | [http://contributor-covenant.org/version/1/3/0/][version]
48 |
49 | [homepage]: http://contributor-covenant.org
50 | [version]: http://contributor-covenant.org/version/1/3/0/
51 |
--------------------------------------------------------------------------------
/awesome.md:
--------------------------------------------------------------------------------
1 | # The awesome manifesto
2 |
3 | If you want your list to be included on `awesome`, try to only include actual awesome stuff in your list. After all, it's a curation, not a collection.
4 |
5 | But **what is awesome?**
6 |
7 | ## Only awesome is awesome
8 |
9 | Research if the stuff you're including is actually awesome. Put only stuff on the list you or another contributor can personally recommend and rather leave stuff out than include too much.
10 |
11 | ## Awesome badge
12 |
13 | [](https://github.com/sindresorhus/awesome)
14 |
15 | Add an awesome badge to the top of your list, right to the title. [Example](https://github.com/sindresorhus/awesome-nodejs).
16 |
17 | ```md
18 | [](https://github.com/sindresorhus/awesome)
19 | ```
20 |
21 | ## Comment on why something is awesome
22 |
23 | Apart from suggesting a particular item on your list, you should also inform your readers *why* it's on the list and how they will benefit from it.
24 |
25 | ## Make it clear what the list is about
26 |
27 | Have a succinct description at the top of your readme. Make sure your list covers a certain scope and nothing else. Link to other awesome lists if you think they already cover a certain subject good enough.
28 |
29 | ## Pay attention to grammar
30 |
31 | Ensure your list is grammatically correct, typo free and has no Markdown formatting errors. This should also apply to pull requests.
32 |
33 | ## Choose an appropriate license
34 |
35 | Keep in mind that if you [haven't selected a license](http://choosealicense.com/no-license/), it basically means the people are *not* allowed to reproduce, distribute or create derivative works.
36 |
37 | [Creative Commons licenses](https://creativecommons.org/) are perfect for this purpose. **We would recommend [`CC0`](https://creativecommons.org/publicdomain/zero/1.0/).** Code licenses like MIT, BSD, GPL, and so forth are not recommended.
38 |
39 | ## Include contribution guidelines
40 |
41 | People who are contributing to your list should have a clear understanding how they should do so.
42 |
43 | If you don't feel like writing one from scratch, feel free to take our [contributing.md](contributing.md) and modify it to your own needs.
44 |
45 | ## Stylize your list properly
46 |
47 | Create a [table of contents](https://github.com/sindresorhus/stuff/blob/master/toc-generators.md), organize the content into different categories, and use images if suitable. Ensure all entries are consistent (e.g. all entry descriptions end in a `.`).
48 |
49 | ## Accept other people's opinion
50 |
51 | If you're an owner of the list, respect other people's opinion. If there are plenty of users not agreeing to your decision, give it a second thought.
52 |
53 | ## Discovery
54 |
55 | Link back to this list from your list so users can easily discover more lists.
56 |
--------------------------------------------------------------------------------
/contributing.md:
--------------------------------------------------------------------------------
1 | # Contribution Guidelines
2 |
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 |
5 | ## Table of Contents
6 |
7 | - [Adding to this list](#adding-to-this-list)
8 | - [Creating your own awesome list](#creating-your-own-awesome-list)
9 | - [Adding something to an Awesome list](#adding-something-to-an-awesome-list)
10 | - [Updating your Pull Request](#updating-your-pull-request)
11 |
12 | ## Adding to this list
13 |
14 | Please ensure your pull request adheres to the following guidelines:
15 |
16 | - Search previous suggestions before making a new one, as yours may be a duplicate.
17 | - Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description.
18 | - Make an individual pull request for each suggestion.
19 | - Use [title-casing](http://titlecapitalization.com) (AP style).
20 | - Use the following format: `[List Name](link)`
21 | - Link additions should be added to the bottom of the relevant category.
22 | - New categories or improvements to the existing categorization are welcome.
23 | - Check your spelling and grammar.
24 | - Make sure your text editor is set to remove trailing whitespace.
25 | - The pull request and commit should have a useful title.
26 | - The body of your commit message should contain a link to the repository.
27 |
28 | Thank you for your suggestions!
29 |
30 | ## Creating your own awesome list
31 |
32 | To create your own list, check out the [instructions](create-list.md).
33 |
34 | ## Adding something to an awesome list
35 |
36 | If you have something awesome to contribute to an awesome list, this is how you do it.
37 |
38 | You'll need a [GitHub account](https://github.com/join)!
39 |
40 | 1. Access the awesome list's GitHub page. For example: https://github.com/sindresorhus/awesome
41 | 2. Click on the `readme.md` file: 
42 | 3. Now click on the edit icon. 
43 | 4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). 
44 | 5. Say why you're proposing the changes, and then click on "Propose file change". 
45 | 6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)!
46 |
47 | ## Updating your Pull Request
48 |
49 | Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-* list guidelines.
50 |
51 | [Here](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that.
52 |
--------------------------------------------------------------------------------
/media/badge.svg:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/readme.md:
--------------------------------------------------------------------------------
1 |