Skip to content
🗃⚛️A GatsbyJs starter that includes the most popular js libraries, already pre-configured and ready for use.
JavaScript CSS
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
src
static
.browserslistrc
.editorconfig
.env.development
.env.production
.eslintignore
.eslintrc.js
.gitignore
.prettierignore
.prettierrc
.stylelintignore
.stylelintrc
LICENSE.md
README.md
commitlint.config.js
gatsby-browser.js
gatsby-config.js
gatsby-ssr.js
package-lock.json
package.json
postcss.config.js
tailwind.config.js

README.md

gatsby-all-in

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

Netlify Status GitHub Gatsby-All-In

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

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

Deploy to Netlify

You can’t perform that action at this time.