The developer.exe component library is a set of five purpose-built React components that together produce the retro arcade aesthetic of the portfolio.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/developer-exe/llms.txt
Use this file to discover all available pages before exploring further.
PixelButton handles all interactive call-to-action surfaces with neon glow and pixel-art borders. GlitchText animates headings and labels with a chromatic-aberration glitch effect. HUD locks a heads-up display bar to the top of the viewport, showing the current route as a game level alongside a live clock and score. CRTOverlay layers a full-screen scanline grid and radial vignette over everything to simulate an old CRT monitor. SynthwaveGrid renders the full-screen hero background: a sky gradient, animated floating particles, a neon horizon line, and the infinitely scrolling perspective grid floor.
PixelButton
Arcade-style button with four neon glow variants
GlitchText
Animated glitch text with optional hover trigger
HUD
Fixed heads-up display overlay with live route and clock
CRTOverlay
Full-screen CRT scanlines and vignette overlay
SynthwaveGrid
Full-screen animated synthwave hero background
Component dependencies
| Component | Framer Motion | React Router | React state |
|---|---|---|---|
| PixelButton | ✅ motion.button | — | — |
| GlitchText | — | — | ✅ hover toggle |
| HUD | ✅ motion.div entrance | ✅ useLocation() | ✅ clock interval |
| CRTOverlay | ✅ AnimatePresence (glitch flash) | — | ✅ glitch toggle |
| SynthwaveGrid | ✅ motion.div (floating particles) | — | — |
Usage patterns
Layout-level components — add once at the app root:CRTOverlay and SynthwaveGrid are full-screen, absolutely/fixed-positioned layers. Mount each of them once at the root of your application so they span the entire viewport. Duplicating them will stack their visual effects.
Inline components — use freely inside page components:
PixelButton and GlitchText are inline elements that can be placed anywhere inside a page or section component. They carry no layout side-effects and compose naturally with Tailwind utility classes via their className prop.
Router-dependent components:
HUD must be rendered inside a React Router <Router> context because it calls useLocation() internally. Place it as a direct child of your router wrapper, before your route definitions, so it persists across page transitions.