Skip to content

Latest commit

 

History

History
59 lines (36 loc) · 2.68 KB

README.md

File metadata and controls

59 lines (36 loc) · 2.68 KB
Raw

image

Demonstrated Skills

  • Conditional Rendering
  • Use of node-sass for the first time
  • Overlapping elements
  • CSS variables
To Do
  • Reduce redundancies in code using CSS function variables.
  • Condense React Components to reduce redundancies (isDesktop state condition is copy pasted throughout every component in order to render correctly)
Note: process.env.PUBLIC_URL refers to the public folder. In React, our app cannot call anything outside of the src folder without this env variable e.g. process.env.PUBLIC_URL + '/images/favicon-32x32.png'

The Challenge

Your users should be able to:

  • View the optimal layout for the site depending on their device's screen size
  • See hover states for all interactive elements on the page

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.