• Work in a fork of this repository
• Work in a branch on your fork
• Write all of your code in a directory named lab- + <your name> e.g. lab-duncan
• Submit a pull request to this repository
• Submit a link to your pull request on canvas
• Submit a question, observation, and how long you spent on canvas

• copy the back-end lecture demo from today for your API, and enable your linter.

• README.md -- with a documentation about your lab
• .babelrc -- with all dependencies and dev-dependencies
• .eslintrc.json -- with the class .eslintrc.json file
• .gitignore -- with a robust gitignore
• .eslintignore -- with the class .eslintignore
• yarn.lock -- with the yarn lockfile
• package.json -- with all dependencies and dev-dependencies
• webpack.config.js -- with webpack config
• src/ -- containing the front end code
• src/main.js -- renders the app
• src/style -- containing your sass
• src/style/main.scss -- for importing and including reset and base
• src/style/_vars.scss -- sass variables
• src/style/_reset.scss -- sass reset
• src/style/_base.scss -- base styles
• src/style/_layout.scss -- layout styles

• Create a frontend that follows react redux best practices
• Create a landing page that enables a user to signup or signin
• Redirect the user to the dashboard page on signup or signin
• Store the users token in a cookie or localstorage on signin

• Test your redux reducers
• Test your util methods

Write a description of the project in your README.md, including detailed instructions for how to build your app. In your frontend README.md add a code block with your frontend .env vars, and in your backend README.md add a code block with your backend .env vars.