Before you begin, set the page properties using File / Page Properties... Because of the
large volume of content, and its lack of organization, most users rely on web searches to
find what they are looking for. Here is how web searches work:
- Most search sites have a web "spider", "crawler" or "bot"
(robot) -- a program that, at night, follows HTML links, reporting back what it finds. The
report includes the URL, keywords, and a summary of the page. The default keywords are
chosen differently by each search site. The default summary is the first section of the
file, outside of the tags. You, the web developer, can
- Let the program decide the keywords and summary (oooh -- could be risky!)
- Tell the program what the keywords and summary are (you control it)
- The search site compiles all of these pages into a database
- When someone searches, the keywords in the database are examines. If a match is found,
the URL and description are presented to the user.
So -- you should use the methods that HTML gives you to control the keywords and
summary. Both are done in the HTML head, using the "meta" tag. Also, the title
that appears on the browser window and the page color are set in the head. In MS
FrontPage98, all of these are set using the File / Page Properties... menu choice and the
Page Properties dialog.

The document title (appears on the browser title bar) is set on the
"General" tab. The background color is set on the "Background" tab.
The keywords and description are set in the User Variables window of the
"Custom" tag as shown above. FrontPage automatically sets GENERATOR to display
its own name and version. Click on the Add button to open up new Name - Value pairs.
Forms. What with colors and images, even animated images, and scrolling and links and
frames, web pages can seem pretty dynamic. Not to mention sound and video which we haven't
touched on. However, all of the elements above are referred to as "static HTML"
and the pages as "static pages." This is opposed to "interactive"
where the user as opposed to the web designer can have some say over what is going on.
With a form, which contains various input elements, the user enters data and makes choices
and sends them in to the web server. The web server reacts, according to a script or
program, and returns a web page which may be customized and depend on the information
submitted by the user. This is called web "interactivity." It is necessary for
eCommerce for the following purposes: (i) the user must select one or more item(s) to
purchase, (ii) the user must choose a delivery method, and (iii) the user must submit a
payment method (e.g. credit card and credit card number. More information may be requested
or required. For example, the online bookseller Amazon.com has a choice of wrapping paper
patterns if the book is a gift.
An form is marked at its beginning with a <form> tag and at its end with a
</form> tag. Between these two tags are input elements or "widgets" and
one or more "Submit" buttons, with perhaps a "Reset" button to clear
all of the input widgets if the user wants to start over. The <form> tag has an
"action" attribute that tells the web server what to to with the form
information. The user fills out the input widgets, or at least those that s/he wishes to,
and clicks on (one of) the Submit button(s) (which can have any text on its surface). The
browser sends all of the information -- form action, contents of the widgets, and which
button was pressed -- back to the web server. What happens next is called the "Common
Gateway Interface", or CGI. The form action information tells the web server to start
a specified computer program -- the CGI program. (Different forms can specify different
CGI programs.) The web server passes all of the form information to the CGI program. The
CGI program processes the form information as it has been programmed to do, perhaps
storing it in a database file. The CGI program also creates a response HTML file for the
user, which may also contain some of the form information, for example confirming which
book was ordered if this is an online bookstore. When the CGI program ends, the web server
looks for the response HTML file and sends it back to the user. This ends the CGI process.
It is worth noting that this a very flexible and multi-purpose process, since the CGI
program can do virtually anything with the data, and prepare the response file can also
have content and formatting that is without limit. The form input widgets are defined by
tags chosen using the menu item Insert / Form Field / type. Ordinary HTML outside
of these form element tags can label the widgets for the user. The various types are
- One-line Text Box, into which the user can type.
- A scrolling Text Box for multiline input
- A check box which can be checked or unchecked. If there are several checkboxes, any
number of them may be checked, from zero to all.
- Radio buttons, which are grouped, and only one in each group can be checked.
- A Drop-Down Menu or "pick list"; the user picks on of the pre-defined items.
The list can also be set up so that the user can pick more than one item on the lists.
When the first form filed is inserted, Submit and Resent buttons are inserted also,
along with the <form> and </form> tags, indicated by dotted lines. Thereafter,
additional form widgets should be inserted inside the dotted lines; otherwise they start a
new, second form. The form widgets and the text that labels them can be positioned by any
valid HTML means, including <Enter>, <Shift><Enter>, tables and frames.
Each input widget has two additional properties, its Name and its Value. The Name is not
seen by the user, and identifies the input for you, the web designer, and for the CGI
program. The Value is what the user enters, although this can be set to a default value by
the web designer. Both are most easily specified by right-clicking on the element and
choosing the Form Field Properties menu item. The dialog supplied the default values for
Name and Value, but these can be replaced by clicking in the fields and typing. Click OK
when done.
Example: The user is supposed to type in her/his credit card number. Insert a One-line
Text Box for this purpose. Label it "Credit Card Number" so the user will know
what to type in. The Name could be "CardNumber" and the Value would initially be
blank, and take on whatever number the user types in. Suppose the user types in 123456789.
Then the Value of CardNumber would be 123456789, which the web browser would send to the
web server, and thereby to the CGI program. Most likely the CGI program would store this
in a database, along with the other purchase information.