gherciu / gatsby-all-in

🗃⚛️A GatsbyJs starter that includes the most popular js libraries, already pre-configured and ready for use.

gatsby-all-in

🗃⚛️A GatsbyJs starter that includes the most popular js libraries, already pre-configured and ready for use. DEMO.

Getting started

• Create a new Gatsby site using the gatsby-all-in starter: gatsby new blog https://github.com/Gherciu/gatsby-all-in
• Edit configuration variables in .env.development file
• Start dev server: npm run start

Features

• ESLint and Stylelint to enforce code style. Run npm run lint:scripts for .js|.jsx and npm run lint:styles for .css|.scss files.
• Pre-commit hooks with husky and lint-staged
• Useful SCSS helpers _mixins and _vars see all in ./src/styles
• redux and redux-devtools implimented and configured to work well in development mode and production. The store is hot reloadable ;)
• Aliases for all folders (components, styles, store etc.) see all available aliases in ./gatsby-config.js
• antd is added and configured to work well as an UI framework (css normalization is not need, antd has own)
• All folders in ./src have own README.md file with a little documentation and usage guide
• Helmet implimented and configured with gatsby-plugin-react-helmet see an example in ./src/layouts/MainLayout.js
• Configured tailwindcss a utility-first CSS framework for rapidly building custom designs.

When ready to build for production

• Create file .env.production the content should be the same as in .env.development
• Build the project: npm run build
• Start production server: npm run serve

---

Contributing

1. Fork it!
2. Create your feature branch: git checkout -b my-new-feature
3. Commit your changes: git commit -am 'Add some feature'
4. Push to the branch: git push origin my-new-feature
5. Submit a pull request :D

Or you can sponsor via Open Collective

Author

@Gherciu/gatsby-all-in © GHERCIU, Released under the MIT License.
Authored and maintained by GHERCIU with help from contributors (list).

If you like this repository star⭐ and watch👀 on GitHub

💫 Deploy

gatsby-all-in's Issues

implement tailwindcss and add configuration file for this

Add config-provider from antd design

Add redux-toolkit to simplify the create store and reducers process

add an alias to tailwind config

useful to parse values from tailwind theme config

use (wrapPageElement) to wrap entire app in MainLayout

For more details see: wrapPageElement

implement and configure .nvmrc (to work corect in most environements like as netlify etc.))

configure circle-ci as a CI/CD or other popular CI/CD provider

implement a redux side-efect middleware like as redux-soldier/redux-saga/redux-observable

implement stylelint-prettier

iimplement .snyc as a library vulnerabilitys manager

implement a library for inject dynamic reducers in redux

add internationalization with i18n or gatsby-react-intl

rewrite all readme files from ./src folder in a more declarative way

add a util to get route config and theme config

add gatsby plugin nprogress as a page loader indicator

Add common-contaners folder structure

implement and configure jest with enzyme/react-testing-library

remove initializeStore function in favor to a static constant

implement DocumentationLayout and LandingLayout corect

update eslintrc file

replace this line 'prettier/prettier': ['error', prettierOptions], in favour to this 'prettier/prettier': 'error', I think this is the same thing but in the first variant, you need to read also the prettier config

Remove bourbon package because is incompatible with postCss

remove ramda in favour to lodash

add netlify button why indicate if the build is passed or not

implement react-svgr to import inline svg and sanitize this