no-code.supply is open.

I've been quietly building landing page templates. Six are out today, each with its own brand, its own type pairing and one interaction it's built around:

→ Aurel: a skincare brand with a WebGL serum drop that bulges toward your cursor → Ferro Type: a type foundry where the hero word bends its weight and width under the pointer → Meridian Expeditions: contour maps that redraw themselves as you switch routes → Oda: an architecture studio whose timber cabin draws itself, with a live sun study → Relay: a dev tool where the editor types a workflow and the run graph executes it live → Signal: a mission-control SaaS with a live infrastructure graph that contains threats as they flare

Built to be edited with AI. Every template ships with a README, a DESIGN.md and an AGENTS.md, so Claude, Cursor or whatever assistant you use changes it the way it was built, not the way it guesses.

Pricing, per template: • HTML: $29 • React: $59 • Bundle (HTML + React): $79

Or get All-Access for $169: all six templates, both editions, plus every future drop. Nine more are on the way, at no extra cost.

No page builder, no lock-in, no third-party requests.

If you build sites for clients, I'd love to hear which one you'd use first.

Ferro Type is the one I would open first. Bending a variable font under the pointer re-lays out the text every frame, which is a much bigger bill than it looks, and stepping the weight in a few fixed increments is usually what keeps it smooth on a laptop that is not plugged in....

I helped build Heap’s Developer Portal from the ground up, creating a dedicated experience for developers and partners to build, configure, and manage integrations with Heap.

Before the portal, integration development relied more heavily on internal processes and support from Heap’s team. The goal was to make the ecosystem more self-service by giving developers the tools and guidance they needed to work independently.

I owned significant frontend work across the portal experience, translating technical integration workflows into a product that was approachable, scalable, and easy to navigate. I worked closely with product, design, and backend engineering to define workflows, establish reusable UI patterns, and make the developer experience feel like a cohesive part of the Heap product.

The portal helped increase organically created integrations by roughly 40% while reducing integration-related support tickets by about 25%.

The drop in support tickets is the number I'd lead with. Curious what moved it most: the step by step setup flow, or being able to test an integration with real data before publishing without pinging your team?