next-all-in
next-all-in copied to clipboard
πβοΈ Next starter for creating any type of site
Getting started
- Clone the repo:
git clone --depth=1 https://github.com/Gherciu/next-all-in.git <YOUR_PROJECT_NAME> - Edit configuration variables in
.env.developmentfile - Start dev server:
npm run start
Features
i18ninternationalization support ( Scalable apps need to support multiple languages, easily add and support multiple languages withnext-i18next).ESLintandStylelintto enforce code style. Runnpm run lint:scriptsfor.js|.jsxandnpm run lint:stylesfor.css|.scssfiles.- Pre-commit hooks with
huskyandlint-staged - Useful SCSS helpers
_mixinsand_varssee all in./styles reduxandredux-devtoolsimplimented and configured to work well indevelopmentmode andproduction. The store is hot reloadable ;)- Aliases for all folders (components, styles, store etc.) see all available aliases in
./next-config.js antdis added and configured to work well as an UI framework (css normalization is not need, antd has own)- All folders in
./and./componentshave own README.md file with a little documentation and usage guide - Configured
tailwindcssa utility-first CSS framework for rapidly building custom designs.
When ready to build for production
- Create file
.env.productionthe content should be the same as in.env.development - Build the project:
npm run build - Start production server:
npm run serve
Contributing
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature - Commit your changes:
git commit -am 'Add some feature' - Push to the branch:
git push origin my-new-feature - Submit a pull request :D
Or you can sponsor via Open Collective
Author
@Gherciu/next-all-in Β© GHERCIU, Released under the MIT License.
Authored and maintained by GHERCIU with help from contributors (list).