https://github.com/rusiruavb/conference-management-frontend

Frontend React application for conference application.
https://github.com/rusiruavb/conference-management-frontend

firebase promise-middleware react redux

Last synced: 3 months ago
JSON representation

Frontend React application for conference application.

• Host: GitHub
• URL: https://github.com/rusiruavb/conference-management-frontend
• Owner: rusiruavb
• License: mit
• Created: 2021-06-14T06:12:39.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2021-06-30T17:15:55.000Z (about 5 years ago)
• Last Synced: 2025-01-16T00:22:40.588Z (over 1 year ago)
• Topics: firebase, promise-middleware, react, redux
• Homepage: https://af-conference-stg.herokuapp.com/
• Size: 473 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
## Conference Management System - Frontend V 1.0

### Deployed Links

Production Deployement - https://af-conference-prd.herokuapp.com/ \

Staging Deployement - https://af-conference-stg.herokuapp.com/

### This management system project is for Application Framework(AF) module.

This is frontend application for conference management system. Technology that we are using to implement this application is **React**. And we use **Redux** for state management in this project.

### How to contribute

1. Fork the project into your local GitHub profile.:fork_and_knife:

2. Clone that project into your computer.:rocket:

3. Assign a issue from the **issue** tab. - *All the issues are the **features** of the API.*

4. Create new brach and called it with the respected feature.:seedling:

> For example: Issue - Customer profile section

> Then you should name your brach like this.

> `feature/customer-profile`

> Brach name always should be simple letters.

5. Do your modifications to the code.👨‍💻

6. Commit changes to your local repository.💬

7. Create a pull request to upstream repository.:hand:

> Before create the pull request, please chack if there are merge conflicts in your code. If there are not conflicts, then create the **Pull Request(PR)**

8. Then you have to assign one or more team members to review your code.:eyes:

> After reviewing process are done and your code is ready to merge, one of our organization member will merge your changes to the **master** branch.