Carnival of HTML: Flair
- The basic web page
- Carnival of HTML
- Extra Credit
- Style Sheets
- The purpose of HTML is to structure your document. Resist the urge to use it for layout. Layout is device-specific, but structure is universal. A well-structured document is easier for new, unanticipated technologies to read, easier for you to maintain, and easier for you to vary the layout on.
- Flair: Images
- Our web page is looking a lot more like a web page now than it did when we started, but no movie review would be complete without stills from the movie. There are four images in the workshop folder, and we’ll add each of them to the review. The first image will be a screen capture of the main character looking at her reflection. Directly underneath the “<div id="review">”, add the image and a paragraph to caption it:
- Flair: Tables
- Another thing that might be useful for readers is a couple of tables of information about the DVD and the movie. Let’s add a list of DVD features. (This table, and the other tables we’ll create, are in the “tables” folder of the resources folder.) Add this below the movie quote at the top of the page, and above the “There are places in this world” paragraph.
- Flair: Lists
- If you pulled the director and writer out of review.txt, you’ll notice that there was a third row I didn’t use. That row contained a bulleted list. Go ahead and add it to the movie table as a third row:
- More about URLs
- That list of links we added in the previous section aren’t actually linked. Here are the links for each item. Add them with an “a” tag.
- Deleted and inserted text
- If you’re writing news stories or blog postings, you’ll often amend your text later: you’ll discover that something you wrote was incorrect or misleading, and you’ll want to correct your text. But it’s bad form to change a news posting or a blog posting without warning; these types of pages are assumed to exist at a specific moment in time. HTML has a special tag for marking text that’s been…
- Entities (special characters)
- In the past, any special characters needed to be specially encoded. It isn’t as necessary today, as long as you specify a character set and make sure that you always stick with that character set. But entity codes can still be useful if you’re working with multiple data sources of unknown character set, or you have multiple people working on the same document and you’re worried that they won’t all use the same character set.
