ALEXANDRE (@alexherbigneaux) – Framer Community

ALEXANDRE

Designer and Framer builder behind MASH, creating brand systems, websites, and Framer supplies for studios, portfolios, and visual brands.

ALEXANDRE3d

Finally starting work on my own portfolio.

About time.

ALEXANDRE2w

Just pushed a small update to Better Parallax.

It now includes a new Autoplay switch, requested by several users.

External video URLs remain available for CMS workflows, with stricter handling for reliability and security. Better Parallax now accepts direct HTTPS MP4 or WebM files hosted on Framer, Cloudinary, Mux, or Supabase. Invalid sources safely fall back to the poster without triggering an external request.

I’ve also pushed the optimization further: supported browsers such as Chrome now use native CSS scroll-driven animations, reducing JavaScript workload. A reliable JavaScript fallback remains available for other browsers.

More improvements coming soon.

ALEXANDRE2w

Been building this quietly for a while. Thought I’d put one frame out there.

ALEXANDREin Marketplace·3w

Made a small new Framer component: Better Parallax

Mostly because I was tired of rebuilding this on every site.

It’s just a clean image/video parallax block, but with the boring parts handled: lazy loading, poster fallback, video mounting, canvas/static/reduced-motion states, shared scroll updates, radius, direction, etc.

Nothing overbuilt. Just a better default when a page needs a bit of scroll depth.

Grab it for free below.

Better Parallax·Component

ALEXANDRE1mo

Had a brand direction project with Compound, an early-stage French soda company.

I wanted to see if I still needed Figma for this kind of work, so I did the whole thing in Framer.

Turns out, not really.

With a few tricks, I can pretty much do whatever I want from here now.

ALEXANDRE1mo

Better Grain update.

I optimized the texture system further so it holds up better across real Framer pages.

The main change: Better Grain now uses reused WebP texture assets instead of per-instance noise generation. Static mode uses embedded WebP tiles. Animated mode uses WebP sprite sheets, stepped CSS motion, viewport-gated animation, and static fallbacks for canvas, static render, restricted render, and reduced motion.

I stress-tested 100 placements on one page under 20× Lighthouse CPU throttling. Because the same texture assets are reused across placements, the page does not generate 100 unique noise layers. In that setup, the 100 placements resolved closer to 2 reused texture sources than 100 separate generators.

Grab it here: