RunCreator Project Summary
1) Explain the topic and purpose of your site.
The purpose of my website is to provide access to the custom routes
entered onto RunCreator, an iOS app I'm designing in another class.
Users are able to add their own routes, or just read and add reviews to
existing ones. Meanwhile, admins can create, update, and delete any
reviews that they wish to.
2) Provide instructions on how your site works (admin credentials,
password-protected pages, etc.).
Admin Permissions Credentials
- Username: admin
- Password: admin
- Username: student
- Password: student
- Delete.php, Add_Route.php, Add_Review.php, Edit_Form.php, and MyReviews.php are password-protected pages to ensure that users are logged in before they can access and edit data.
3) Explain the source of your data.
Data about the custom routes and their respective reviews have been
stored in the database. This includes standard information about runs
such as skill level, route name, distance, elevation gain, surface type,
and city. I used various sources for my data, including:
Map My Run,
Google Maps,
and
Run Keeper. On top of that, to implement user permissions and reviews on the
website, I had to store information about users, access levels, and
reviews.
4) Attach Database Diagram (screenshot or link to the PDF file).
5) Describe extras used. If API used, provide link to API documentation.
Frontend ↔ Backend AJAX ( JavaScript ↔ PHP )
- Used on the Search Routes data table
- Allows user to search via filters and receive results right away
-
General User
- Can create, read, update, and delete on their own reviews only
- Can create and read routes
-
Admin
- Can create, read, update, and delete on both their own and others' reviews
- Can create and read routes
- Used on the Search Routes data table to help with legibility
- Used on the My Reviews data table to help with legibility