Scroll → a camera flies through a watch gallery → zooms into the dial → you pick a dial colour → add to cart.

That's the homepage of AUREL, a luxury watch store I designed and built as a portfolio project. ⌚

Under the hood: • 3D scroll story with React Three Fiber, GSAP and custom shaders • Full shop flow: filters, product variants, cart, 4-step checkout • Mobile CSS 3D fallback + reduced-motion layout • Accessible, fast, and ready to plug into Shopify

Stack: React, Vite, Tailwind, Three.js, GSAP, Zustand

I'm a web developer (React · WordPress · PHP, 6+ years) looking for remote frontend or WordPress roles. Recruiters and hiring managers, my DMs are open.

#ReactJS #FrontendDeveloper #ThreeJS #OpenToWork #WebDevelopment

This is nice

I turned the checks I run on Lovable, Bolt and Replit apps into a small scanner.

Run one command in your app's folder and it lists the gaps that expose data or money, file by file: keys that end up in the browser, the Supabase service role in client code, tables without row-level security, Stripe webhooks nobody verifies, AI routes anyone can call.

It runs locally, has no dependencies, never uploads your code, and masks every key it finds. Add --ci and it fails the build when anything is red.

It is heuristics, not a guarantee. But it catches the things I look for in the first hour of an audit.

Ship Check Scanner: https://contra.com/products/dvWCzeVV-ship-check-scanner-find-the-gaps-before-your-users-do

The checklist it is built on is free: https://contra.com/products/cTLDQhiJ-the-ship-check-list-what-to-check-before-real-users-pay

What is the first thing you check before a launch?

The service role key in client code is the one I would bet most no code founders have never heard of. Honest of you to call it heuristics. First thing I check before a launch is whether the site says in one line who it is for, which is a different kind of gap but costs just as much money.