ch0ic3/awesome
1
0
Fork 0
mirror of https://github.com/sindresorhus/awesome.git synced 2024-12-22 17:06:08 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
😎 Awesome lists about all kinds of interesting topics
682 Commits 2 Branches 0 Tags 20 MiB
Markdown 100%
32ce665963
Go to file
Gilbert 32ce665963 Add small dev shops 
**https://github.com/gilbertginsberg/awesome-small-dev-shops**

**awesome small dev shops is a curated list of dev shops around the world with <= 30 employees. And this list exists because it benefits many groups of people — devs, designers, companies of all sizes, conference organizers, recruiters, small dev shops, among others.**

# By submitting this pull request I confirm I've read and complied with the below requirements.

**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**

- I have read and understood the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) and the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md).
- This pull request has a descriptive title.<br>For example, `Add Name of List`, not `Update readme.md` or `Add awesome list`.
- The entry in the Awesome list should:
	- Include a short description about the project/theme of the list. **It should not describe the list itself.**<br>Example: `- [Fish](…) - User-friendly shell.`, not `- [Fish](…) - Resources for Fish.`.
	- Be added at the bottom of the appropriate category.
- The list I'm submitting complies with these requirements:
	- **Has been around for at least 30 days.**<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
	- It's the result of hard work and the best I could possibly produce.
	- Non-generated Markdown file in a GitHub repo.
	- **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self)
	- The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics.
	- Not a duplicate.
	- Only has awesome items. Awesome lists are curations of the best, not everything.
	- Includes a project logo/illustration whenever possible.
		- Placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron)
		- The image should link to the project website or any relevant website.
		- The image should be high-DPI. Set it to maximum half the width of the original image.
	- Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
	- Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge).
		- Should be placed on the right side of the readme heading.
		- Should link back to this list.
	- Has a Table of Contents section.
		- Should be named `Contents`, not `Table of Contents`.
		- Should be the first section in the list.
		- Should only have one level of sub-lists, preferably none.
	- Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license).
		- That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.**
		- If you use a license badge, it should be SVG, not PNG.
	- Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines).
		- The file should be named `contributing.md`. Casing is up to you.
	- Has consistent formatting and proper spelling/grammar.
		- Each link description starts with an uppercase character and ends with a period.<br>Example: `- [AVA](…) - JavaScript test runner.`
		- Drop all the `A` / `An` prefixes in the descriptions.
		- Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`.
	- Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
- Go to the top and read it again.
2017-08-29 12:52:41 -04:00
media ✨ badge ✨ 2015-07-30 18:28:41 +02:00
.editorconfig add .editorconfig 2016-05-02 15:21:32 +07:00
.gitattributes minor tweaks 2016-01-18 13:22:00 +01:00
awesome.md DOC: Fixed minor but glaring grammar error 2016-03-15 13:51:46 -04:00
code-of-conduct.md update code of conduct 2016-05-02 15:27:18 +07:00
contributing.md 🐐 2016-05-03 16:58:47 +07:00
create-list.md Add a link to Yeoman generator for awesome lists (#847) 2017-03-07 18:38:05 +07:00
pull_request_template.md Minor guideline improvements 2017-08-11 02:09:45 +02:00
readme.md Add small dev shops 2017-08-29 12:52:41 -04:00

readme.md

Awesome



✨ Prelaunching the Awesome Weekly newsletter! ✨ Vote it up on Product Hunt


What is an awesome list?    Contribution guide    Creating a list    Sticker


Just type awesome.re to go here. Check out my blog and follow me on Twitter.

Contents

Platforms

Programming Languages

Front-End Development

Back-End Development

Computer Science

Big Data

Theory

Books

Editors

Gaming

Development Environment

Entertainment

Databases

Media

Learn

Security

Content Management Systems

Hardware

Business

Work

Networking

Decentralized Systems

Miscellaneous

License

CC0

To the extent possible under law, Sindre Sorhus has waived all copyright and related or neighboring rights to this work.