This is a simple web application which is intended to demonstrate the following ideas:
-
software architectural thinking;
-
decoupled frontend and backend;
-
a DevOps mindset;
-
some benefits of using the latest technology;
-
applicability of JavaScript and Node to solving real-life problems.
-
The app should display a list of contacts retrieved from a backend service.
-
When a contact is clicked, a business card of this contact should be presented. The business card should contain the following attributes:
- full name;
- position;
- phone number;
- email;
- full address;
- website (URL);
- taglines (an array of strings).
-
The business card of the client could potentially be an image of their real business card (scanned during the data entry process), but if such is not available, a default business card should be presented (as a generated view).
-
The app should allow to make a simple search in the contact list.
-
The app should show in a separate view how many contacts starting from each alphabet letter are there.
-
The app should show each contact's location on a map.
-
The app should be nice and easy to use (give the user experience a priority).
-
The app should be a pleasure to develop (mind the developer experience too).
-
The app should be easy to deploy (think about continuous deployment).
-
The backend service should be scalable (in all possible directions, if possible).
-
The code should be "production-ready" (deploying it to production will not harm anyone).
-
The project should have a clear and meaningful structure and code organization.
-
All the manual tasks should be automated if possible (use build tools).
-
Standard tasks should be solved using design patterns, whenever this applies.
TBD
TBD
MIT
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