├── README.md ├── contributing.md ├── create-list.md └── fresh.md /README.md: -------------------------------------------------------------------------------- 1 | # We stay Fresh 🍅 2 | **Fresh** 🍅 is a new spin on [sindresorhus/awesome](https://github.com/sindresorhus/awesome) - community curated lists that never go out of style. 3 | 4 | - [Read the Fresh 🍅 Manifesto](https://github.com/sw-yx/fresh/blob/master/fresh.md) 5 | - Make a new list - fork this and rename the repo! 6 | 7 | # Keep Us Fresh 🍅 8 | 9 | - Submit new links via [Pull Request](https://github.com/sw-yx/fresh-async-react/pulls) 10 | - This list follows [the Fresh 🍅 Manifesto](https://github.com/sw-yx/fresh/blob/master/fresh.md) 11 | - New Links must use this format: 12 | - `DD MMM YYYY: [Link Name](link) Description` 13 | 14 | # Links 15 | 16 | - 29 Mar 2018: [fresh-concurrent-react](https://github.com/sw-yx/fresh-concurrent-react) Fresh links about async React (React Fiber, Time Slicing, React Suspense, etc) 17 | - 13 Nov 2018: [fresh-react-hooks](https://github.com/sw-yx/fresh-react-hooks) Fresh links about React Hooks by purpose, thoughtpieces and demos 18 | 19 | # History 20 | 21 | - None yet! 22 | 23 | ## License 24 | 25 | [![CC0](http://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0/) 26 | 27 | To the extent possible under law, [swyx](https://swyx.io) has waived all copyright and related or neighboring rights to this work. **Fresh** 🍅 is a new spin on [sindresorhus/awesome](https://github.com/sindresorhus/awesome) - community curated lists that never go out of style. 28 | -------------------------------------------------------------------------------- /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 fresh list](#creating-your-own-fresh-list) 9 | - [Adding something to an fresh list](#adding-something-to-an-fresh-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 | - **Link additions should have a date of relevance.** 28 | 29 | Thank you for your suggestions! 30 | 31 | ## Creating your own fresh list 32 | 33 | To create your own list, check out the [instructions](create-list.md). 34 | 35 | ## Adding something to a fresh list 36 | 37 | If you have something fresh to contribute to an fresh list, this is how you do it. 38 | 39 | You'll need a [GitHub account](https://github.com/join)! 40 | 41 | 1. Access the fresh list's GitHub page. For example: https://github.com/sindresorhus/fresh 42 | 2. Click on the `readme.md` file: ![Step 2 Click on Readme.md](https://cloud.githubusercontent.com/assets/170270/9402920/53a7e3ea-480c-11e5-9d81-aecf64be55eb.png) 43 | 3. Now click on the edit icon. ![Step 3 - Click on Edit](https://cloud.githubusercontent.com/assets/170270/9402927/6506af22-480c-11e5-8c18-7ea823530099.png) 44 | 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/). ![Step 4 - Edit the file](https://cloud.githubusercontent.com/assets/170270/9402932/7301c3a0-480c-11e5-81f5-7e343b71674f.png) 45 | 5. Say why you're proposing the changes, and then click on "Propose file change". ![Step 5 - Propose Changes](https://cloud.githubusercontent.com/assets/170270/9402937/7dd0652a-480c-11e5-9138-bd14244593d5.png) 46 | 6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)! 47 | 48 | ## Updating your Pull Request 49 | 50 | Sometimes, a maintainer of a fresh 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 fresh-* list guidelines. 51 | 52 | [Here](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that. 53 | -------------------------------------------------------------------------------- /create-list.md: -------------------------------------------------------------------------------- 1 | # Creating Your Own List 2 | 3 | - Read the [fresh manifesto](fresh.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 fresh list should be named `fresh-listname` and have a [license](fresh.md#choose-an-appropriate-license), and [contribution guidelines](fresh.md#include-contribution-guidelines). Adding a [code of conduct](http://contributor-covenant.org/) is also strongly recommended. 6 | - Make sure to regularly groom your fresh list for stale links! 7 | - Make sure you read the [contribution guidelines](contributing.md) before submitting a request for your list to be added here. 8 | 9 | Thanks for stayin' fresh! 10 | -------------------------------------------------------------------------------- /fresh.md: -------------------------------------------------------------------------------- 1 | # The fresh manifesto 2 | 3 | If you want your list to be included on **fresh**, try to only include actual fresh stuff in your list. After all, it's a **live curation, not a museum**. 4 | 5 | But **what is fresh?** 6 | 7 | ## The **fresh** standard v0.2 8 | 9 | - **fresh** as in **new**: **Every link must display an accompanying date**. For blogposts, talks or other content with a definite date, that is easy. For github projects or websites that are potentially evergreen, the date is the last date where the maintainer(s) have verified freshness. 10 | - long lists should split links out by topic, at maintainer's discretion. 11 | - **fresh** as in **good**: It is the responsibility of the maintainer to keep a high quality bar. This is necessarily subjective and imperfect. It also means people should fork `fresh` lists if they feel they can do a better job of maintaining. 12 | - **when stuff goes stale**: They get relegated to a `History` topic which is in chronological order for future readers to peruse. If really awesome stuff is going stale, too bad: get someone to make an updated talk or blogpost to replace it. Let the old make way for the new. 13 | 14 | ## Fresh summary 15 | 16 | Once you subjectively have enough content that it starts getting difficult to hold everything in your head, start writing an aggregated summary briefing on the topic. Use the links you have accumulated just like a wiki. 17 | 18 | ## Comment on why something is fresh 19 | 20 | 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. 21 | 22 | ## Make it clear what the list is about 23 | 24 | Have a succinct description at the top of your readme. Make sure your list covers a certain scope and nothing else. Link to other `fresh` lists if you think they already cover a certain subject well enough. 25 | 26 | ## Pay attention to grammar 27 | 28 | Ensure your list is grammatically correct, typo-free and has no Markdown formatting errors. This should also apply to pull requests. 29 | 30 | ## Choose an appropriate license 31 | 32 | 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. 33 | 34 | [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. 35 | 36 | ## Include contribution guidelines 37 | 38 | People who are contributing to your list should have a clear understanding of how they should do so. 39 | 40 | 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. 41 | 42 | ## Stylize your list properly 43 | 44 | 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 `.`). 45 | 46 | ## Accept other people's opinion 47 | 48 | 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. 49 | --------------------------------------------------------------------------------