One of the original draws of the early World Wide Web, which for most people seems to have outpaced the general Internet in popularity, was the ability to host web pages.

We will be experiencing that very task, through the manual creation of our own web pages, as well as the necessary UNIX-related backdrop helping to ensure its operation.

Web pages are written in HTML (HyperText Markup Language), a document format that web browsers can interpret and render content to the screen.

They are reached via URLs (Uniform Resource Locators), which inform various tools of the how, where, and what to retrieve.

• how: what is known as a schema, this is the http://, https://, and ftp:// that far too often is abstracted by the web browser in the address bar. This doesn't mean it is by any means optional: the web browser still has to insert that information.
• where: host, fully-qualified domain name (FQDN), and any resultant path referencing the location of content on the server
• what: the actual file we wish to retrieve. Often times, if no specific file is requested, the web server can be configured to serve a default “index.html”.

In our case, we'll be using the Lab46 Web Server to host our own web content. Piecing together the above how, where, and what, our URL will resemble the following:

• http://lab46.corning-cc.edu/~username/file.html

Many of you have likely already been interacting with your web URL as a means of facilitating activities in other assignments.

The “~username”, and specifically the tilde (~), is a server-configured feature indicating your home directory's web directory, which is public_html/, any content put under that directory and made world readable (public_html/ itself as well as your parent home directory must both have world search in order for it to work as well). You may create subdirectories under public_html/ and store web content under them- the same permissions requirements apply.

To reference any subdirectories, merely append the directory name after the “~username/” component of the URL.

As indicated above, web documents intended for viewing in a web browser are predominantly either written (or ultimately displayed as) HTML.

HTML uses a set of predefined tags, very much like some of the wiki-based tags you may have used while maintaining your up-to-date weekly Opus entries.

A google search for HTML tags will turn up a seemingly unending list of information on HTML and the available tags, that information which you will be required to obtain to complete this project.

The basic format of many tags is of one of the two formats:

• pair (open and close): <p>This identifies a paragraph</p>
• unary (standalone): <img src="images/image1.png" />

The forward slash (stroke) is used to identify the closing tag, and as also present at the end of the unary tag.

Common mistakes are misspelling the tag, or forgetting to close an opening tag.

Your task for this project will be to create a series of web pages in the form of a simple web-based adventure game.

It will consist of a minimum of 18 pages, each one consisting of a room that the viewer can navigate to.

Requirements are as follows:

• starting page in the base of your public_html/ directory named: adventure.html
  • This page should have an introduction describing the nature of your quest/adventure
• each page must have a set of links to adjoining rooms (methods of connection up to you: left, right, up, down, north, south, etc.)
• also in the base