How Truman Students Built Websites Before WordPress

Truman’s personal Web-space system used ordinary files, a campus T: drive and public www2.truman.edu URLs—a publishing model documented years before WordPress’s 2003 debut.

Before WordPress turned website publishing into a dashboard, Truman's personal Web system could be understood as a much simpler chain:

make a file → save it in Web-accessible storage → open the public URL

Truman ITS documentation preserves that model unusually well.

Students received personal Web space

Truman's documentation says faculty, staff and students are provided personal Web space.

The public address follows the classic university tilde-user pattern:

www2.truman.edu/~username

On campus, the same Web space is described as the T: drive.

That connected ordinary file storage directly to public Web publishing.

The homepage was just a default file

A personal Web directory did not need a CMS to decide what the home page was.

Truman's documentation identifies standard filenames such as:

  • index.html;
  • index.htm;
  • index.php.

When the Web server sees a recognized index file in the directory, it can serve that file when someone visits the directory URL without typing a filename.

That is the basic mechanism hidden behind many modern publishing systems.

"Publishing" could mean saving a file

A September 2000 Truman AAUP newsletter gives a period description of the workflow using Netscape Composer.

The user edits a page and saves it to the T: drive. The file then becomes available as a Web page.

The example in that newsletter is faculty-facing, so it should not be treated as proof that every student followed the exact same software steps.

But it matches the personal-Web-space architecture that Truman documentation says was available to students.

There was no required WordPress-style dashboard

Different authoring tools could produce the files.

Historical Truman documentation mentions tools such as Netscape, FrontPage and Dreamweaver in its Web-publishing material.

The editor was only part of the process.

The actual public site was the collection of files stored where the Web server could reach them.

For the software side of that workflow, see FrontPage, Dreamweaver and Web Folders: The Tools Behind Kirksville's Early Web.

This model predates WordPress itself

WordPress's own release history dates WordPress 0.70 to May 27, 2003.

Truman's documented T:-drive and www2 workflow was already being described in 2000.

That does not mean Truman switched to WordPress in 2003, or that WordPress immediately replaced file-based campus publishing.

It establishes only the historical comparison:

Truman users were publishing Web files manually before WordPress existed as a public release.

What the older workflow exposed

The file-based model made several concepts visible to the person publishing:

  • the actual files;
  • the home-page filename;
  • the storage location;
  • the public URL;
  • file permissions when something failed.

A modern CMS can abstract most of that away.

The old method was less convenient, but it made the relationship between file, server and URL difficult to ignore.

That is what makes the surviving Truman instructions useful today. They preserve the mechanics of ordinary Web publishing from before "log in to the site and click Publish" became the normal mental model.