Just brainstorming.
The user upon visiting the site should see the table for "Upcoming Rides" with a button somewhere for "Add a New Ride", and below it, the table for "Pending Requests" with the a button somewhere for "Add a request". This will make the design more ready for mobile-responsive design, with only one vertical column going down the page.
Since there is only one data model, you can pass all the fields you'd like the user to see when he clicks on the button, and render only the form fields needed for that route. That reduces all the different html form code to one reusable template, and the different python routes to just "Add" or "Edit" rides, rendering only the parts of the form that you want the user to see/be editable
Just brainstorming.
The user upon visiting the site should see the table for "Upcoming Rides" with a button somewhere for "Add a New Ride", and below it, the table for "Pending Requests" with the a button somewhere for "Add a request". This will make the design more ready for mobile-responsive design, with only one vertical column going down the page.
Since there is only one data model, you can pass all the fields you'd like the user to see when he clicks on the button, and render only the form fields needed for that route. That reduces all the different html form code to one reusable template, and the different python routes to just "Add" or "Edit" rides, rendering only the parts of the form that you want the user to see/be editable