For steps on how to work with this repository please see here
You can find the deployed project at VBB-Deployment.
| Michelle Hey | Amado Guerrero | Ignacio Ocampo | Amy Barger | John Oblenda | Mustafa Hassan |
|---|---|---|---|---|---|
 |
|||||
 |
|
|
|
|
|
- run:
npm installto download all dependencies. - run:
npm startto start your local development server.
When using Okta for authentication, the app will need to run locally on port 3000.
- Is a mobile-first design.
- Private routes protect all resources that are not authenticated.
- Headmaster dashboard and Admin dashboard
- Headmaster profile and edit.
- Admin library view, edit, and delete.
- Headmaster mentee Create, Read, Edit, and Delete.
Back end built using:
- Json Web Server
- Json Web Token (Authentication)
- Faker.js
- Mock back-end with realistic data generated by Faker.js.
- Mock back-end with basic JWT authentication.
- BASEURL/login
- BASEURL/library
- BASEURL/village
- BASEURL/school
- BASEURL/mentee
- BASEURL/headmaster
1 - npm install
2 - Create .env file with 'REACT_APP_BASE_URL = YourURL' and 'REACT_APP_PORT = 3000
3 - That is all
* build - creates a build of the application
* start - starts the production server after a build is created
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.
Commit message lines are capped at 100 characters. Use the types below when staging your commits.
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, styling, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug or adds a feature
- perf: A code change which improves performance
- test: Adding missing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
See Backend Documentation for details on the backend of our project. More personal team notes, incl updated roadmaps: https://www.notion.so/Labs-1-b3ff11cad50d4576a3e7bcf2d7269652