LEACB: From Beta to Release

The Beginning

LEACB started as an experiment. I wanted to answer a simple question: can a portfolio be an experience? Not just a page with links and a headshot. An actual interactive, immersive, 3D environment that demonstrates what I build by being what I built.

The first prototype was rough — a floating camera, a few particles, and plain white panels in a black void. It barely worked on mobile. But the core idea was there: navigate a 3D space to explore who I am and what I do.

The Beta Phase

The beta went through three major iterations. Each one taught me something critical:

• Beta 1 — Basic Three.js scene, no post-processing, simple panels with solid colors. Looked like a tech demo, not a portfolio.
• Beta 2 — Added particles, improved lighting, introduced glass-morphism CSS. Better, but the panels were still flat rectangles that blended into the background.
• Beta 3 — Introduced EffectComposer and UnrealBloomPass. The moment bloom was added, LEACB transformed from "cool experiment" to "this could actually be my real portfolio." Also added the loading screen, HUD overlay, and mini-games.

Breaking Things

The path from beta to release was paved with broken builds. Import maps conflicting with module scripts. Post-processing passes that killed mobile performance. A particle breathing effect that caused memory leaks in Firefox. A custom cursor that didn't track correctly when the page was scrolled.

Every bug was a lesson in how browsers actually work under the hood — not how documentation says they should work.

What Changed for v1.0

The jump from beta to v1.0 wasn't one big rewrite — it was hundreds of small refinements:

• Panel textures rewritten with higher-resolution canvas, scanlines, corner brackets, and status indicators
• Bloom parameters tuned for maximum glow without visual mud
• All section overlays fixed for proper scrolling on mobile and desktop
• Blog system rebuilt with 13 posts, each with floating dot navigation and scroll-spy
• Skills orbit layout recalculated for even distribution
• FPS counter added to HUD for transparency
• ASCII art console output loaded from local file
• Cloudflare Pages deployment hardened with proper _redirects and sitemap

Design Decisions

The cyan-purple-gold palette wasn't chosen randomly. Cyan is the primary — it represents technology, clarity, and forward motion. Purple is the accent — it adds depth, mystery, and creativity. Gold appears sparingly — it marks importance: the blog panel, key highlights.

The fonts follow the same intentional hierarchy: Orbitron for display (futuristic, geometric), Share Tech Mono for technical content (terminal feel), and Rajdhani for body text (clean, readable, slightly technical).

"v1.0 doesn't mean finished. It means ready to be seen."

What's Next

LEACB v1.0 is the foundation. The roadmap includes custom WebGL shaders for dynamic backgrounds, GPGPU particle physics, per-project 3D showcases, and a potential WebGPU migration when browser support stabilizes. This is just the beginning.

Thank you for exploring LEACB. If you've read this far, you're exactly the kind of person I built this for.