Building a tailor's website

A tailor is a good teacher for a web studio, because a tailor already knows the thing we keep having to relearn: the fabric decides half the garment, and no amount of finishing rescues the wrong cloth. Most of these notes are versions of that.

The first build shipped with tasteful placeholder imagery. It looked fine, and it was quietly lying — every frame said "stock," and a walk-in customer can smell that. When the owner sent twenty-one photographs from the actual showroom and two phone videos, we replaced every image. Trust went up the moment the pictures stopped being perfect and started being true: the real bilingual signboard, the fabric walls, actual customers in their finished garments.

Real assets don't just look better; they impose honesty. You can't caption a photo with a detail it doesn't contain. We deleted invented "pattern-tag" captions because the new photos didn't show tags. The rule that fell out of it: write alt text and captions to what the frame actually holds, nothing more.

One of the videos arrived as 258 MB — 4K, sixty frames a second, seventy-six seconds of a slow pan. Beautiful, and completely wrong for a phone on a wedding-hall Wi-Fi. We trimmed it to the twenty seconds that earned their place, dropped it to 720p at thirty frames, muted it, and it became a 2 MB loop that only loads when it scrolls into view. A poster frame stands in until then.

Fast and real are not opposites — but you have to do the work to keep both. The heavy source stayed the source; the web got the honest, light version.

The name moved under us three times. It began as the studio's own name, then became the fabric marque it's an authorised showroom for, then settled on the marque leading with the studio name as a qualifier beneath it. Each pivot could have meant hand-editing eight pages of headers and footers.

It didn't, because the wordmark and the signboard lived in one block that we changed with a single scripted pass across every page. A brand that can move should be built to move — one source of truth, one edit. The companion lesson is restraint: don't gold-plate a lockup before the name has stopped changing. We polished it after it settled, not before.

The big passes — swapping the photos, rewriting eight pages for local search, building three landing pages — went fastest as parallel work, one worker per page, each reading its own context and writing to it. But anything that must be identical everywhere — the header, the footer, the branding, a cache rule — we never fanned out. Identical work goes through one script; it's the only way to guarantee it's actually identical.

And every fan-out earned an adversarial pass afterward: a separate reviewer whose only job was to find where the parallel work had drifted or overreached. Parallelism buys speed; verification buys the right to trust it. More than once the reviewer caught a placeholder left behind, a schema that didn't match its visible text, a keyword pushed one notch past natural.

A mobile render looked broken — text clipped at the right edge, an unmistakable overflow. We nearly "fixed" a bug that didn't exist. The truth was in the harness: the headless browser had quietly clamped the viewport and a scale-factor flag had stretched the canvas, so the screenshot lied about the layout. Measuring the page directly — its scroll width against the actual viewport — showed zero overflow.

A screenshot is evidence, not proof. When something looks wrong, instrument it before you touch it. Half the "bugs" are the ruler, not the wall.

The owner had a list of phrases to "rank number one for, everywhere." Some were winnable — the hyper-local ones, the neighbourhood and the street. Some needed a page of their own before they could rank at all, so we built those pages. And some — the national "top ten best" listicle terms — a single-location tailor will never win, and chasing them only wastes the effort that could win the others. We said so plainly and dropped them from the target list.

Two things worth carrying out of that. First, the website ranks in the search results; the business profile ranks on the map — they're different systems, and reviews and proximity drive the map more than any tag you can write. Second, we refused the theatre: no keyword-stuffing, no invented reviews, no star ratings without real ones behind them. An adversarial audit — six independent critics, each attacking a different angle — kept us honest and found the one genuinely broken thing (canonical URLs that didn't match how the host served them). Blunt truth ages better than optimistic keywords.

No prices, no fabricated testimonials, no claims the shop couldn't stand behind — and, because the brand belongs to someone else, a plain line naming the studio as the operator and authorised showroom. None of this was a legal afterthought bolted on at the end; it was written into the instructions every worker followed and checked in every verification pass. The guardrails that keep a site truthful are cheapest to install while you build, and most expensive to retrofit.

Everything above was the site. Getting the site to actually live at its address took nearly as long, and it's the part nobody budgets for. In order: a new .in domain won't do anything until its WHOIS contact is verified; changing the registrar's nameservers is not the same as attaching the domain to the host; and the host won't serve it until a DNS record points back at the project.

The sharpest trap was a permissions one. The machine's logged-in session could deploy the whole site and register the custom domain from the command line — but the same token was refused when it tried to write a DNS record. The credential that ships your code is not always the credential that edits your DNS. Knowing exactly where an authenticated session's power ends saved an hour of confusion; the last record went in by hand, and the certificate issued itself a few minutes later.

Every interim deploy went to a private, no-index staging URL — reviewable, never indexable — so the search engines only ever meet the finished room. Production waited until the domain resolved, with canonical URLs written to match exactly how the host serves them (clean, no file extensions) so authority never splits between two versions of the same page. A soft launch is a launch with the door still shut. Open it once, deliberately, when the room is ready.

The website was a weekend of HTML. Making it true, fast, findable, compliant, and genuinely live at its own name was the month. A tailor would recognise every step of it: choose the right cloth, measure the real person, cut once, check the fit before you finish, and don't hang the sign until the shop is actually open.

Names and specifics are genericised, as always. The craft speaks without them.

Postscript: the sign is up and the shop is open — the finished site is live at bespokestudio.co.in.