Visit https://loving-engelbart-9e6bf3.netlify.com/
- Visual Fidelity: Remain as close as posible to the design.
- UI Components: clearly differentiate between UI components (in 'elements' folder) and intentful/specific components (in 'components' folder).
- Layout vs Appearance: Separate styling between Layout and appearance. Components control their own appearance but their Layout rules are defined by their parents. This helps in making components reusable.
- Structure: Provide a folder/file structure that allows for maintaining code tidy even as the codebase grows.
Things left out due to shortness of time.
- Incomplete: Was not able to work on history chart nor on type ahead features.
- Syntax: Bad habit from current workplace, I need to go through the codebase and add ; semicolons at the end of several lines of code.
- API request: Used Netlify proxying as a workaround for CoinMarketCap forbidding calls straight from browser but with more time would make it so that the API key is used from a stores .env variable instead of being sent as a query param. that lists your approach identifies any known issues in the implementation, opportunities for improvement, or environment configuration.
- Other: Anything that where considered optimization where
This project was bootstrapped with Create React App.
In the project directory, you can run:
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.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify