Xerox Alto’s old server folders are browsable, with code, fonts and applications intact
The Computer History Museum preserved a research workplace’s files in their original groupings, making the software’s surroundings part of the history.

Filene, Ibis and Indigo still have files to browse. The old PARC server names survive in the Computer History Museum’s Xerox Alto archive, so visiting a piece of computing history can mean opening somebody’s folders instead of admiring another picture of a mouse.
The museum’s release account describes source code, executables, fonts, documentation and other material from 1975 through 1987. The archive keeps the original server groupings, plus collections recovered from other tapes. Each file generally appears in a viewable form and its original raw form. The paperwork made the trip too (excellent foresight).
The collection includes a larger working environment than the familiar graphical-interface highlights suggest. The museum describes BCPL, Mesa, Smalltalk and Lisp programming environments, together with applications including Bravo, Markup, Draw, Sil and Laurel. A person can investigate how a workplace fit together instead of treating every famous application as an isolated invention.
That surrounding material changes the kinds of questions it is possible to ask. A font file beside a document can explain an assumption that the document never bothers to state. A manual can name a behavior that would be obscure from the source alone. Keeping the neighbors lets the next reader follow those relationships.
Browsing also sets a useful limit on the promise. A raw executable in a preserved directory is not automatically something a current laptop can run. The viewable copy lets a person inspect material without making that leap. An old file can be legible while the machinery needed to execute it remains a separate project.
For someone curious about the Alto, choosing one recognizable application is a better start than opening every folder at once. The archive can then answer the narrower questions around it: what documentation survives, what source belongs nearby, and which file is a rendering intended for present-day viewing.
That approach would also make a useful model for preserving a current project. Keep a file’s original bytes and a readable rendering when possible, but don’t confuse them. The rendering helps people inspect the contents; the original preserves details that the renderer may omit. Future readers deserve to know which one they are looking at.
A preserved workspace can make the past feel less inevitable. The applications share a place with all the supporting material required to use and maintain them. The folder structure allows a visitor to follow work rather than a finished retrospective, with the occasional puzzling filename left available for another person to investigate.
The museum account explains how the release became browser-readable. Whether any particular file answers a visitor’s question still requires opening it. That is an unusually pleasant amount of unfinished business for an old server to have.
Ibis is still taking visitors.