What Happened to 'View Source'?
The web used to come with a key to its own construction. For a generation of curious tinkerers, the path to understanding how a website worked was breathtakingly simple: right-click, select "View Page Source," and suddenly, the entire digital facade fell away. You were greeted by a raw text file of HTML, the bones and sinew of the page before you. This wasn't a hidden developer tool or a paid feature; it was a default, fundamental permission slip. It said, implicitly, "Here is how this is made. You can learn from it, borrow from it, remix it." Today, that key is rusting in the lock.
Modern web development, with its complex frameworks and build processes, has rendered the native "View Source" increasingly opaque. What you see when you inspect the code of a contemporary site is often a tangled forest of minified JavaScript, references to external modules, and a skeletal HTML document that bears little resemblance to the rich page in your browser. The actual logic, the human-readable structure, has been compiled and bundled away. The intent is efficiency and performance, laudable technical goals. But a side effect is a closed door where an open window once stood.
This shift presents a subtle but serious challenge for web archiving and digital preservation. Archivists aim to capture the experience and the content of the web for the future. But when the underlying source is a black box of machine-optimized code, we also lose the ability for future historians, scholars, or simply curious minds to easily understand its construction. We preserve the rendered output—a kind of digital taxidermy—but not the clear, annotated blueprint. The web’s original ethos of viewable, learnable transparency is receding.
The Preservation of Process
This isn't just about nostalgia for simpler websites. It's about preserving a record of process and intention. The handwritten HTML of a 1990s personal homepage, with its comments and clunky tables, tells a story about the person who built it and the tools available at the time. It’s a direct artifact. A React component built through a toolchain, once archived, may only tell a story of obfuscation.
Some in the open data and preservation community are pushing back, advocating for a principle of "Archivable Source." This is the idea that developers should consider, alongside performance metrics, how their site's fundamental building blocks might be preserved and understood. It might mean providing a separate, commented source bundle to an archive like the Internet Archive alongside the crawl. It could mean championing frameworks that prioritize readability without sacrificing function.
The loss of 'View Source' as a universally effective tool is more than a technical footnote. It's a cultural shift from a web that invited you to look under its hood to one that often asks you to just admire the paint job. As we work to save the digital present for the future, we must ask: are we saving only the glossy brochure, or are we finding ways to preserve the workshop notes, the sketches, and the instructions? The answer will determine how well future generations can truly understand, and learn from, the web we built.
Notes & further reading
A few pages I came back to while writing this: