Boys & Girls Club of Conejo Tracker Emotion Tracker

You can find the deployed project here.

Contributors

Alexander Besse	Donavyn Haley	Jordan Hanson	Jamie Jenks	Sebastian Mendoza	Iaroslav Mokroguz	Jacob Olness	Leah Tabush
TPL	Front-End Engineer	Back-End Engineer	Back-End Engineer	Co-Design Lead	Front-End Engineer	Back-End Engineer	Co-Design Lead

• Fork and clone the repo to install it as your own remote.
  • note please be sure to set your remote for this repo to point to your Labs Team Front End Repository.
• 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.

Key Features

• Batch or individual generation of printable ID cards with QR Codes
• Batch or individual import of staff, programs and members parsed from .csv files

Front end deployed to AWS

Back end built using:

Java Spring

• 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

APIs

Okta Authentication

The sign-in experience is one of the most important user experiences any app developer needs to consider. To provide a seamless and attractive, yet secure authentication experience is not a trivial task. Typically, the sign-in logic accompanies other features such as password reset and registration. More importantly, enhanced security in the form of strong and adaptive authentication during the sign-in process is often critical to many implementations.

Okta provides many options for developers to handle the authentication experience that are built on top of the underlying feature set in Okta. Password policies, strong and adaptive authentication policies, and password reset workflow can all be configured easily in the administrator UI. Many of these policies can also be controlled through Okta's API.

Okta provides OAuth 2.0 and OpenID Connect implementations, the Sign-In Widget, the Auth JS SDK, and the Authentication API.

Installation Instructions

npm i

Other Scripts

* 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

Contributing

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.

Issue/Bug Request

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.

Feature Requests

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.

Pull Requests

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.

Pull Request Guidelines

• 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.

Documentation

See [Backend Documentation](🚫link to your backend API SWAGGER DOCS here) for details on the backend of our project.