At 1:32 in the morning, we decided to turn our entire homepage into Halloween. By 2:45 it was live — dressed head to foot, approved by the man who ordered it, and built so the real site underneath never moved.
The band above is the live dressed hero exactly as visitors met it on Halloween night — garland, moon, and the Big Candle seated in the cemetery, over the hero video still playing behind the dressing.
1:32 AM
The ask lands — homepage only, one night only
2:45 AM
Live — asked for, approved, and up in one morning
2 moves
The whole conversion: orange treatment + elements placed into open space
11:50 PM
Teardown fires on schedule — the site wakes up clean
One night only. This page is the receipt.
The ask
The brief, sharpened within minutes of landing at 1:32 AM: a full Halloween background — moon at the top, a haunted house at the foot — orange stroke and glow replacing the blue, links orange, readability untouched, and nothing launches until the Chairman approves the visual. Homepage only. One night only. The design desk's first take was tasteful and light — and too light. The second went the full ask, and failed as a delivery: built as one tall file, it reached the Chairman's phone as a hairline on black. That failure wrote a standing studio rule before the night was out — full-page visuals are never delivered as one tall strip again.
2:10 AM — the turn: his design
Then the Chairman brought his own design — a render he had generated in Gemini. His words: “This is the design I would go for.” The desk's flat work was set aside without argument, and his render became the bar for richness. The feasibility check came back with the discipline that made the night work: the conversion was two moves only — the orange treatment, and his elements placed into the page's open spaces. No layout changes. No content changes. No structure changes. The page's bones never moved again.
The spark. The Chairman's own Gemini render, shown contained at its native width — the share served it 228 pixels wide, and it is framed here as what it is: the seed document the whole night grew from.
Five pictures, one argument
It starts with the Chairman's render. Then our first attempts, including the one that failed in his hands. Then the reset: his design recreated on the real page — four painterly scene pieces generated in-studio (a garland, a cemetery, a haunted house, a pumpkin cluster) composited onto the untouched homepage. Then the same page with Kristen's touches. Then the final. Nothing here is a mock-up of the work. It is the work, in the order it happened. Tap any frame to open the full comp.
v1 — the light dressing. Pulled back: too light.v2 — the full night. The tall-image lesson.v3 — recreated from his pick, on the real page.v3 + touch — light spill, bat line, fog seams, last-frame pumpkin.Final — plus the Big Candle and the corner fix.
The same two moves at desktop width — v3's treatment on the desktop structure, in a scroll window. This is the version the Chairman approved at 2:25 AM: “I really like it. So let's go with this.”
Full reign, and a really big candle
With v3 approved, his extensions arrived as placement calls, not rebuilds: all the blue text goes orange too (a full sweep after the build found zero blue text remaining; the FS logo mark stayed blue by his explicit word — a graphic, not text), the card highlight glow turns orange at identical strengths, more jack-o'-lanterns on the cards, the page numerals orange with their transparency untouched. Then he closed his guidance:
“I've given all the guidance I want to give on this. I give you guys full reign.” — with one seed: a really big candle, off to the left a little
The candle was generated in-studio, silhouette-cut, and seated in the cemetery's left foreground as a vigil light. Its flicker system animates opacity only — no cycle under about four seconds, every layer desynced, and reduced-motion settings switch it off entirely; twenty-three layers of it were live that night. Design's verdict on the animation, after reading it on the served page: honest candlelight, not cheesy — it shipped animated.
His closing fix, at 2:37 AM: the Junipero banner and the BMA band carried square corners while everything else on the page was rounded — round them. That one was built permanent. It is the single piece of Halloween night still on the site today, deliberately: it outlived the costume because it was never part of the costume — it was a fix the night happened to surface.
And the build itself is why the whole thing could move at this speed: the dressing lived in one marked block inside the site's shared stylesheet and script, gated to the homepage alone. The homepage file itself was never edited. Dressing the site was an addition; removing it would be a restore — not a rebuild, not a rescue.
The seed he gave — the Big Candle as generated, before the silhouette cut.Its seat, live on a phone — the candle in the cemetery's left foreground, the hero video still playing behind it.
The night, in receipts
1:32 AMThe ask lands: dress the homepage only, one night only — really go at it. The spec sharpens minutes later: moon top, haunted house at the foot, orange over blue, readability untouched, approval before launch.
1:44 AMv1 is superseded by v2 in the same push. v2 fails in the Chairman's hands as a tall-file delivery — and the tall-image rule is written and adopted within the hour.
2:10 AMThe turn: the Chairman brings his own Gemini design — “This is the design I would go for.” His render becomes the richness bar.
2:11 AMScope is clarified and held exactly: two moves only — the orange treatment, and his elements into the page's open spaces. Kristen is licensed to put her touch on it before it reaches him.
2:25 AMv3, recreated from his pick with Kristen's touch applied, is approved: “I really like it. So let's go with this.” Build order issued.
2:29 AMFull reign granted — one seed: a really big candle, off to the left a little. The candle is generated, seated as a vigil light in the cemetery's left foreground, and the flicker system is specified: natural, not cheesy.
2:37 AMHis closing note — “Everything looks great” — plus one fix: round the Junipero and BMA band corners. Built permanent.
2:45 AMLive. His verdict: “the desktop looks pretty good so far. It really looks good I'm pretty impressed… good job guys really good job I'm really impressed.” Minutes later, on the phone version: “still looks good on mobile too.”
11:50 PMGone — down the same night it went up, on schedule, verified: the restored files' checksums matched the pre-dressing backups exactly. The homepage woke up the next morning as itself.
The live tour
The dressed page, section by section, as it actually served that night — desktop detail first, then the phone frames in page order.
The orange glow system, desktop. A work card caught in its hover state — the site's blue highlight glow, orange for the night at identical strengths, verified live.The page top. What a phone visitor met first: the garland, the moon, the orange headline over the live hero.The Junipero Band. A client's banner wearing the season — with the Chairman's last fix visible: corners rounded, permanently.The Work Cards. The portfolio in costume: jack-o'-lanterns nested on the frames, numerals turned orange at their original transparency.The Closing Panel. Where the page asks for your business, it asked in orange that night — not one blue letter left standing, by sweep, not by eye.The Footer. Every dressed page needs its last word. Ours was a haunted house at the foot of the page, exactly where the design put it.
The whole night, top to bottom
The dressed homepage exactly as it served — the full page inside one scroll window, at natural width for the screen you're on. Scroll it like a page.
The dressed page, whole — captured live on Halloween night; fixed furniture shown once at the top so it doesn't stripe the record.
Flip it. Nothing moves.
Same homepage, same widths, same scroll positions — the clean page and the Halloween page, captured as matched pairs and registered against each other: in a 50% crossfade of the two states, every headline, button and band sits pixel-true and sharp; only the dressing fades. That's the point of the trick. The theme was a costume; the body underneath never changed — the homepage's own file was never edited at any point in the build. (One honesty note: the page is animated — a ticker, a pulsing logo, the candlelight — so those elements sit wherever their cycle was at the moment each state was photographed. That is inherent to photographing a living page.) The desktop toggle leads, as the night did; the phone pair is beneath it.
Showing: the clean page · desktop, 1440px
The desktop pair — 1440 × 14,123 pixels in both states, one shared slice list. The before image sets the frame; the dressed layer is locked to its box.
Showing: the clean page · phone, 390px
The phone pair — 390 × 19,902 pixels in both states. Same registration check, same result.
What the night proves
The Chairman's own generated design beat the desk's two attempts — and the desk's job got better the moment it switched from inventing to interpreting: his richness, our structure, his rules.
Every ruling after the turn was a placement decision, not a rebuild. The page never changed bones once — which is precisely why a full holiday conversion could be designed, approved, built and retired inside a single day without ever putting the underlying site at risk.
The night's two failures — the flat first attempts and the tall-image delivery — were both converted into standing studio law before the night ended.
And approval-to-live ran on receipts at every desk: nothing was claimed done without a sighting behind it.
Fast on. Fast off. Nothing underneath disturbed.
The discipline was the design. The Halloween layer lived in one marked block of the site's shared style and script files, gated to the homepage alone — the homepage itself was never opened. So the teardown was a restoration, not a demolition: at 11:50 PM the pre-dressing backups went back, and the verification is on record — the live files' checksums matched the backups to the character, no Halloween markup served after, the blue ghost wordmark back in the footer where it belongs. What was meant to survive the night did: the article shelf, the lead system, and the rounded corners. Everything else — garland, candle, fog, pumpkins, orange — now lives only here, in the captures on this page. The dressing's image files remain on the server, unreferenced: a costume in the closet.
One night, worn once, retired on schedule. That's the discipline the case study is really about: the exit was planned before the entrance — and it fired to the minute.
