How robbiebyrd/classicy works
Project type and purpose
• This is a React-based UI framework and demo application (“Classicy”) built on Next.js.
• It provides a library of Mac OS 8–style components (Desktop, Finder, Windows, Buttons, Menus, etc.), plus a reference Next.js app to demo them.
File structure
• Top-level:
– package.json, next.config.js, tsconfig.json → Next.js + TypeScript configuration
– .github/workflows/nextjs.yml → CI/CD pipeline (build & deploy)
– bin/make_audio_sprites.sh → build script for generating audio sprites
– jest.config.ts, src/tests → unit test setup with Jest
• public & resources → static assets (images, sounds, fonts, theme JSON, exports)
• src/app → Next.js “app” directory containing both:
– /Applications → example apps (Browser, EPG, News, TV, etc.)
– /SystemFolder → core framework components (Desktop, ControlPanels, Finder, QuickTime, SystemResources subcomponents)
• src/globals.module.scss, component .module.scss files → theming and styling via CSS Modules / SASS
Extracted insights from README
• Tech stack: Next.js, React, TypeScript, SASS, Jest, Yarn, GitHub Actions
• Architecture overview:
– <ClassicyDesktopProvider> supplies global system state (themes, sounds, active app/window)
– Individual <ClassicyApp> instances host <ClassicyWindow> children, which host UI controls
– React Contexts + event dispatchers manage theme changes, window focus, drag/resize, sound events
• Extensibility: Apps plug in via Context, static assets are consumed at runtime, themes defined in JSON
Essential details to capture
• The separation between build/CI, server, and client layers
• The top-level DesktopContext feeding into nested components
• The plugin relationship: Desktop → Apps → Windows → Controls
• The event-reducer loop for theme changes, window focus, sound playback
• Static asset hosting and consumption