Skip to content

Latest commit

 

History

History
83 lines (52 loc) · 7 KB

README.md

File metadata and controls

83 lines (52 loc) · 7 KB
Raw

Apollo

You can find the deployed project at a.apollox.dev.

Check out the demo here.

Contributors

Jonathan Hsu Hunter Stevens Student 3 Student 4 Student 5


MIT React code style: prettier

  • 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

  • create topics
  • submit survey requests
  • review and reply to team member survey responses
  • notification system for sending out surveys
  • customizable topic creation wizard that includes custom questions & preset templates

Front end deployed to AWS Amplify

Back end built using:

  • Node
  • PostgresQL
  • Heroku

APIs

Okta

Custom API is built and hosted on Heroku. Includes functional endpoints for all CRUD operations. Check out the Back-End repository for more information.

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 Labs26-Apollo-BE-TeamA for details on the backend of our project.