AOL’s help desk had its own training material for getting employees connected. This March 2002 SERA 2.5 module runs to 44 pages, covering the client, troubleshooting and remote-access support. The cover and selected interface pages preserve the training document’s original appearance. It is a historical look at AOL’s internal support tools, rather than current connection instructions.
An e/n site could have a new layout, a long update about a terrible day, and a list of links to people who were also having terrible days. That was the whole thing. Everything and nothing. Usually posted after midnight. No niche. No content strategy. Just a small website announcing that school sucked and the new layout wasn't finished yet. I'd read that.
SERA was the other kind of AOL sign-on: a way for employees to reach the corporate intranet remotely. The enclosed user guide is dated November 8, 2001 and covers Windows, Linux, Solaris and Mac clients. The archive includes the 19-page guide alongside platform-specific installers. The screenshots here come from that guide; the old software has not been installed or tested.
Leaving IRC wasn't enough. You needed a custom quit message so everyone knew you were leaving in a very specific and interesting way. A joke, a quote, something that made closing a program sound important. Nobody announced going to the kitchen with that much effort. Disconnecting from a chat server got a whole closing statement.
Backordered, canceled or shipped? AOL’s OrderINQ reference gave support staff a list of codes for checking an order’s progress. This two-page document explains statuses such as backorder notices, cancellations and completed payments. The pictured page is the original reference table, not a customer’s order history.
Somebody gave you ops in an IRC channel with six people in it and suddenly you had responsibilities. The topic needed updating. The rules needed enforcing. Somebody was using too many capital letters. Five minutes earlier you were asking how to change your nickname. Now you were management.
Not every file in this archive is a prog or publishing tool. This 27-page document is an employee insurance booklet for AOL, with an August 2000 effective date and a January 2002 revision. It belongs in a company-history collection rather than the AOL Progs section. This is a historical document, not information about anyone’s current coverage.
Lol sometimes the plan was to sign off AIM and sign right back on so one particular person would notice. Couldn't just say hey. Had to make an entrance. Nothing says casual like disconnecting yourself from the entire internet social scene for eight seconds.
AOL publishers had to think about reporting as well as the page itself. This three-page tracking document discusses URL construction, WebStats, ASPP, Media Metrix and Rainman reporting. It is a small behind-the-scenes snapshot of how publishing teams were asked to measure channels and coordinate a launch.
They couldn't answer your IM, but they had time to change the away message twice. Interesting. Very interesting. Apparently being away involved a lot of editing. You weren't going to say anything. You were just going to put up your own completely unrelated away message that was obviously about it.
This archive contains a full 334-page Eprise Participant Server Event Reference, copyrighted 2000–2001. It is developer documentation for the publishing platform, with events organized as a technical reference. Its presence in this collection is documented; the file alone does not establish exactly where AOL used it.
