We are nearing the end of the project in total and it has been a very productive month for the team and have made great strides in understanding the svelte documentation and implementation.
The back-end team has successfully retrieved the client and order data from the backend MongoDB database and have used that information to set up a JSON structure in which the front-end can team can use to seamlessly display the data for each driver. To form the JSON structure, the back-end team took the addresses in a given route and called the Google Maps API to return to the back-end the correct order route. Using that order, we created a navigation URL for the driver, which is a part of the JSON structure that is returned to the front-end team.
The front-end team split up into two parts, one side being displaying vehicle data and the other side being displaying the routes taken by the delivery driver based on the vehicle. On the routes, the front-end team has been working on how to display vehicle and order information on the pageZoneID page but had encountered some issues, particularly the binding aspect with the checkboxes, but found the solution by using the HTML table element and got the checkboxes working. Now the front-end team responsible for the vehicle and order information is working on just making the tables and page look cleaner and user-friendly but because the HTML table element has bad CSS, we are planning on using the existing svelte grid component to better display the data. For the routes side, we were able to finish the idea and execute the routes page, the routes overview page, and the routes detail page and were able to connect the three pages together for a cohesive, user-friendly interface. We made it to where when the user clicks on the vehicle information, it would display the vehicle type, capacity, and vehicle ID. From there, it would show the organization ID and addresses of the stops made and is then given an order code, which then leads to a clickable google maps link, which generates the route. The front-end team responsible for the routes aspect is now working on making the page look neat and is fixing some technical components.