For steps on how to work with this repository please see here
🚫 Note: All lines that start with 🚫 are instructions and should be deleted before this is posted to your first Pull-Request is merged. This is intended to be a guideline. Feel free to add your own flare to it.
You can find the deployed project at Underdogdevs.
🚫Add contributor info below, make sure add images and edit the social links for each member. Add to or delete these place-holders as needed
Vaibhavi Balar | Tom Bielawski | Seth Blakely | Isaac Ellingwood | Jordan Gearhart |
---|---|---|---|---|
UX/UI | UX/UI | TPM | Front End | Front End |
Joshua Gearhart | Trevour Guild | Raphael Hebert | Christopher Henao | Marie Hotchkiss |
---|---|---|---|---|
Back End | TPM | Front End | Back End | Back End |
Jesse Johns | Taylor Kang-Illescas | Damien Leu | Aldo Mata | Kenny Miesner |
---|---|---|---|---|
TPM | Front End | Back End | Back End | UX/UI |
Marius Moldovan | Spencer Patterson | Rory Roberts | Johanna Rodriquez | Rick Mansfield |
---|---|---|---|---|
Front End | Back End | UX/UI | UX/UI | TPM |
Rafael Mendoza | Kade Griffith | Teresa Franxman | Richard J Oh | Nicholas Hamilton |
---|---|---|---|---|
UX/UI | TPM | UX/UI | Front End | Front End |
Chris Boyle | Courtney Harris | Shawn Rice | Placeholder | Placeholder |
---|---|---|---|---|
Back End | Back End | TPM | Placeholder | Placeholder |
Chris Boyle | Courtney Harris | Shawn Rice | Placeholder | Placeholder |
---|---|---|---|---|
Back End | Back End | TPM | Placeholder | Placeholder |
Markeisha Wallace | Brittany Pete | Kim Nguyen | Josh Patton | Mallory Shea |
---|---|---|---|---|
TPM | TPM | Front End | Front End | UI/UX |
🚫 more info on using badges here
- Clone the repo front-end repository to your machine. DO NOT FORK.
- Create an environment file (.env) based on the sample .env front-end and populate the environment variables .env variables
- Run:
npm install
to download all dependencies. - Run:
npm start
to start your local development server.
When using Okta for authentication, the app will need to run locally on port 3000.
- feature one
- feature two
- feature three
- feature four
- feature five
- point one
- point two
- point three
🚫 List the rest of the back end end features and libraries in the same format as the framework above
🚫Replace text below with a description of the API
Water's like me. It's laaazy ... Boy, it always looks for the easiest way to do things A little happy sunlight shining through there. Let all these little things happen. Don't fight them. Learn to use them. Even the worst thing we can do here is good.
🚫Replace text below with a description of the API
This is the way you take out your frustrations. Get away from those little Christmas tree things we used to make in school. Isn't it fantastic that you can change your mind and create all these happy things? Everything's not great in life, but we can still find beauty in it.
🚫Replace text below with a description of the API
You can do anything your heart can imagine. In life you need colors. This is where you take out all your hostilities and frustrations. It's better than kicking the puppy dog around and all that so. I'm sort of a softy, I couldn't shoot Bambi except with a camera. Trees get lonely too, so we'll give him a little friend. We'll lay all these little funky little things in there.
🚫explain how to install the required dependencies to get this project up and running with yarn and NPM
🚫replace these examples with your own
* build - creates a build of the application
* start - starts the production server after a build is created
* test - runs tests in **tests** directory \* eject - copy the configuration files and dependencies into the project so you have full control over them
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.
- 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.
See [Backend Documentation](🚫link to your backend API SWAGGER DOCS here) for details on the backend of our project.