Submit the URL to your project's repository on Github.com, for example https://github.com/yourusername/p1.
Like the weekly assignments, late projects will not earn the 5 points reserved for “timeliness”; late work is only accepted until +7 days after the due date.
Use a minimal amount of CSS to cleanly style the page; it does not have to be a work of art, but I do want you to demonstrate you are comfortable with CSS. You can, but don't have to, use CSS tools like Bootstrap, SASS, etc.
Do not copy the HTML/CSS directly from the above provided example.
You should use modern and semantic HTML; running your site's production URL through the w3 validator should produce not produce any errors or warnings. (If you disagree with any of the warnings the validator is showing, email me ahead of time so we can confer on whether ignoring the warning is acceptable).
Must be powered by PHP.
Should randomly pull from a selection of at least 3 different quotes each page load.
The purpose of this requirement is to a) confirm your servers can run PHP, and b) give you an opportunity to practice the initial PHP info assigned as readings in your Week 2 assignment.
File must be named README.md and placed in the root of your application.
Use proper Markdown syntax.
All links must be clickable.
For outside resources, do not include course notes or examples, but do include any/all of the following:
Specific forum posts (e.g. stackoverflow) that provided information you utilized in your code
Sources for images that you did not create
Outside resources such as CSS frameworks, Google fonts, etc.
Anything else (if in doubt, cite!)
Your application should be accessible via http://p1.yourdomain.com.
You can name your repository on Github anything you want, but I suggest p1.
Application should be in its own Github repository (do not put multiple projects in the same repo).
Repository should be public; if you have an exception that requires a private repository, please email me.
Your application on production should match what is in your repository; i.e. do not make direct edits to your production code bypassing version control.
Interface and design should be clear and organized.
There should be no accessibility/design issues (e.g. super small font, yellow text on a white background, etc.).
Site should load in <= 2 seconds.
Text should use correct grammar, spelling, and punctuation.
Any graphics/images should be of good quality— there should be no pixelated, blurry, distorted, or otherwise low quality images.
Layout and interface should look presentable on laptop/desktop resolution (responsive design is welcome, but not required).
Code should be organized, tidy, and easy to follow.
Code should be consistently and accurately indented.
Any extraneous code (including old, commented-out code) should be removed before completion.
CSS can be included externally (preferred) or embedded; it can not be included inline.
Proper HTML structure should be used.
For most of your projects in this course, you're encouraged to post questions in the Issues forum so we can collaboratively help one another and learn from the troubleshooting process. The one exception to this is in regards to the PHP/random quote requirements of this project - do not post about that specifically, as it will “spoil” the answer for other students. If you have questions about this code, contact me directly.
Follow any/all other best practices not explicitly mentioned above but discussed in lecture/notes.