ReactCreate React Appstyled-componentsGSAPLenisReact Router

This was the previous version of cleof.us, a single-page React portfolio built with Create React App, styled-components, GSAP, and Lenis. The whole thing was built around a custom LED-matrix background (LedGrid) that lit up across the page behind the hero, project highlights, about section, tech stack, and contact form.

Before this, my projects and background were scattered across GitHub, resumes, and one-off links, and there was no single, memorable place that represented me. A generic portfolio template would have solved the 'have a link to share' problem but not the 'make it feel like mine' one.

A user-configurable LED grid instead of a static hero background

LedGrid.js rendered a full-page grid of glowing dots, and a SettingsModal let visitors pick the LED color (purple or green) and the animation mode themselves: cursor-follow (desktop only), matrix rain, wave, or none.

Reason:
A static gradient or hero image is forgettable. Letting visitors tweak the background turned a decorative element into something people would actually notice and play with.

Tradeoff:
Hand-rolling multiple animation states and a settings UI took a lot longer than dropping in a pre-made background library, and cursor-follow only worked on desktop, so mobile visitors always got a fallback animation.

styled-components, GSAP, and Lenis on top of Create React App

Theming ran through a ThemeContext and styled-components (AppContainer and friends), scroll and entry animations through GSAP, and smooth scrolling across Hero, AboutMe, ProjectGrid, TechStack, and Contact through Lenis.

Reason:
CRA doesn't come with any styling or animation opinions, and this combination got me a really custom, animated feel without adopting a heavier design-system framework.

Tradeoff:
The CRA + styled-components + GSAP bundle is heavier and slower to iterate on than a Next.js/Tailwind stack, which was part of the reason for the 2026 rebuild.

Shipping a DeprecationModal ahead of the actual rebuild

The old site had its own DeprecationModal component that told visitors an overhaul was coming, instead of letting the site go stale without saying anything.

Reason:
If a redesign is already planned, it's better to say so than to let visitors assume an old-looking site is just unmaintained.

Tradeoff:
A visible "this is getting replaced" notice can undercut confidence in the current version while people wait for the rebuild.

  • Was the live personal portfolio at cleof.us until the current Next.js site replaced it.
  • Shipped a fully custom, user-configurable LED-grid background (color + animation mode) instead of a static template hero.

  • For a personal site, having a look people remember can matter more than how technically sophisticated it is.
  • By the end, CRA + styled-components + GSAP was slow enough to iterate on that rebuilding made more sense than patching it, which is how this site happened.
This was my personal site at cleof.us before the 2026 overhaul. cleof.us now points to the site you're on, so the live link above reflects wherever the domain currently resolves, not necessarily this exact version.