Web Programming with html5, css, and JavaScript

Paradise in Parkville!

Welcome to Parkville – Party Town, USA.
• Continuation code for phrasing elements whose code is too long for one line:
■
If a phrasing element cannot fit on one line, you should insert newlines at logical 
breaking points. In the following examples, the 
a
element cannot fit on one line so 
newline insertions are required. In the “bad” example, newlines are inserted after 
href=
and 
onclick=
. Those are poor breaking points because the 
href
and 
onclick
assignments are split. In the “good” example, newlines are inserted after 
website 
and 
after the 
a
start tag. Those are good breaking points because they help prevent the 
href
and 
onclick
assignments from being split.
637
body
Container

---

Bad:
For additional information on our ICS
program, check out this website - "http://www.park.edu/csis" onclick=
"return confirm('Are you sure?');">
http://www.park.edu/csis
Good:
For additional information on our ICS program,
check out this website –
onclick="return confirm('Are you sure?');">
http://www.park.edu/csis
■
Note that the 
a
element’s continuation lines are aligned with the 
a
element’s first line; 
that is, they are not indented. That’s because the 
a
element is within a 
p
container. If the 
a
element were in a container (like nav) that was not supposed to look like a paragraph, 
then you should indent like this: 
onclick="return confirm('Are you sure?');">
3. Lists:
• Normally, you should nest 
ol
, 
ul
, 
dl
, and 
li
elements as follows:

1. 
   Morning
   
   
   
   • Wake up
   
   
   • Go to school
   
   
   
   


2. 
   Afternoon
   
   
   
   • Kick back and relax.
   
   
   • 
     Lecture period – not much prepared so allow students to
     ask questions and surf the Internet for cool web pages.
     
   
   
   • Go home and watch TV.
   
   
   
   


3. Evening