Sign In page

• takes username and password,
• uses axios to authenticate what is submitted (by communicating with backend)
• sends user to one of 4 role pages (customer, driver, employee) --- the number of role pages may be subject change using API
• has route to signup page

Sign Up page

• This is a data entry form - inputs first name, last name, email, password, phone number, street address, city , state, and home address. (this may be revised based on the information we actual need)
• sends data to database using API
• routes back to sign in page

Please comment or edit if any change or clarification is needed for the above goals because doing so will help clarify for everyone else how each part fits together or distinction of tasks to be done

The first page a user should see when they go to our page is the sign in page/ sign up button. So the first thing we will need to do to make the sign up/sign in page is to create the react foundation, then use react router to create a route to the index page. Then we need to make the html/ react components, and link the database to our application. I will be working on the database to the application connection.

Based on the login type (employee or customer) we need to render different components. The body of the homepage will be the same for everybody, but the navbar will not.
For customer login, in the navbar we need

1. Link to profile
2. Send a package
3. All packages -> all packages for customer

For employee login, use the data returned from the api to determine which employee type it is.
For front clerk in navbar we need. (emp type 1)

1. Link to profile
2. All packages -> view all packages in the system + status (will be able to process them)

For the driver, (emp type 2)

1. Link to profile
2. All packages -> view all packages in system -> add them to current delivery (change status)
3. Delivery -> shows all packages to be delivered + can be mark as delivered

For the manager (emp type 3)

1. Link to profile
2. Employee overview -> view all employee and some stats + able to add (employee signup) and remove (fire or quit)
3. All packages -> same as other two but full control
4. Reports -> will link to page where different reports can be generated. ( we can have more links in it)

while the Sign Up page is a data entry form that submits customer data we need forms that submit package data and employee data, then we need reports and queries for the packages, customer and employee data.
this is what the next part of the project it, we need the front end forms to send the data via the api to the backend and queries that send the results back to view the data as a report of in some other way.

the following pages for the roles can be created on the front end and will be through the nav bar. If it is easier you can split these pages then route them later

Customer
Profile page for customers // also called Home Page- that modify their individual customer data and view it--data entry form
Package page for customer - input package for themselves -- data entry form
Package status - all packages sent and received by individual customer

Employee
Process page - we have a button that queries all new packages that haven't been processed for the day and employee presses button, then sends data to backend where it says employee processed x packages -- This idea is work in progress
Employee page - can get reports on customer data and package data -- data reports and query's
Manager

Manager report page - report on employee data
manager employee creation page - can modify and create new employees data -- data entry form and data query

Discussion:
post offices and locations to send to, arrivals and cost change, if you deliver to post office then its cheaper and faster or it costs more and takes longer to deliver to a location