Programming Project Part 2

Class Project: PHP Website (But for real this time)

Project Plan Part 2

• Very similar to part one, this must be a GitHub gist that is professionally written. It must include your name, CS1520, and email address.
• Make use of GitHub markdown, I will not accept a run-on plain text file (look into GitHub Markdown if you need a hand)
• Your plan should include the following:
• What are you going to improve on from part one?
• Are you going to improve your project from part one? Or are you going to do something completely different?
• Using a frontend framework? Which one?
• Also, anything else you think may be important to have added to the plan. We just want to cover all our bases.
• A list of ANY questions you may have about your idea or the project in general. This is the best time to hammer out any of the smaller details.
• If you were thinking about using some advanced topics, like MVC or anything like that, let me know as this would be the time to do it.

Requirements

• Organized file tree
• Document stating what you changed/fixed/implemented vs. Part 1 and what you've learned since then. Be thorough and provide details. Should be about a page long.
• There must be some Database interactivity
• Better use of JS, perhaps using an API? (We'll be going over some of them, but don't hesitate to research on your own)
• Programming Requirements:
• The entire site must be in PHP this time.
• Use of variables, includes, arrays, functions, file reading etc.
• When should I use [requirement]?
• Ex. If you have a collection of links that have text and hrefs that need to be displayed, store them in an array and correctly loop through them where you want them to display
• Ex. Repeating some PHP more than once in a PHP block? Store it in a variable.
• Use PHP partials to keep the code clean and organized, no need to repeat yourself.
• There are no hard requirements for what PHP to use and when. The best approach would be to use as many of the topics covered in class (appropriately) as necessary to make the site work and prove your ability
• If you are unsure on what to use or when/how to use it, please reach out to me or a TA
• PLEASE DO NOT HESITATE TO ASK IF YOU NEED CLARIFICATION OR HELP WITH ANYTHING. I CANNOT STRESS THIS ENOUGH
• Grading Rubric will be the same as for part one.

Programming Project Part 1

Class Project: PHP Website

Project Plan

• Basically, this will act as a roadmap for both you and me, so we can have a clear outline of what our projects will entail. Nobody wants to program themseleves into a corner and wind up having to scrap hours of work if they can help it. You can be as verbose as you like in this, but I would like to see at least a couple sentences on each point.
• Your plan should include the following:
• What technology are you going to be using? (PHP for the most part, but it never hurts to outline everything you are going to use.)
• What is your site going to be about? Self promotion? Promotion of something else? Etc. The worst that can happen is that I will suggest another route.
• Using a frontend framework? Which one?
• Also, anything else you think may be important to have added to the plan. We just want to cover all our bases.
• A list of ANY questions you may have about your idea or the project in general. This is the best time to hammer out any of the smaller details.
• OPTIONAL: Do you want to use some advanced topics? Such as MVC structure, or using PHP as a backend for some other frontend framework, etc. This will not entitle you to different or better grading. You will still be accountable for all the same requirements. I am well enough equipped to review, grade and comment on most implementations.
• Create a GitHub Gist and email me the link to it. If you would like further direction on anything, let me know. Let's have fun and demonstrate what we've learned so far!
• NOTE: Since the class project is split up into two milestones (part one due halfway through, part two due at the end), this is really only in relation to the first part of this project. All the requirements will be the same for part two, but just implementing features based on what we will learn during the second half of the class.

Requirements

• Organized file tree
• One page or multi page layout. Minimum of three sections/pages
• Page Examples:
• About, contact, resume/CV, fan page about your favorite rapper or super hero, anything is fine. Just remember though, you may want to keep it professional in the event you want to use this as your actual personal site down the road.
• You may use a frontend framework, such as Bootstrap or Foundation. You may also use a template, all I ask is that you do not use it as it comes. Add your own layer of style on top of what is included.
• All pages (views and includes, etc) should be written in PHP, at least for this first part of the project
• One component/page of your site should be a contact form, I would prefer this to submit to a database, but if you want to defer the database and have it email you or write to a text file, that is ok too.
• Programming Requirements:
• Intelligent use of topics covered in class so far. Such as:
• Use of variables, includes, arrays, functions, file reading etc.
• When should I use [requirement]?
• Ex. If you have a collection of links that have text and hrefs that need to be displayed, store them in an array and correctly loop through them where you want them to display
• Ex. Repeating some PHP more than once in a PHP block? Store it in a variable.
• Ex. Don't want to write your header and footer on each page for a multi page approach? Use an include file. Similarly, if you have a function that you will use over and over, that should also go into an include file.
• There are no hard requirements for what PHP to use and when. The best approach would be to use as many of the topics covered in class (appropriately) as necessary to make the site work and prove your ability
• If you are unsure on what to use or when/how to use it, please reach out to me or a TA
• PLEASE DO NOT HESITATE TO ASK IF YOU NEED CLARIFICATION OR HELP WITH ANYTHING. I CANNOT STRESS THIS ENOUGH

Submission Guidelines

• Submissions must be through GitHub
• Remember to make a copy of the project folder containing the file tree. You will need an unaltered version of this to hand in alongside your part two.

Grading Rubric

• I'm going to be more attentive to the way you write your code for this project. In the event that it will become public facing in the future, it is important for you to have well written, clean semantic code. Myself or the TAs will be available to help you with this as well.
• Clean, readable, sematic code, organized assets and folders, etc.: 15%
• Intelligent implementation of requirements: 45%
• Usability (navigation works, the site loads, assests aren't broken or unavilable, it's not too confusing to use, looks ok etc.): 25%
• Submission guidelines are adhered to: 15%