Netscape Navigator in Kirksville: Revisiting Truman’s Old Web Instructions

Surviving Truman ITS documentation still tells users to open Internet Explorer or Netscape Navigator and browse to a www2 personal homepage.

Truman ITS still hosts instructions that sound like a preserved fragment of the early Web.

The page tells users to open Internet Explorer or Netscape Navigator and enter a www2.truman.edu personal-page address.

That makes the support document a useful historical artifact even though its original publication date remains unresolved.

The instruction begins with a browser

The surviving page tells the user to browse to a URL in the form:

www2.truman.edu/~yourID

The tilde-user format identifies a personal Web-space model rather than a centrally managed profile page.

The browser’s job was simply to request the published page from the server.

The homepage filename mattered

The documentation warns users to make sure the homepage is named index.htm.

That reflects a basic Web-server convention.

A default index filename lets the server know which file to return when someone visits a directory-level URL.

Without the expected file, the user might see an error or nothing useful.

Permissions mattered too

The same instruction tells users to check file permissions when a page does not display.

That detail reveals how exposed the publishing machinery was.

A user could create a perfectly valid HTML file and still fail to publish it because the server could not read it.

Modern CMS platforms hide most of that problem behind an application interface.

A September 2000 Truman AAUP newsletter documents Netscape Composer as an editing tool.

The workflow it describes is:

  • edit a file in Composer;
  • save it to the T: drive;
  • the file becomes part of the Web site.

Navigator viewed pages.

Composer edited them.

The two were part of the same software family but performed different jobs.

The 2000 newsletter gives the workflow a date

The current ITS page does not expose a trustworthy original publication date.

The September 2000 AAUP newsletter provides a solid contemporary checkpoint showing Netscape Composer inside Truman’s Web-publishing environment.

That allows us to say Netscape-era authoring was documented at Truman by 2000.

It does not prove when the support page itself was first posted.

Old support pages can outlive their software

A University documentation system can preserve instructions long after:

  • the software is obsolete;
  • the browser is unsupported;
  • the server architecture has changed;
  • the original page has been migrated into a newer CMS.

That is why current page timestamps should not be treated as historical creation dates.

What this document proves

It proves Truman supported or documented a workflow involving:

  • Netscape Navigator;
  • personal www2 pages;
  • default index files;
  • permissions;
  • Netscape Composer-era authoring.

It does not prove:

  • first Netscape version used at Truman;
  • first year of Netscape support;
  • how many people preferred it to Internet Explorer;
  • exact retirement date.

The document is strongest when treated as an artifact of a workflow, not as a complete browser history.