A playground for testing out all new tech for school, such as homework & school assignments. The goal of this project is to learn and understand CSS Grid, React Backend & Frontend fully so that I can implement it in coming school and work related projects.

• Quick start
• Status
• What's included
• Bugs and feature requests
• Contributing
• Community
• Versioning
• Creator
• Copyright and license

Navigate the a directory on your computer were you are working on sites and run this command:

git clone https://github.com/bromso/school-projects.git

Navigate the site’s directory and run this command.

npm i

Navigate the site’s directory and start it up. Will be located on url: http://localhost:8000

gatsby develop

Navigate the site’s directory and start it up. Wait until Gatsby has fully started and you will find the IP to put in your browser on your smartphone.

gatsby develop -H 0.0.0.0

Navigate the site’s directory and start it up. Will be located on url: http://localhost:6006

npm run storybook

I recommended to have these CLI's and dependencies in order to download and install everything without a clitch.

Logo	Name	Comments
	Homebrew	Package manager (for Mac)
	NVM	Node & NPM Version Manager
	NodeJS	JavaScript Runtime Engine
	NPMJS	Node Page Manager
	GatsbyJS	Site Generator
	Storbyook	UI Component Explorer

The application uses these technologies.

Logo	Name	Comments
	HTML5	Markup language
	CSS3	Styling language
	Husky	Git message validator
	Commitlint	Git linter
	Editorconfig	IDE coding styles
	Semantic Release	Versioning tool
	Prettier	Code formatter
	GatsbyJS	Site generator
	ReactJS	JavaScript library
	Styled-Components	ES6 & CSS to style components
	Storbyook	UI Component Explorer

The application uses these hosting vendors.

Logo	Name	Comments
	Github	Code repository
	Netlify	Webpage hosting

No contributions are necessary because the project is just for showing teacher at school.

No bug and feature request are necessary because the project is just for showing teacher at school.

For transparency into my release cycle and in striving to maintain backward compatibility, school-projects is maintained under the Semantic Versioning guidelines. Sometimes I screw up, but I adhere to those rules whenever possible.

Always write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should look like this:

$ git commit -m "A brief summary of the commit
>
> A paragraph describing what changed and its impact."

See the Releases section of our GitHub project for CHANGELOG for each release version of MaterialUI projects.

Avatar	Name	Email	Website
	Jonas Bröms	[email protected]	jonasbroms.com

• Prettier
• ESLint

This project is licensed under the terms of the MIT license. For more information, click here.