Next: The file head Up: Schwab & Schroeder: SEP Previous: An alternative Style

HTML page enhancements

A good on-line source for tips on authoring web pages is the section Authoring web pages, images and scripts at <http://www.boutell.com/faq>. The following example (See Figure 2) demonstrates the HTML constructs we typically choose when writing the SEP web pages:

<HTML>
   <HEAD>
      <TITLE>Shakespeare on doubts</TITLE>
      <META NAME="keywords" CONTENTS="Shakespeare measure doubt">
   </HEAD>
   <BODY bgcolor="white">
      <IMG ALIGN=right SRC="angst.gif" HEIGHT=56 WIDTH=50 ALT="[Fearful face]">
      <H4>Shakespeare: Measure for Measure</H4>

Our doubts are traitors, <BR> 
      And make us lose the good we oft might win, <BR> 
      By fearing to attempt.
   <HR>
   <ADDRESS>
      <A HREF="mailto:matt@sep.stanford.edu">matt@sep.stanford.edu</A>
   </ADDRESS>
   <!-#include virtual="/return2sep"->
   </BODY>
</HTML>

angst
Figure 2 This example corresponds to the HTML skeleton that is discussed in the text. The HTML page contains a few invisible features. For example, the image is accompanied by a short statement that is displayed by text-only browsers. A keyword statement helps web search engines to catalog the page.

A browser may successfully render web pages even if the pages ignore some of the discussed HTML elements. Such negligence may, however, cause difficulties for web search engines, other browsers, or book-marks. Therefore, we recommend modeling new web pages on the above example.

docshtml
Figure 3 Table-of-contents page that lists SEP's reproducible publications (reports and books). Each hyperlink leads to a document specific table-of-contents page as shown in Figure 4.

sep92html
Figure 4 The table-of-contents page of SEP sponsor report 92. Each chapter (article) is represented by an abstract, a link to a postscript file, and a tarred document directory.

Next: The file head Up: Schwab & Schroeder: SEP Previous: An alternative Style

Stanford Exploration Project
3/8/1999