I did the following: 1) Added an About page which includes a breakdown of API endpoint information; 2) Adjusted Clint's code to include a description column for trails; 3) Adjusted Clint's POST code to render a list of trails after submitting a trail to the database, and output a message above (based on the success or failure of whether a trail was POSTed); 4) Adjusted Clint's SQL to order the trails by name - I thought it'd look good alphabetical; 5) Changed the trail web form code so that the names of each field correspond with Clint's database column names; 6) Created a trail view page, which iterates through the trail dict that Clint pulled from the database; 7) Played around with the stylesheet some (need to put it in its own file but I'm lazy).
I did the following: 1) Added an About page which includes a breakdown of API endpoint information; 2) Adjusted Clint's code to include a description column for trails; 3) Adjusted Clint's POST code to render a list of trails after submitting a trail to the database, and output a message above (based on the success or failure of whether a trail was POSTed); 4) Adjusted Clint's SQL to order the trails by name - I thought it'd look good alphabetical; 5) Changed the trail web form code so that the names of each field correspond with Clint's database column names; 6) Created a trail view page, which iterates through the trail dict that Clint pulled from the database; 7) Played around with the stylesheet some (need to put it in its own file but I'm lazy).