Notes · Nov 5, 2026 · 1 min read

Why my portfolio is a window manager

Most "OS in the browser" portfolios are a gimmick: a desktop wallpaper and a few fake apps. I wanted the opposite: a real framework where my site is just one of its clients.

Keep the core neutral

The rule for the core package is simple: would a third-party developer expect this in a reusable workspace framework? Window management, plugin lifecycle, the event bus and adapter interfaces pass. My CV, projects and branding do not, so they live in this app instead.

Dogfooding finds the gaps

Building this site exposed missing framework features right away. Launcher icons were a hardcoded switch, so plugins could not bring their own. The host app could not reach the runtime to sync windows with the URL. Both are now public APIs, covered by tests.

— Avetis Manucharyan, avet.dev