How much for this? I have the some html done and the whole database done on mysql. You need to code the php part
Final Project Final Project Submission Upload to itpwebdev.com by 11:59pm on Wednesday, 12/08. Do not modify any files after the deadline. Late Submission Late submissions are accepted until 11:59pm on Friday, 12/10 with 10% per day penalty. No submissions are accepted afterward. You must email your instructor once your late project is uploaded, otherwise you will receive a zero (0) score. Overview For the final project you will create a database-driven website on a topic of your choice. You must design your own database, but you may use data from other sources. Your website needs to work on itpwebdev.com. Past Examples: ● Food Snobs ● Endangered Animal List ● The Movie DB ● Dive Finder ● TV Show Rating Requirements Project Summary 1. This can be a linked PDF document or separate HTML page (not counted toward page count requirement). 2. Explain the topic and purpose of your site. 3. Provide instructions on how your site works (admin credentials, password-protected pages, etc.). 4. Explain the source of your data. 1 of 5 © 2021 Zune Nguyen http://50.28.106.64/~projects/itp300/food_snobs/site/login.php http://50.28.106.64/~projects/itp300/animal/animal_search.php http://50.28.106.64/~projects/itp300/movie_db/ http://50.28.106.64/~projects/itp300/divefinder/main.php http://50.28.106.64/~projects/itp300/tv_rating/search.php 5. Attach Database Diagram (screenshot or link to the PDF file). 6. Describe extras used. a. If API used, provide link to API documentation. 7. Describe CSS frameworks or templates used. Provide links to original files. Project Database 1. Design and normalize your own database. a. Do not use song, DVD, or football databases from lectures, assignments, or labs. b. Not adhering to this will result in a zero (0) score for the final project. 2. Populate the database with sufficient data. a. I.e. if implementing pagination, database needs to have enough records to show few pages. b. You can use data from other sources. 3. At least three (3) tables and two (2) table relationships. 2 of 5 © 2021 Zune Nguyen Project Website 1. All config and image files (if any) organized within separate folders (for example config and img). 2. CRUD functionality: a. Site needs to provide functionality to Create, Read, Update and Delete records from the database. 3. Original layout. a. Do not use class examples, labs, or assignments with modified content. b. You may use CSS frameworks (Bootstrap, etc.) or templates, but you must credit them in your project summary. c. Not adhering to this will result in a zero (0) score for the final project. 4. Clean and readable design. 5. Design consistency: a. All pages (including error pages) should have similar structure (header, navigation, footer, etc.). 6. Clear purpose and topic. 7. Substantial and real content beyond database output. a. Introductory pages, narrative text, etc. b. No lorem ipsum or image-fillers. c. Content should cover the topic in fair detail. 8. Good balance between text and graphics: a. I.e. do not create a text-only or an image-only website. 9. At least three (3) distinct pages or sections (single-page sites). a. “Coming Soon” pages do not count. b. Project Summary page does not count. c. If creating a single-page site, each section needs to be clearly marked and have substantial content that could be split into a separate page. 3 of 5 © 2021 Zune Nguyen 10. Navigation or menu used to navigate to different pages or sections. a. Needs to be present and consistent on all pages. 11. Intuitive User Interface (UI): a. Clickable elements should be clearly marked, b. All links take users somewhere, even if it’s Coming Soon page (no dead links), c. Etc. 12. External CSS used for all shared styling. a. Styles for specific pages should be in Internal CSS or separate CSS file linked on that page only. 13. All code passes validation: a. HTML: https://validator.w3.org/#validate_by_input. b. External CSS (if any): https://jigsaw.w3.org/css-validator/#validate_by_input. c. Validate code after PHP output (right-click → View Source). Project Extras At least Three (3) from following extras: 1. SQL Aggregate Functions, 2. Pagination, 3. Sessions / Cookies, 4. Different User Permission Levels: a. At least three (3) levels: general (everyone), registered users, admin (privileged) users. b. For example: i. Everyone is able to browse the database. ii. Registered users can create new records (blog posts, comments, etc). Registered users only able to edit or delete their own records. 4 of 5 © 2021 Zune Nguyen https://validator.w3.org/#validate_by_input https://jigsaw.w3.org/css-validator/#validate_by_input iii. Admins able to perform CRUD on entire database. 5. PHP Mail Function with HTML-formatted Email, 6. File Upload, 7. Frontend ↔ Backend AJAX ( JavaScript ↔ PHP ), 8. REST (Server-Side) API – counts as two (2): a. Different from the API used in class, 9. Many-to-many table relationship – counts as two (2), 10. Other – consult the instructor. Submission 1. Create final_project directory on your itpwebdev account within public_html directory. 2. Upload all project files to final_project directory. a. Link the project home page on your Student Page. 3. Upload project summary to to final_project directory. a. Link the project summary on your Student Page. 5 of 5 © 2021 Zune Nguyen