Platform Architecture

This site runs on the architecture it documents: a small core platform that treats every project demo as a plug-in module. Each module ships a manifest describing its name, category, and entry point — the registry collects them at startup, and everything else, from the tools grid to the diagram above, is derived from that single source.

Module code stays out of the main bundle and is fetched only when a window is opened, so a heavy demo never slows the first paint. The desktop metaphor comes from shared services — the window manager, terminal, ⌘K command palette, and a global keyboard handler — that modules consume through a small SDK instead of importing each other.

The Core Platform handles routing, module discovery, and lazy-loading. Services provide shared capabilities like the terminal, command palette, and window management. Each Module encapsulates a distinct tool — from an X-ray classifier to a Raft task queue — loaded on demand to keep initial bundle size minimal.