You can find the deployed project at Live in The Best Place.
| Devin Bielejec | Nazifa Hossain | Seth Lachman | Chris Pupo | Erik Sandoval |
|---|---|---|---|---|
 |
 |
|
|
|
 |
|
|
|
|
Moving is an inevitable part of life that most people will experience. Often, there's buyer's remorse after the fact for one reason or another. With Let's Move Homie, we strive to get you as much information about a potential place to live in a quick, user friendly manner. Whether you want to look up a specific location you have in mind, or just want to scroll across a map and see how certain cities rank compared to others, Let's Move Homie is here to help.
- Login/Logout
- Profile
- Factors (User clicks checkbox for which factor is important)
- Top-10 cities (Roughly standardized top 10 cities)
- Map - City Outlines
- Strong React Ecosystem
- Reusable components
- Great state management
- Great Dev tools
Back end built using:
MongoDB, Express and NodeJS, REST API
We used Styled Systems to create a custom design system. Styled Systems Readme
In order for the app to function correctly, the user must set up their own environment variables. There should be a .env file containing the following:
🚫These are just examples, replace them with the specifics for your app
🚫Document what you used for testing and why
Please run yarn install then the following dependencies:
"axios": "^0.19.0",
"react": "^16.11.0",
"react-dom": "^16.11.0",
"react-hook-form": "^3.27.0",
"react-redux": "^7.1.3",
"react-router-dom": "^5.1.2",
"react-scripts": "3.2.0",
"reduce-reducers": "^1.0.4",
"redux": "^4.0.4",
"redux-thunk": "^2.3.0",
"styled-components": "^4.4.1",
"styled-system": "^5.1.2"When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a [code of conduct].
Please follow it in all your interactions with the project.
If you are having an issue with the existing project code, please submit a bug report under the following guidelines:
- Check first to see if your issue has already been reported.
- Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
- Create a live example of the problem.
- Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.
We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.
If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.
Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.
- Ensure any install or build dependencies are removed before the end of the layer when doing a build.
- Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
- Ensure that your code conforms to our existing code conventions and test coverage.
- Include the relevant issue number, if applicable.
- You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
These contribution guidelines have been adapted from this good-Contributing.md-template.
See Backend Documentation for details on the backend of our project.