My goal was to simulate a professional work envionment.
- I built tis app based on Figma Design: project on figma
- I worked with tasks on Kanban Board.
- Somewhat complex stateful logic: Example code
- responsive CSS using Grid: Example code
- The application fetches data from tho local json-server: Example for request api and hooks
- Use Material-Ui (MUI) to build user interface
- I didn't use a state management library like Redux on purpose. For this app simple UseContext and useState is sufficient. I realized that more and more projects don't use Redux anymore since GraphQL or React-Query are often used for data management.
- Material-ui is a great library for styling. It includes SX prop as a shortcut for defining custom style. Use Scoped classes, and allows a seamless integration with JS.
- My plan is to become a full-stack developer eventually. But for the beginning I focus on the frontend. That's why I decided to use JSON-SERVER rather to create a custom server. I have Basic background knowledge as well.
- Refactor some of the components, especially header components.
- Add a special backend with Express.js & Mongodb
To run the app, be sure to install spotify-json-server
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.\
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!
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.