Web / 2026
The visual language started in Figma: oversized type, a lot of black, acid green and pink. The real questions showed up in the browser. What happens when a headline changes language? Where does a card land on a narrow screen? How long can an intro run before it becomes the thing you want to skip? Most of the useful decisions came from tuning rhythm and proportion while using the actual site.
GSAP runs the opening wave, reveals, counters and small pointer reactions. Lenis handles smooth scrolling and stays synchronized with ScrollTrigger. I didn't want every empty space to move. The animations that stayed either introduce a section, explain a change or make an interaction feel better. Everything else is just noise.
Spanish isn't a button that swaps text on top of the English site. It has its own routes, metadata and shareable case-study URLs. The browser suggests a language on the first visit; after that, the visitor's choice wins. I also rewrote the copy to get rid of portfolio filler and keep the kind of voice I would actually use outside this page.
Astro generates static pages so the content arrives quickly and is readable in the initial HTML. React only stays where interaction needs it. The site also has canonicals, hreflang, structured data, a sitemap, social previews, keyboard navigation and a reduced-motion mode that never hides the content. It isn't the flashy part, but it is what keeps the site from falling apart outside the demo.
It's called Folio 2026 because it is no longer that first version, and because I don't want to freeze it as a finished piece. Projects and images will change, and a few decisions that feel brilliant today probably will too. That's part of the point: the site also records how my judgment keeps changing.