Inspiration

W1C started as a way to extract the good parts from two experiments: a GNOME/Ubuntu desktop wrapped around ATProto browsing, and a Windows 95-style Phoenix ATProto PDS. I was starting to feel like their interface work was too useful to stay trapped in those apps.

Intrepid Ibex gave W1C its GNOME 2 and Ubuntu 8.10 center of gravity with the brown top panel, tan window chrome, compact task buttons, tray affordances, desktop shortcuts, and the practical density of Nautilus, gedit, Terminal, and the rest of that era’s app vocabulary.¹

Tempest supplied the Windows 95 side with teal desktop color, blue titlebars, raised and sunken borders, server-rendered forms, flash messages, dense tables, status rows, document browsers, and word-processor shells.²

Those references pushed the project toward web components rather than app components so apps that can load custom elements and CSS would be able to use them.

Design-Systems

I looked at a few modern design-systems to help me structure the project.

Bolt’s “system of systems” framing helped split foundations, layout, elements, components, animation, and documentation into separate concerns.³

Web Awesome keeps its install story optimized for developer experience with all-in imports, cherry-picked imports, CDN usage, theme CSS, optional native styles, utilities, SSR compatibility, and asset loading.⁴

Nord’s catalog is the model for treating component pages as product surfaces because of how cleanly they’ve separated status, category, API, examples, accessibility notes, theming & tokens, and icons.⁵

Crayons reinforced the no-build path, keeping static HTML as a first-class consumer, CSS custom properties should carry customization.

Framework wrappers can wait until the custom elements are worth wrapping.⁶

Icons

The W1C icon set is one named set. The Windows-like file, app, desktop, and window icons cite Wikimedia Commons Microsoft icon references as visual inspiration.⁷

Plain action, formatting, status, and object symbols come from Bootstrap Icons.⁸

The icon renderer follows the practical IconData shape used by Iconify-style data, with attributes for inner SVG body, optional viewBox geometry, and a single trusted data object passed to a component.⁹

Classic Mac

System.css shows how far plain CSS can go with monochrome controls, menu bars, windows, dialogs, titlebars, and form elements.¹⁰ Its repository also gives W1C a concrete license and font checkpoint for the Mac-facing work.¹¹

AjaxIronside built a compact reference for classic Mac menu, link, and window composition, useful because it is small enough to inspect as a whole.¹²

Brian Benchoff’s System 7 writeup is broader, with active and inactive windows, desktop state, z-index, scrollbars, 32x32 icons, and the difference between recreating an operating system and building a web page that borrows its habits.¹³

Color and theme tokens

W1C themes are hand-authored CSS token sets.

Reasonable Colors helped with predictable named color scales and readable shade jumps.¹⁴

Uchu helped with perceptual color thinking where the theme needed more life than a default web-safe palette.¹⁵

The result is simply readable variables first, generated token pipelines later if a project ever needs them.

Web 1.0 and Geocities

The early-web layer comes from personal pages. GeoCities, Tripod, Angelfire, and neighborhood-style URLs gave the web a visible sense of place.¹⁶

Early web design also left behind a somewhat eclectic recognizable culture with framesets, tables, spacer GIFs, image maps, proprietary browser tags, and the later move away from table-based layout.¹⁷¹⁸¹⁹

Wired’s farewell to GeoCities captured how much of the personal web disappeared when those hosted pages shut down.²⁰

The modern indie-web revival shows why people still miss sites that feel owned, specific, and a little strange.²¹