Previous Page TOC Next Page Home


13

Putting HTML to Work Building a Sample Site

You've come a long way in a short time. Your Web server is up and running, and you've learned a great deal about HTML. Now it's time to put what you have learned to work by building a sample Web site from the ground up. This project will give you an opportunity to try out many of the HTML tags that you have learned along the way.

On the accompanying CD, you will find a group of files that comprise a sample Web site for a fictitious business called YourCo that sells a software product called Widget. Our imaginary Web site is designed to provide information about the products of YourCo, process orders, provide for immediate download of a demo version of Widget, and give the customer an opportunity to talk to us via a feedback form. These files are intended to give you something to experiment with and build upon. Hey, maybe your site could use some of these capabilities as is.

Planning Your Web Site

There are many things to consider when setting up your Web site. A well thought-out site will go online quickly and painlessly, whereas a poorly thought-out site will be a management nightmare from day one.

For example, if you were to decide to change your directory structure after establishing your site, you would have to change all the links that contained any of the affected URLs. Any non-local links would also have to be changed. And because most indexing on Web search databases takes from two to three weeks now, that could put your site out of business for awhile.

As part of your planning, think about your mission. What is it that you want to do with your Web site?

Figure 13.1 is a feature map of our sample Web site for YourCo. As you can see, this site includes several links between pages, usage of the Netscape mailto feature, and a few CGI programs. See the next section for a brief description of each of the HTML files.


Figure 13.1. Diagram of features of the YourCo Web site.

Installing the Sample Web Site Files

On the CD, you will find all the source documents for this chapter in the \site directory. Here is a brief description of the sample Web site files, in the same order as they will be discussed in this chapter:


All of the HTML files in this chapter were originally created using WebEdit 1.1.

To install the sample Web site on your hard drive, just copy all the files from the \site directory on the CD-ROM into the default directory of your Web server. The fact that one of the files is actually named default.htm means that it will be automatically sent by the server if any Web client specifies only the FQDN portion of your Web site. In other words, if the client doesn't specify a filename in the URL, the server tries to return a file called default.htm from the given directory. And if the URL doesn't contain a pathname either, the server looks in its default directory.

Configuring the Sample Site

There are a few places you need to edit in the sample HTML files. You can load the files into WebEdit and search for the word YourCo. Obviously, you want to change this to the real name of your organization. You might as well just search for the word your because a few of the files include text such as your IP address here or your e-mail address here. You'll see that the search for your will also turn up a few unintended hits. As we discuss the files one-by-one in the next section, we'll call your attention to several lines you need to modify.


Note: If you don't have your HTTP server online yet, most browsers have an option similar to Netscape Navigator that allows you to look at the files by choosing "File/Open File..." This is sometimes called local mode. It is very useful for testing your pages.

Review of the HTML 2.0 Form Tags

Before diving into studying the HTML files line by line, let's recap the HTML tags that are used for creating forms on the Web. The sample files are going to show you a couple of working examples that utilize several of these tags. The possibilities for creative form development are endless. Perhaps as you study Table 13.1, your imagination will lead you to an idea about a form that you or your office could deploy on the Web (or on the Intranet).

Table 13.1. HTML tags for creating forms.

<FORM> ... </FORM>

These tags appear within the <BODY> of the HTML file. Everything you code in between them will comprise the form. In addition to other HTML tags, the tags described in this section are valid within a <FORM> block.

<TEXTAREA> ... </TEXTAREA>

These tags cause the browser to present a multi-line text edit box on the form. You can control the width and height in character units with the ROWS and COLS properties. As with the <INPUT> and <SELECT> tags, the NAME property is used to identify the data that is returned to the server for CGI processing or sent in the e-mail body if mailto is used (more about that later).

<INPUT> ... </INPUT>

These tags define a single-line text box for strings or integers; a checkbox; a radio button; a pushbutton; and a few other varieties of controls. The TYPE attribute is what determines the style of <INPUT> control.

<SELECT> ... </SELECT>

These tags define a listbox of items from which the user can choose an item. You may use several <OPTION> tags within the <SELECT> block to present the available items.

<OPTION>

This tag indicates a selectable item within a <SELECT> block. You might also specify one of the values to be selected by default using the SELECTED attribute.

Understanding the HTML Code, Step-by-Step

You can browse through the HTML code and the screen shots in this chapter to get an idea of all the functionality at this site. You might be surprised at how few files are necessary to deliver such a substantial and professional business presence. You will notice that the home page contains all the necessary introductory information about YourCo, including links to more specific information on its services and products.


If possible, try to keep the size of your home page down to one viewing screen. This will ensure that people can easily see your introductory information and still allow them to jump from link to link without having to use the scroll bars on their browser.

Let's go behind the scenes and see what makes the sample site tick. We are going to present each file and talk you through the highlights. We'll start off by looking at the default.htm file.

default.htm

The purpose of this file was mentioned previously; this is the YourCo home page. It is the first impression your customers will get, and it should give them an opportunity to quickly find what they are looking for.

Listing 13.1 is the contents of default.htm. The annotations following the listing will reference the HTML code.

<HTML>

<HEAD>

<!-- Created: 7/30/95 8:39:28 PM-->

<!-- A comment area with file creation date and time-->

<TITLE>YourCo Inc. Home Page</TITLE>  <!-- Every file needs a TITLE-->

</HEAD>          <!-- End of the HEAD section-->

<BODY>           <!-- Begin the body of the file-->

<IMG ALT="The YourCo Logo" SRC="yourco.gif">

<!-- Display an image of YourCo's logo-->

<!-- Note the alternative text will be displayed if the browser

does not support graphics or does not have them turned on-->

<H1>Welcome to YourCo, Inc.!</H1>

<!-- A heading level one text section, no need to insert a [br] or [p] to

start next line-->

YourCo is the world's leading supplier of Widgets. We have been

in business since 1994, and have had a Web presence since today.

Our newest product is

<A HREF="product.htm">Widget</A>.

<!-- This is a hyperlink to the product.htm file-->

You can

<A HREF="order.htm">order your own copy of Widget</A> electronically.

You can also

<A HREF="custreg.htm">register for the YourCo customer newsletter</A>

, sent out by e-mail every month.<P>

We are pleased to provide the following information about YourCo:<P>

<UL>

<!-- An unordered list with hyperlinks-->

<!-- note that the [LI] tag is not paired-->

<LI><A HREF="Release.htm">YourCo Press Releases</A><P>

<LI><A HREF="Intro.htm">Introduction to our Products</A><P>

<LI><A HREF="Train.htm">YourCo Training Services</A><P>

<LI><A HREF="Consult.htm">YourCo Consulting Services</A><P></UL>

<H2>Comments or Problems</H2>

<!-- Heading level 2-->

For information on YourCo's products and services, please send e-mail to

<A HREF="mailto: info@YourCo.com"><I>info@YourCo.com</I></A>,

for an automated reply,

<!-- The mailto tag used in a hyperlink will pop up a mail window in most

browsers-->

or use our <A HREF="feedback.htm">feedback form</A> for other inquiries.

<P>

Thank you for visiting YourCo's WWW server.

We hope to hear from you again soon.

<HR>This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

<!-- Insert your standard address and copyright information at the bottom of

each page. #169 is the special character entity for the copyright symbol.-->

</BODY>            <!-- End of body-->

</HTML>            <!-- End of file-->
Noteworthy Code in default.htm

Near the top of the file is a suggested standard comment indicating the date the file was last edited.

As per suggested style guidelines, the <IMG> tag includes alternative text that will display in the event the browser doesn't load the GIF file.

Remember, unlike most HTML tags that are paired, the <P> tag is not usually paired with </P>, but it can be. As you read the comments within the code, be aware that we used the notation [tag] instead of <tag> because some browsers will be thrown off track by the occurrence of unintended HTML tags.


If you ever notice that your HTML code appears strange when you test it in local mode of your browser, be suspicious of the possibility that tags are embedded within comments.

The first interesting thing about this code is the <A> tag and the HREF attribute. This is called an A HREF for short. If you look at default.htm in your browser or in Figure 13.2, you'll see the line that reads, Our newest product is Widget. This snippet of code is responsible for underlining the word Widget:

<A HREF="product.htm">Widget</A>

The underlining is displayed to the user to indicate that the word is a hyperlink to another document, in this case product.htm. The absence of a pathname or a full URL on the HREF attribute means that the file product.htm must reside in the same directory on your Web server as the current file (default.htm).

Following the code further, you will see a few other A HREF hyperlinks. Then you come to the bullet list section. This bullet list starts with the <UL> tag, which stands for unordered list. It is unordered in the sense that it is not numbered. Numbered lists use the <OL> tag. (The O stands for ordered.) Within a <UL> or an <OL> section, you can include several <LI> tags for list items. In fact, as this example shows, you can include all kinds of other HTML code. What's interesting about the bullet list in default.htm is that it includes embedded <A HREF> hyperlinks!

Now you get to the <mailto> tag. This is an interesting critter. Netscape invented this very useful extension to HTML level 2. Most new browsers now support this feature, but some still do not. The purpose of this extension is to give the client a very convenient way to e-mail a message to you. When you think about it, this is something that you may very likely want to do while visiting a Web page. And you wouldn't want to have to bother with writing down an e-mail address, just to type it into your mail program later. The mailto feature works by popping up a browser-defined dialog box (slightly different in every browser), where the recipient list is already filled in with the e-mail address given in the HTML file, in this case info@YourCo.com. Typically, the client has already configured a browser with his or her own e-mail address, so all the client has to do is fill in the subject and the body text. Here are the steps of this transaction:

  1. The client requests the server to send the document default.htm.

  2. The server sends default.htm, and the client displays it.

  3. The user clicks the mouse on the underlined text area of the screen.

  4. The browser analyzes the pixel coordinates of the mouse click and determines that it is within the underlined text area of the screen formed by the <A> tag.

  5. Because the browser understands the <A> tag uses HREF with mailto:, it opens a local dialog box asking the user to fill in the mail Subject and Body Text. The recipient's address is already filled in based on the HREF mailto supplied by the server. The sender's reply address and the SMTP server to use for sending mail on the client system must be preconfigured by the user of the browser.

  6. When the user hits the Send button in the e-mail dialog, the mail is sent by the browser to the address that was originally specified in the HTML code written on the server side. The mail dialog closes, and the user can continue reading the Web page.

This six-step description falls somewhere in the middle of the complexity spectrum. It gets inside the HTML code but stays above the HTTP levels, and well above any analysis of the TCP/IP data stream.

If you suspect that some of your Web visitors won't have support for mailto, you do have alternatives. One method is to run a CGI application on the server side that accomplishes nearly the same thing. You might also take a look below at the file custreg.htm. It uses mailto in a slightly different fashion as part of an HTML form.

Finally, note the <HR> tag. This stands for horizontal rule. It draws a line across the page for decoration and readability. We use it here to separate the standard copyright or address information that shows at the bottom of the page. The copyright symbol is embedded with the special code &#169;. There are many other special symbols available. A Netscape HTML extension permits the use of &copy; to achieve the same purpose with greater readability. In any case, you must include the trailing semicolon.

You may know that HTML has an <ADDRESS> tag. This is often used for the same purpose as what we are doing with everything following the <HR> tag. Basically, it will italicize your address information.

That wraps up our basic description of default.htm. Many of the other files include several of these same features. In the sections that follow, we'll mention the areas of the code that aren't covered elsewhere.

consult.htm

This page describes our make-believe consulting services. Figure 13.2 shows the page loaded in Navigator.


Figure 13.2. consult.htm as it appears in Navigator.

Please see Listing 13.2 for the HTML code.

<HTML>

<HEAD>

<!-- Created: 7/30/95 8:39:28 PM-->

<TITLE>YourCo Consulting Services</TITLE>

</HEAD>

<BODY>

<H1>YourCo Consulting Services</H1>

<H3>Let the world know about all of your services.</H3>

<!--Give web surfers a way to return to the home page.-->

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>
Noteworthy Code in consult.htm

There isn't much to explain about this short page. The bottom of this page, as well as all the others except default.htm, includes a hyperlink back to the home page. This is common courtesy because readers will frequently click a link as an experiment, only to be carried to a page from which they want to return quickly.

We leave it up to you to dress up the content of this page. It is meant only as a placeholder to show where consulting services could be mentioned on a Web site.

custreg.htm

This file lets customers put themselves on the YourCo mailing list. Figure 13.3 shows custreg.htm loaded in Navigator. This form also uses mailto, but it uses it within a <FORM> tag. The difference between this and the mailto used in default.htm is that here the data in the form is automatically mailed to the address specified by the mailto element and no pop-up e-mail window is activated on the client.


Figure 13.3. Custreg.htm in Netscape Navigator 2.0.

The HTML code for the customer registration form appears in Listing 13.3.

<HTML>

<HEAD>

<TITLE>YourCo Newsletter Registration</TITLE>

</HEAD>

<BODY><H1>YourCo Newsletter Registration</H1>

<FORM METHOD="POST" ACTION="mailto:register@YourCo.com">

<!-- Using "mailto" as a method in a form will mail the contents of the form

to the address stated, if the browser supports "mailto". It is more robust to

provide a CGI application to handle forms data.-->

Please help us to keep you informed about our products by filling in this

questionnaire. This will add you to our e-mail list.

<p><PRE>

<!-- Use [PRE] tags to help you line up forms-->

<!-- INPUT data will be mailed.-->

        Your Name: <INPUT NAME="user" SIZE="30"><P>

Your organization: <INPUT NAME="org" SIZE="30"><P>

      Your e-mail: <INPUT NAME="mail" SIZE="30"><P>

</PRE>

<input type=submit value="When done, click here to send">

<!-- Invokes the form action.-->

</FORM>

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>
Noteworthy Code in custreg.htm

As you can see, this HTML code is quite different than the code in the first two files. This code takes advantage of the <FORM> tag, a very powerful feature in HTML 2.0. Notice the line of code that reads

<FORM METHOD="POST" ACTION="mailto:register@YourCo.com">

This uses the ACTION attribute of the <FORM> tag to specify that the browser should perform a mailto operation on the client side after the form is submitted. It works in tandem with this line of code near the end of the form, just before the </FORM> tag:

<input type=submit value="When done, click here to send">

The <INPUT> tag specifies that a field should be drawn on the form. The TYPE attribute of this field is submit, which means that it will be a pushbutton. The VALUE attribute indicates what the label of the button will be. On this form, the button is called, "When done, click here to send." The browser will determine the size of the button based on the current font and the text supplied for the VALUE attribute.

When a user presses the submit button, the FORM ACTION will occur. The ACTION attribute could point to a CGI script to run on the server side, but in this case it is using built-in functionality on the client browser to cause the form data to be mailed. The recipient of the mail is automatically supplied by the HTML code on the server. Here, the form will be mailed right back to YourCo! Webmasters consider it convenient to receive form data like this in their incoming mail.

The other noteworthy code in this form determines how the screen gets drawn. The three lines containing <INPUT> tags draw text boxes for the user to fill in. Each box accepts up to 30 characters. The form data from those text boxes will be sent through e-mail formatted like this:

Return-Path: <bill@whitehouse.gov>

From: bill@whitehouse.gov

Date: Sat, 30 Sep 95 09:35:51 -0700

Subject: Form posted from Mozilla

Apparently-To: <register@YourCo.com>

user=Bill&org=Whitehouse&mail=bill@whitehouse.gov

The NAME attributes on the <INPUT> tags determine the labels that go with the form data when it is sent through e-mail or processed by CGI applications on the server. You can see the user, org, and mail labels in the last line in the form data above. The & characters are field delimiters.

feedback.htm

Figure 13.4 shows a form that enables your customers to submit feedback via e-mail. This capability is an important part of quality customer service.


Figure 13.4. Feedback.htm in Netscape Navigator.

See Listing 13.4 for the HTML code as you follow these additional comments.

<HTML>

<HEAD>

<TITLE>YourCo Feedback Form</TITLE>

</HEAD>

<BODY>

<H2>YourCo welcomes your comments and suggestions.</H2>

<P>

<!-- YOU MUST CHANGE THIS LINE TO REFLECT YOUR SERVER DOMAIN NAME-->

<FORM METHOD=POST action="http:<!--your IP address here/http/cgi-

bin/perform.exe">

<!-- Here we use a CGI application to handle the form data. The perform.exe CGI application will handle parsing the data from the form and then mailing it.-->

<INPUT TYPE=hidden name="CmdFile" value="/http/mail.cmdl">

<INPUT TYPE=hidden name="mailto" value="your e-mail address here">

<INPUT TYPE=hidden name="errto" value="your e-mail address here">

<!-- These hidden values tell the mailto CGI application where to mail the

data and where to send error reports.-->

<B>Subject:</B>

  <SELECT name="subject">

  <OPTION> Comments on YourCo Web page

  <OPTION> I'd like to open an account

  <OPTION> I'd like to comment on...

  <OPTION> I need some information on...

  <OPTION> Would you please...

  <OPTION> Other

  </SELECT>

<PRE>

            <B>Name:</B> <INPUT name="name" SIZE=30>

    <B>Company Name:</B> <INPUT name="company" SIZE=50>

       <B>Phone No.:</B> <INPUT name="phoneno" SIZE=20>

  <B>E-mail Address:</B> <INPUT name="e-mail" SIZE=30>

</PRE>

<P>

<PRE>

<B>Your Mailing Address:</B>

   <B>Street/PO Box:</B> <INPUT name="address1" SIZE=50>

            <B>City:</B> <INPUT name="city" SIZE=30>

           <B>State:</B> <INPUT name="state" SIZE=10>

             <B>Zip:</B> <INPUT name="zip" SIZE=11>

         <B>Country:</B> <INPUT name="country" SIZE=30>

</PRE>

<P>

<B>Comments:</B>

<BR>

<TEXTAREA name="~comments" cols=60 rows=4></TEXTAREA>

<P>

<input type=submit value="When done, click here to send">

</FORM>

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>
Noteworthy Code in feedback.htm

Of interest here is the <SELECT> ... </SELECT> block that includes several <OPTION> items. The <SELECT> block creates a drop-down listbox named subject, on the form. The item the user chooses will be sent as a text string to the CGI application on the server.

There are two separate blocks of <INPUT> tags. <INPUT> defaults to a single line text field if the TYPE attribute is not present. The SIZE attribute is used to limit the number of characters that the user is permitted to type in the field. This is an example of client/server cooperation. The CGI application on the server might be storing the form data in a relational database that has limited size fields. The HTML/CGI programmer can use the SIZE attribute to ask the browser to ensure proper constraints on the data that will be submitted. This represents a simple kind of fault tolerance that will prevent the user from breaking the CGI application either intentionally or accidentally. Of course, the CGI application is ultimately responsible for parsing the data and handling any error conditions.

Each <INPUT> tag is indented with spaces instead of tabs to line up the fields. Not all browsers will interpret tab characters the same way, so spaces are preferred.

A <TEXTAREA> and a submit button finish up the form. The <TEXTAREA> tag is used to create multi-line edit fields.

intro.htm

This purpose of this page is to introduce the YourCo products. See Figure 13.5 for the way it looks on the Web.


Figure 13.5. Intro.htm running on the Web.

See Listing 13.5 for the HTML code of the file intro.htm.

<HTML>

<HEAD>

<!-- Created: 7/30/95 8:39:28 PM-->

<TITLE>Introduction to YourCo Products</TITLE>

</HEAD>

<BODY>

<H1>Introduction to YourCo Products</H1>

<H3>For just a few $'s per month you could tell the world about your

products here.</H3>

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>

There is nothing new to say about this file from a programming viewpoint. It is a placeholder for the actual HTML file, which you can modify to describe your products.

order.htm

This purpose of this page is to let your customers order your products. See Figure 13.6 for the way it appears on the Web.


Figure 13.6. Order.htm shown running on the Web.

See Listing 13.6 for the HTML code of the file order.htm.

<HEAD>

<TITLE>YourCo Order Form</TITLE>

</HEAD>

<BODY>

<CENTER>

<!-- CENTER is an HTML 3 tag -->

<H2>YourCo On-line Order Form</H2>

<HR>

</CENTER>

<FORM METHOD=POST ACTION="http:<!--your IP address here/http/cgi-

bin/perform.exe">

<INPUT TYPE=hidden name="CmdFile" value="/http/mail.cmdl">

<INPUT TYPE=hidden name="mailto" value="your e-mail address here">

<INPUT TYPE=hidden name="errto" value="your e-mail address here">

<INPUT TYPE=hidden name="subject" value="demo Order">

<PRE>

<BR>E-mail address:<INPUT NAME=e-mail_addr TYPE=text SIZE=40>

<BR>Your Name:    <INPUT NAME=Name TYPE=text SIZE=40 MAXSIZE=40>

<BR>Shipping and billing address:

<BR><TEXTAREA NAME=address ROWS=3 COLS=30 MAXLENGTH=150></TEXTAREA>

<BR>Item 1: <INPUT NAME=Tittle TYPE=text SIZE=40>

<BR>Item 2: <INPUT NAME=Medium TYPE=text SIZE=40>

<BR>Item 3: <INPUT NAME=Edition TYPE=text SIZE=40>

<BR>    Shipping/handling ($10.00) <INPUT NAME=SH TYPE=text SIZE=7>

<BR> CA Residents add 7% Sales Tax <INPUT NAME=Tax TYPE=text SIZE=7>

<BR>                  Order Total$ <INPUT NAME=Total TYPE=text SIZE=7>

</PRE>

<H4>Payment Method</H4>

<INPUT TYPE=radio NAME=pmtmethod VALUE="check" Checked>Check

<INPUT TYPE=radio NAME=pmtmethod VALUE="account">Account

<P>

<INPUT TYPE=submit VALUE="Submit Order!">

</FORM>

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>
Noteworthy Code in order.htm

Other than the radio buttons, there are no new elements to describe on this form. Strictly speaking, if you want to indicate an on/off condition of a single item, normal Windows GUI style suggests the use of a checkbox. Radio buttons are usually used to represent a group of several mutually exclusive items. Radio buttons are exactly what we want on this form because we have several payment methods (well, only two currently—but you can easily add more).

Again, an <INPUT> tag using TYPE=submit is coded to send the form data to the CGI application on the server. The Web server will invoke a CGI application (perform.exe) in the cgi-bin directory each time that a client presses the submit button.

product.htm

product.htm is used to further describe the products of YourCo. See Figure 13.7 for the way it appears on the Web.


Figure 13.7. Product.htm running on the Web.

See Listing 13.7 for the HTML code of the file product.htm.

<HTML>

<HEAD>

<!-- Created: 7/30/95 8:39:28 PM-->

<TITLE>Product</TITLE>

</HEAD>

<BODY>

<H1>All About Widget</H1>

<H3>Widget is the best widget-type product in the world.</H3>

To download a free demo copy of Widget, click <A HREF="demo.zip">here.</A>

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>
Noteworthy Code in product.htm

This code contains nothing unusual; however, it permits your customer to download a free demo copy of your software product and try it out. Here's how this works. The <A HREF> refers to demo.zip. When the user clicks that screen region and the client requests the file demo.zip from the HTTP server, the client doesn't yet know exactly what type of document it really is. The server will send a header back to the client informing it that the data type is urlencoded. The client will most likely tell the user that it is unprepared to handle that type and ask the user if he would simply like to download and save the file. Of course this is precisely what the user is hoping to do! Clicking the appropriate button in that message box will initiate the file transfer. It might take some time to download large files, so Netscape Navigator will display a progress bar as the download proceeds to 100% complete. Remember that you will often need to use WinZip to decompress files that you retrieve on the Internet.

release.htm

This purpose of release.htm is to display YourCo Press Releases. See Figure 13.8 for the way it looks on the Web.


Figure 13.8. release.htm running on the Web.

See Listing 13.8 for the HTML code of the file release.htm.

<HTML>

<HEAD>

<!-- Created: 7/30/95 8:39:28 PM-->

<TITLE>YourCo Press Releases</TITLE>

</HEAD>

<BODY>

<H1>YourCo Press Releases</H1>

<H3>Sunday, July 30, 1995 8:55:55 PM<BR>

Over 20 million people have access to the Web. Usage is growing 50% per

month.</H3>

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>

train.htm

The purpose of this page is to describe YourCo training services. See Figure 13.9 for the way it looks on the Web.


Figure 13.9. train.htm running on the Web.

See Listing 13.9 for the HTML code of the file train.htm.

<HTML>

<HEAD>

<!-- Created: 7/30/95 8:39:28 PM -->

<TITLE>YourCo Training Services</TITLE>

</HEAD>

<BODY>

<H1>YourCo Training Services</H1>

<H3>The World Wide Web has become the fastest-growing part of the

Internet in the last year.</H3>

<P><HR><I><A HREF="default.htm"><IMG SRC="RETURN.GIF">

Back to YourCo Home Page.</A></I><P>

This page, and all contents, are Copyright &#169; 1995 by YourCo Inc.

</BODY>

</HTML>

train.htm contains nothing new from a programming standpoint.

What's Next

This wraps up Part III of the book. Now we can get into some of the really exciting things you can do at your Web site. Here are just a few of the topics which lay ahead of us: keeping statistics of which pages are visited most often; running a mail server; running an FTP server; and connecting HTML code to relational databases.

Because you nearly have your site running officially on the Internet, you might want to take special notice of many security ideas that are going to be brought up in the remainder of the book. Several tips presented in Part IV should help you avoid some of the common risks from hackers.

Previous Page TOC Next Page Home