my old portfolio was fine, but it felt a bit boring like a resume. i wanted to create a space that actually represents who i am. not just a resume, but a place for my thoughts, interests, and of course, my code.

how it works

went with astro for static generation. content lives in markdown files, making updates simple. tailwind css handles styling. site has sections for projects, work experience, and blog posts (i call them thoughts).

content structure uses collections with type validation. keeps things organized and prevents breaking changes.

cinema

added film tracking because, well here’s the full story if you’re curious.

used tmdb for film data, it’s also used by letterboxd. loading many posters from tmdb urls at once was hitting rate limits and some posters wouldn’t load. so i wrote a prebuild script that fetches posters, processes them with sharp to optimize file sizes, and uploads them to r2. caching system skips already-processed films on new builds, improving build times. so in the markdown file i just put the tmdb id of the film, the prebuild script and astro handles the rest.

it was a great opportunity to learn gsap. i used it for poster expansion animations (css transitions weren’t enough). i also implemented virtual rendering for the grid to keep it performant.