This project was bootstrapped with Create React App.
- Kevin Smith - keveightysev
- Andrew Ackerman - ackers93
- Emily Bruner - emilybruner
- Anna Franceschi - bamfranceschi
- Aaron Gillies - Hail91
- Andrew Maddocks - AndrewMaddocks
- Vickie Nelson - victoriaisabeldesign
- Joscelyn Stancek - JossWritesCode
- Vanessa Tellez - vtellez1
- Cori Paris - coriagogo
- Sydney Crumley - srsimps19
- Andrew Goenner - drewgoenner
- Gustavo Isturiz - gisturiz
- Ty Lippe - TyLippe
- Ahmar Mansoor - ahmarsworld
- Matt Masters - TamaHills
- Gizella Ortiz - gizellaortiz
- Leslie Rodriguez - rleslie1015
- Nicholas Truson - NicholasTruson
Kansha Rewards is an app that was designed to increase satisfaction and productivity in the workplace by allowing employees to send recognition and badges to their peers in an app. The badges appear on the profile page, and the recognition appears on both the profile page and a live feed of all recognition, where employees will also be able to send a reaction and/or comment on the recognition.
- Register a new user by using Auth0
- Send recognition and badges to peers to thank them for their hard work
- Admins can delete users and any recognition/comments
- Mods can delete recognition/comments in their own department
- Users can comment and like recognition in a live feed, and see what badges their peers have earned.
- React allows us to determine and built the best architecture for our team
- Already known by the entire team, thus making it the easiest to work with
- Greatly simplifies global state management
- Versatile in its utility
- Allowed us to style according to our UX designer's specifications
Back end built using:
- Simpler and easier to use with Java, as its javascript.
- Node is what the majority of us learned for our backend unit
- Very capable and full featured
- Most of the team is familiar with Express
- The Connect Middleware functionality makes our backend service very extensible.
- Extremely flexible
- Full featured schema and query builders
- lets us switch from development to staging to production with ease.
Authenticate and authorize apps and APIs with any identity provider running on any stack any device or cloud. It is simple to integrate and allows users to just sign up with a Google account if they wish.
Amazon Simple Storage Service (Amazon S3) is an object storage service that offers industry-leading scalability, data availability, security, and performance. This means customers of all sizes and industries can use it to store and protect any amount of data for a range of use cases, such as websites, mobile applications, backup and restore, archive, enterprise applications, IoT devices, and big data analytics.
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:
* REACT_APP_REDIRECT_URI_BASE = "http://localhost:3000"
* REACT_APP_CLIENT_ID = "7zLELHA3Jyrt7O5M561HgBg3EjRsoT5K"
* REACT_APP_BASE_URL = "https://kansha-staging.herokuapp.com"
* REACT_APP_AUTH_DOMAIN = "kansha.auth0.com"
We used Jest to build our testing for Kansha.
- Clone the repo to your drive
- cd into the kansha/kansha-fe/react-app
- type yarn to install the dependencies (if you use npm, it would be npm install)
* yarn start - starts the local build of the app
* yarn test - runs the created tests on the build
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. .