Public record · civic memory · regional context
Seattle ChronicleHistorical record & civic resource
resource orientation
This guide preserves the structure and working ideas behind an early civic web presence: its naming history, domain pathways, technical notes, content standards, and planning documents.
Naming the record
The preserved material traces the changing language used to describe a public-facing web service and the routes readers used to reach it.
The early service was associated with the Public Access Network, or PAN. Later references used CityofSeattle.net, while Seattle.gov became the more streamlined domain associated with the city’s web and email presence. These names show how public agencies adapted their online identity as the web became a central information channel.
Read the domain record →Context for PAN, CityofSeattle.net, and the later Seattle.gov identity.
Technical overviews, browser guidance, and the logic of a shared public site.
Mission statements, strategy notes, and preserved annual-report pathways.
Address history
Domain changes are not only technical events. They also record how an institution presented access, authority, and continuity to the public.
01 · Earlier routes
Several domains and subdomains were used as interchangeable paths into the public web service.
02 · Shared structure
Planning documents emphasized a connected web presence rather than isolated departmental sites.
03 · Reader access
Old links remain useful as evidence of how readers navigated services, records, and public information.
System notes
The technical record includes practical guidance for viewing documents, understanding site structure, and maintaining consistent presentation. Read these pages as documentation of an earlier stage in public web publishing.
A broad orientation to the way information was grouped and presented.
A preserved route into the technical foundations of the public site.
Browser guidance reflects the formats and constraints of its period.
Reference note
Policies, software guidance, contact pathways, and annual reports belong to particular periods. Seattle Chronicle presents them as historical reference, not as current operating instructions.
Review resource policy material →Content standards
Preserved standards pages show an effort to make civic information consistent, understandable, and available across a broad range of readers and devices.
Common guidance helped different contributors publish within a recognizable public framework.
Content planning connected individual pages to practical public questions.
Presentation and accessibility notes treated clear structure as part of public service.
Policies and contact routes made the wider information system easier to understand.
Plans & reports
Reports and strategy documents place the web presence within a longer history of planning, review, and public communication.
Annual reports
Annual reports offer snapshots of priorities, activity, and the state of the service at particular moments.
Strategy
Mission and strategy pages explain the intended role of a connected civic information service.
Policy
Policy documents preserve expectations around links, privacy, acceptable use, and presentation.
Reader’s desk
A short guide to reading an older web record in its proper context.
PAN refers to Public Access Network, an early name associated with the public information service and its predecessor bulletin-board environment.
The record documents a period when more than one domain or subdomain could lead readers to the same broader public web presence.
No. Treat the linked policies and standards as historical documents. Current instructions should come from the relevant present-day authority.
They help readers understand how priorities, publishing practices, and the organization of public information changed over time.
Yes. Send a concise page reference or research question to info@seattlechronicle.com-us.com.
resource desk
Search by a subject such as domain names, accessibility, annual reports, policy, or site structure.