Problem: Homepage
tl;dr
Build a simple homepage using HTML and CSS.
Academic Honesty
This course’s philosophy on academic honesty is best stated as "be reasonable." The course recognizes that interactions with classmates and others can facilitate mastery of the course’s material. However, there remains a line between enlisting the help of another and submitting the work of another. This policy characterizes both sides of that line.
The essence of all work that you submit to this course must be your own. Collaboration on problems is not permitted (unless explicitly stated otherwise) except to the extent that you may ask classmates and others for help so long as that help does not reduce to another doing your work for you. Generally speaking, when asking for help, you may show your code or writing to others, but you may not view theirs, so long as you and they respect this policy’s other constraints. Collaboration on quizzes and tests is not permitted at all. Collaboration on the final project is permitted to the extent prescribed by its specification.
Below are rules of thumb that (inexhaustively) characterize acts that the course considers reasonable and not reasonable. If in doubt as to whether some act is reasonable, do not commit it until you solicit and receive approval in writing from your instructor. If a violation of this policy is suspected and confirmed, your instructor reserves the right to impose local sanctions on top of any disciplinary outcome that may include an unsatisfactory or failing grade for work submitted or for the course itself.
Reasonable
-
Communicating with classmates about problems in English (or some other spoken language).
-
Discussing the course’s material with others in order to understand it better.
-
Helping a classmate identify a bug in his or her code, such as by viewing, compiling, or running his or her code, even on your own computer.
-
Incorporating snippets of code that you find online or elsewhere into your own code, provided that those snippets are not themselves solutions to assigned problems and that you cite the snippets' origins.
-
Reviewing past years' quizzes, tests, and solutions thereto.
-
Sending or showing code that you’ve written to someone, possibly a classmate, so that he or she might help you identify and fix a bug.
-
Sharing snippets of your own solutions to problems online so that others might help you identify and fix a bug or other issue.
-
Turning to the web or elsewhere for instruction beyond the course’s own, for references, and for solutions to technical difficulties, but not for outright solutions to problems or your own final project.
-
Whiteboarding solutions to problems with others using diagrams or pseudocode but not actual code.
-
Working with (and even paying) a tutor to help you with the course, provided the tutor does not do your work for you.
Not Reasonable
-
Accessing a solution to some problem prior to (re-)submitting your own.
-
Asking a classmate to see his or her solution to a problem before (re-)submitting your own.
-
Decompiling, deobfuscating, or disassembling the staff’s solutions to problems.
-
Failing to cite (as with comments) the origins of code, writing, or techniques that you discover outside of the course’s own lessons and integrate into your own work, even while respecting this policy’s other constraints.
-
Giving or showing to a classmate a solution to a problem when it is he or she, and not you, who is struggling to solve it.
-
Looking at another individual’s work during a quiz or test.
-
Paying or offering to pay an individual for work that you may submit as (part of) your own.
-
Providing or making available solutions to problems to individuals who might take this course in the future.
-
Searching for, soliciting, or viewing a quiz’s questions or answers prior to taking the quiz.
-
Searching for or soliciting outright solutions to problems online or elsewhere.
-
Splitting a problem’s workload with another individual and combining your work (unless explicitly authorized by the problem itself).
-
Submitting (after possibly modifying) the work of another individual beyond allowed snippets.
-
Submitting the same or similar work to this course that you have submitted or will submit to another.
-
Using resources during a quiz beyond those explicitly allowed in the quiz’s instructions.
-
Viewing another’s solution to a problem and basing your own solution on it.
Background
The internet has enabled incredible things: we can use a search engine to research anything imaginable, communicate with friends and family members around the globe, play games, take courses, and so much more. But it turns out that nearly all pages we may visit are built on three core languages, each of which serves a slightly different purpose:
-
HTML, or HyperText Markup Language, which is used to describe the content of websites;
-
CSS, Cascading Style Sheets, which is used to describe the aesthetics of websites; and
-
JavaScript, which is used to make websites interactive and dynamic.
Focusing on just the first two of those three languages for now, create a simple homepage that introduces yourself, your favorite hobby or extracurricular, or anything else of interest to you.
Getting Started
Here’s how to download this problem’s "distribution code" (i.e., starter code) into your own CS50 IDE. Log into CS50 IDE and then, in a terminal window, execute each of the below.
-
Execute
cd
to ensure that you’re in~/
(i.e., your home directory, aka~
). -
Execute
mkdir chapter5
to make (i.e., create) a directory calledchapter5
in your home directory. -
Execute
cd chapter5
to change into (i.e., open) that directory. -
Execute
wget http://cdn.cs50.net/ap/2019/problems/homepage/homepage.zip
to download a (compressed) ZIP file with this problem’s distribution. -
Execute
unzip homepage.zip
to uncompress that file. -
Execute
rm homepage.zip
followed byyes
ory
to delete that ZIP file. -
Execute
ls
. You should see a directory calledhomepage
, which was inside of that ZIP file. -
Execute
cd homepage
to change into that directory. -
Execute
ls
. You should see this problem’s distribution code, includingindex.html
andstyles.css
. -
You can immediately start a server to view the site by typing
http-server
in the terminal window and clicking on the link that appears, which should be of the form
https://UNIQUEID-ide.cs50.xyz:8080
, whereUNIQUEID
is a long, alphanumeric slug specific to your account.
Specification
Implement in your homepage
directory a website that must:
-
Contain at least four different
.html
pages, at least one of which isindex.html
(the main page of your website), and it should be possible to get from any page on your website to any other page by following one or more hyperlinks. -
Use at least ten (10) distinct HTML tags besides
<html>
,<head>
,<body>
, and<title>
. Using some tag (e.g.,<p>
) multiple times still counts as just one (1) of those ten! -
Integrate one or more features from Bootstrap into your site. Bootstrap is a popular library (that comes with lots of CSS classes and more) via which you can beautify your site. See Bootstrap’s documentation to get started. To add Bootstrap to your site, it suffices to include
<link href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" rel="stylesheet">
in your pages'
<head>
, below which can<link href="styles.css" rel="stylesheet">
containing your own CSS.
-
Have at least one stylesheet file of your own creation,
styles.css
, which uses at least five (5) different CSS selectors (e.g. tag (example
), class (.example
), or ID (#example
)), and within which you use a total of at least five (5) different CSS properties, such asfont-size
, ormargin
; and -
Ensure that your site looks nice on browsers both on mobile devices as well as laptops and desktops.
-
No need to include any JavaScript on your site for this problem set, unless so inclined!
Testing
If you want to view how your site looks while you work on it, there are two options:
-
Within CS50 IDE, navigate to your
homepage
directory (remember how?) and then executehttp-server
-
Within CS50 IDE, right-click (or Ctrl+click, on a Mac) on the
homepage
directory in the file tree at left. From the options that appear, select Serve, which should open a new tab in your browser (it may take a second or two) with your site therein.
In either case, you’ll be brought to a URL of the form
https://UNIQUEID-ide.cs50.xyz:XXXX
Where UNIQUEID
is a long, alphanumeric slug specific to your account, and XXXX
is either 8080
or 8081
, those referring to the port number on which your web server is listening for requests (instead of the default 80
or 443
for HTTP and HTTPS requests, respectively). At that address, you’ll see a listing of all of the files in your homepage
directory, and from there can navigate to any HTML page you’ve created.
Recall also that by opening Developer Tools in Google Chrome, you can simulate visiting your page on a mobile device by clicking the phone-shaped icon to the left of Elements in the developer tools window, or, once the Developer Tools tab has already been opened, by typing Ctrl
+Shift
+M
on a PC or Cmd
+Shift
+M
on a Mac, rather than needing to visit your site on a mobile device separately!
Hints
For fairly comprehensive guides on the languages introduced in this problem, check out the documentation for each on W3Schools.
How to Submit
Step 1 of 2
Head back to the ide.cs50.io[CS50 IDE] and ensure that index.html
is in ~/chapter5/homepage
, as with:
cd ~/chapter5/homepage
ls
If index.html
is not in ~/chapter5/homepage
, move it into that directory, as via mv
(or via CS50 IDE’s lefthand file browser).
Step 2 of 2
-
To submit
homepage
, executecd ~/chapter5/homepage submit50 cs50/problems/2019/ap/homepage
inputting your GitHub username and GitHub password as prompted.
If you run into any trouble, email sysadmins@cs50.harvard.edu!
You may resubmit any problem as many times as you’d like before the deadline.
Your submission should be graded for correctness within 2 minutes, at which point your score will appear at submit.cs50.io!
This was Homepage.