HWG-Basics List FAQ

Table of Contents

1. Introduction
2. Validation, what is it and why would I want to use it?
3. Cascading Style Sheets, what are they and where can I learn more?
4. Should I design for a specific browser and resoulution? Which ones?
5. What are tables? Where can I learn more?
6. In a link, how do I "break out" of frames?

1. Introduction
   

   This document contains answers to commonly asked questions on the HWG-Basics mailing list and will gradually grow with information to help both beginners and advanced writers.
   
   

   If you feel that you have a topic that should be added, you may submit it to the list guides at hwg-basics-help@hwg.org. Your submission will be considered on the basis of:

   1. Does it really pertain to a frequently asked question?
   2. Does it indeed provide an answer to the frequently asked question?

   This is not an offer for free advertising of any site, nor will blatant commercial sites be considered. This information is provided for the writers who have come here to learn. Comments about this document should be sent to hwg-basics-help@hwg.org.

   Table of Contents

2. Validation, what is it and why would I want to use it?
   

   Browsers accept Web pages and try to display them even if they're not legal HTML. Usually this means that the browser will try to make educated guesses about what you probably meant. The problem is that different browsers (or even different versions of the same browser) will make different guesses about the same illegal construct.

   It is even possible for a browser to crash. That is why you want to make sure your pages are legal HTML. The best way to do that is by running your documents through one or more HTML validators. A HTML validator will either parse your HTML markup or scan it and look for errors. To validate an HTML document you need to insert a special <!DOCTYPE...> statement at the beginning of your document. This identifies the file as HTML and states which version you are using. Listing of <!DOCTYPE...> statements.

   If you use the W3C validator for HTML, you should also be sure to validate Style Sheets as well.

   Sometimes a validator will generate pages of errors. It is usually worthwhile to correct one or two near the top of the page and re-validate. Often, many of the later subsequent errors will also be repaired.

   If you need to clean up some existing html on a page generated by you, someone else, or an authoring tool, you might want to try HTML Tidy. As with any unfamiliar tool, be sure to make a spare copy of the file first, in case something important to you gets lost.

   You can also check the HWG Validation Resource Page for both online and offline validators and tools.

   Table of Contents

3. Cascading Style Sheets, what are they and where can I learn more?
   

   Style sheets describe how documents are presented on screens, in print, or perhaps how they are pronounced. By attaching style sheets to structured documents on the Web (e.g. HTML), authors and readers can influence the presentation of documents without sacrificing device-independence or adding new HTML tags. Cascading Style Sheets were developed by the World Wide Web Consortium (W3C). Style sheets have been an W3C activity since the consortium was founded and has resulted in the development of Cascading Style Sheets (CSS). The easiest way to start experimenting with style sheets is to find a browser that supports CSS.

   W3C Home Page
   List of browsers that support CSS1 and their progress.
   W3C Style Sheet Information Page
   Webmonkey tutorial for getting started
   HWG CSS FAQ for much detailed information on CSS usage.
   Browser support
   

   Table of Contents

4. Should I design for a specific browser and resoulution? Which ones?
   

   You want to be careful about designing a web page that looks great on your computer but is a jumbled mess or doesn't even show up on someone else's. This can arise becaues browsers vary in what tags and attributes they recognize and how hard they try to make up for any errors you may make in your code.

   That fact leads designers to testing in different browsers, on different operating systems, and with different screen resolutions. But which ones of the many out there should you focus on?

   The answer will depend partly upon who visits your site. Are they professionals, software developers, web site designers, magazine and newspaper editors, writers, hobbyists, children, or teens?

   In general, professionals and web site designers tend to use newer, nicer browsers. Teens who enjoy working with computers tend to fit into this category as well. Children, however, may use whatever is available or, possibly, what came on their computer.

   Resolution is just as difficult and also depends on the visitors. In general, people who really enjoy using computers and professionals (graphic designers, etc.) use higher resolutions.

   Another way to answer this whole question is to try to make your site accessible to all. Generally, the more you build flexibility into your design, the more easily it will accommodate a variety of users and their hardware and software, even though it may not look identical to all. If you use valid structural code, combined with style sheets for appearance, your site should be accessible to most visitors.

   For some tips on how to do this, see Accessible Site Design

   For browser and screen resolution trends see the following links: Browser statistics
   Trends in browser use and screen resolution
   Search the HWG archives Try "resolution" and "browser."

   Table of Contents

5. What are tables? Where can I learn more?
   

   The primary purpose of tables is to lay out data in tabular form for easier reading. They have been used as well to position various elements on the page. The latter use is gradually being superceded by use of cssfor layout. Tables are created using the <TABLE...> tag and its attributes.

   HTML Goodies Tables Tutorial
   Webmonkey Tutorial
   Accessible tables
   

   Table of Contents

6. In a link, how do I "break out" of frames?
   

   To "break out" of frames you need to insert target="_top" at the end of your tag.
   e.g. <A HREF="http://www.foo.com/" target="_top">
   This will allow the target page to load full screen, not into a frame.

   Table of Contents