├── .gitattributes ├── .editorconfig ├── PULL_REQUEST_TEMPLATE.md ├── CONTRIBUTING.md ├── README.md └── CODE-OF-CONDUCT.md /.gitattributes: -------------------------------------------------------------------------------- 1 | * text=auto 2 | readme.md merge=union 3 | -------------------------------------------------------------------------------- /.editorconfig: -------------------------------------------------------------------------------- 1 | root = true 2 | 3 | [*] 4 | indent_style = tab 5 | end_of_line = lf 6 | charset = utf-8 7 | trim_trailing_whitespace = true 8 | insert_final_newline = true -------------------------------------------------------------------------------- /PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | - [ ] I have read [Contribution Guidelines](https://github.com/reyronald/awesome-toolkits/blob/master/CONTRIBUTING.md) and followed everything. 2 | - [ ] I have an appropriate description with correct grammar. 3 | 4 | **[what you are adding here, with a link]** 5 | 6 | [Brief comments on why you think this should be added] 7 | 8 | 12 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please note that this project is released with a 4 | [Contributor Code of Conduct](code-of-conduct.md). By participating in this 5 | project you agree to abide by its terms. 6 | 7 | --- 8 | 9 | Ensure your pull request adheres to the following guidelines: 10 | 11 | If you are adding a new entry: 12 | 13 | 1. Make sure the title says "Add [new entry]", with the name of the entry. 14 | 1. The entry is in the appropiate section. 15 | 1. The entry is not a duplicate. 16 | 1. The format of the entry should be a link to the repository or site and 17 | a short description, separated by a dash, and ending with a punctuation mark. Example: 18 | * [Entry](Link URL) - Short description. 19 | 1. The text of the link should be the name of the package or project. 20 | 1. Is added at the bottom of of each section/category. 21 | 22 | Thank you for your suggestions! 23 | 24 | ## Updating your PR 25 | 26 | A lot of times, making a PR adhere to the standards above can be difficult. 27 | If the maintainers notice anything that we'd like changed, we'll ask you to 28 | edit your PR before we merge it. There's no need to open a new PR, just edit 29 | the existing one. If you're not sure how to do that, 30 | [here is a guide](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md) 31 | on the different ways you can update your PR so that we can merge it. 32 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Awesome Toolkits [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome) 2 | 3 | > A curated list of open source, high-quality, popular and well maintained toolkits 4 | 5 | A "toolkit" is a set of tools in any form that allows you to create applications with no build configuration. 6 | 7 | ## Contents 8 | 9 | - [Web](#web) 10 | - [Mobile](#mobile) 11 | - [Other](#other) 12 | - [Related lists](#related-lists) 13 | - [Contribute](#contribute) 14 | - [License](#license) 15 | 16 | ## Web 17 | 18 | * [Create React App](https://github.com/facebookincubator/create-react-app) - Create React apps with no build configuration. 19 | * [Create React App Typescript](https://github.com/wmonk/create-react-app-typescript) - Create React apps using typescript with no build configuration. 20 | * [vue-cli](https://github.com/vuejs/vue-cli) - A simple CLI for scaffolding Vue.js projects. 21 | * [Angular CLI](https://github.com/angular/angular-cli) - CLI tool for Angular. 22 | * [ember-cli](https://github.com/ember-cli/ember-cli) - The Ember.js command line utility. 23 | * [Parcel](https://github.com/parcel-bundler/parcel) - Blazing fast, zero configuration web application bundler. 24 | * [Next.js](https://github.com/zeit/next.js/) - Next.js is a minimalistic framework for server-rendered React applications. 25 | * [Nuxt.js](https://github.com/nuxt/nuxt.js) - Versatile Vue.js Framework. 26 | * [Razzle](https://github.com/jaredpalmer/razzle) - Create server-rendered universal JavaScript applications with no configuration. 27 | * [nwb](https://github.com/insin/nwb) - A toolkit for React, Preact, Inferno & vanilla JS apps, React libraries and other npm modules for the web, with no configuration (until you need it). 28 | * [Gatsby](https://github.com/gatsbyjs/gatsby) - Blazing-fast static site generator for React. 29 | * [Neutrino ](https://github.com/mozilla-neutrino/neutrino-dev) - Create and build modern JavaScript applications with zero initial configuration. 30 | 31 | ## Mobile 32 | 33 | * [Create React Native App](https://github.com/react-community/create-react-native-app) - Create a React Native app on any OS with no build config. 34 | 35 | ## Other 36 | 37 | * [react-scripts](https://github.com/facebookincubator/create-react-app/tree/master/packages/react-scripts) - This package includes scripts and configuration used by Create React App. 38 | * [kcd-scripts](https://github.com/kentcdodds/kcd-scripts) - CLI toolbox for common scripts for [Kent C. Dodds](https://github.com/kentcdodds/kcd-scripts)' projects. 39 | 40 | ## Related lists 41 | 42 | * [Awesome](https://github.com/sindresorhus/awesome) - Curated list of awesome lists. 43 | * [Awesome Node.js](https://github.com/sindresorhus/awesome-nodejs) - Delightful Node.js packages and resources. 44 | 45 | ## Contribute 46 | 47 | Contributions welcome! Read the [contribution guidelines](contributing.md) first. 48 | 49 | ## License 50 | 51 | [![CC0](http://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](http://creativecommons.org/publicdomain/zero/1.0) 52 | 53 | To the extent possible under law, [Ronald Rey](http://github.com/reyronald) has waived all copyright and 54 | related or neighboring rights to this work. 55 | -------------------------------------------------------------------------------- /CODE-OF-CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at reyronald@gmail.com. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at [http://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: http://contributor-covenant.org 74 | [version]: http://contributor-covenant.org/version/1/4/ 75 | --------------------------------------------------------------------------------