TouchBase is a web application that streamlines job application data for a user.
"Take a load off of your job search with TouchBase, the best tool for organizing your career development. Add and search through jobs you've applied to, and make optimal use of the connections you've made along the way. TouchBase brings you closer to that final offer letter.
TouchBase displays your data for a short profile, jobs you applied to, connections you've made through networking, and events you're interested in attending. It secures this data to an account using its very own API and through hashing passwords and creating an encrypted token. You can access, add, edit, and delete all of this data as the user sees fit. You can also organize how this data is displayed. Additional features for how this data is displayed can be continuously added.
TouchBase was built with a plan, but with as the codebase progressed an on-needed basis formed. The three main components (Jobs, Connections, and Events) are almost entirely identically to each other with the exception of styling and small functionality changes. These components are well-commented, so it's easy to understand what is happening in the code, but there's a lot of repeated information between the components.
TouchBase may need DRY refactoring in how these components relate to one another. The components operate in a very straight-forward and clear way, but there are areas where it can definitely be consolidated.
Refactoring would also be very useful in terms of styling. There are a lot of repeated styles in the SCSS files and it would be useful to turn some into variables and mix-ins.
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.
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