Site Slap Devlog #5 (it ships today)
TL;DR
- the popup got its brain: it renders your actual upgraded site now, written by Claude Haiku, shown in a sandboxed iframe
- went through three ai models to kill the slop. the free ones couldn’t write html
- final polish landed: tab name, hand favicon, pulsing dots pulling people to the better skins
- found out the site was invisible to everyone except me. fixed an hour before shipping
- site slap is live. link at the bottom. go get roasted.
the upgrade renderer
the moment your slap result lands, two requests fire in the background, one per tier. by the time you scroll down and hit view
upgraded, the redesign is already sitting there.
Claude Haiku gets the screenshot plus the fixes and writes your site back as one self-contained html file. no javascript allowed,
and the iframe’s empty sandbox attribute makes sure it wouldn’t matter anyway. prompts are requests. sandboxes are enforcement.
the roasts still run free on groq. scoring doesn’t need the muscle, writing html does. about three cents per render, daily capped
so a viral day costs me a dollar and not my whole balance.
three models and a thumbnail trick
groq’s scout wrote the first upgrades. overlapping headlines, floating color blocks. i gave it a page of design rules. still slop.
maverick was better and slower. haiku ended the argument.
the other half of “broken” renders was my fault: the model writes desktop css and i was rendering it in a 670px frame. now the
iframe is actually 1280px wide and a css transform scales it to 52%, like a thumbnail. layout at real size, display at small size.
best bug of the week: one render had perfect nav links next to three giant ugly buttons. turns out buttons don’t inherit fonts.
browsers give buttons their own default font unless you write button { font: inherit }. that reset is now a mandatory line the
model must paste, not a rule it might remember.
the launch blocker nobody saw
an hour before shipping, i checked the live url from outside my account.
login page.
vercel’s deployment protection was walling everything, production included. i’d been looking at my site logged in for days, seeing
it fine, while every public url served a vercel login screen. the site worked perfectly and nobody on earth could see it.
one setting flipped, one clean domain added, and then a real test from the outside: curl the live api, no cookies, no login.
example.com came back with a 40 and “barely functional, utterly forgettable.” the renderer returned real html with the viewport
meta exactly where the prompt demands it. green across the board.
you and the public do not see the same internet. test logged out.
thank you
this project went from “paste a url, get roasted” scribbled in a chat to a three-skin app with an ai design critic and a popup that
redesigns your site in front of you. five devlogs, three dead heroes, two ai providers, one rem/em bug i will never make again.
thanks to Hack Club and Stardance for the reason to ship instead of endlessly polish. thanks to everyone who read these devlogs and
watched the thing grow. and thanks to arngren.net for being the calibration anchor no prompt could do without.
it ships.
Tip of the Day
open your deployed site in an incognito window before you share it anywhere. logged-in you and the public are two different
visitors, and only one of them matters on launch day.
🖐️ go slap your site
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.