Maria Babo — Portfolio and shop-and-photos platform

Someone viewing a session needs to see enough to want to buy, but can't walk away with the file for free. Locked photos become a blurred preview with a repeated watermark, stored in a public bucket. Originals sit in a private R2 bucket that is never served directly: every read goes through a short-lived signed URL, generated only after the server checks that the photo was unlocked or paid for.

The amount never comes from the client: the server computes it from the configured price. Confirmation arrives as a Mercado Pago webhook, which the API validates by recomputing the HMAC-SHA256 signature over the id, request-id and timestamp, with a constant-time comparison. Only then does the API query the payment on Mercado Pago's own API instead of accepting the status in the notification body, and ties it to the shop order or the session payment through the external_reference.

The reference is a design export, not the previous site. Scripts normalize each export into a versioned snapshot and produce a diff report between versions before any code is written. Images become WebP and the grid pages are generated from files that aren't edited by hand. Each project's content is data, and the pipeline runs types, lint, build and end-to-end tests on every landing change.

The frontends ship to Vercel on every push to master. The API is only redeployed when its paths or the database and storage packages change: the Action enters the VPS over SSH, rebuilds the image, applies the Prisma migrations and brings the container up. The API's rate limit is in memory, per IP, enough for a single process, and the code notes that it would need to become something shared if the API scaled out.