Margo Rubber

A B2B export site for a rubber-components manufacturer: eleven product categories with SKU pages, industries, an export map, case studies, resources, legal pages and enquiry forms. The Figma comps disagreed with each other and with the research pack: five different founding years, six export-country counts, three minimum order quantities, three response-time promises, four email addresses, and certifications on the about page that the client does not hold. Shipping any of those wrong would have cost the client credibility with exactly the buyers who check.

The usual answer is to ask the client and wait. The answer here was to make the contradictions impossible to ship, so that the site could be built while the answers arrived. Client work for Third Shade Media; no visuals, live URL to follow when the domain goes up.

Next.js 16 App Router with Server Components and TypeScript, Tailwind v4, an MDX content pipeline validated by Zod, migrated to Sanity as the content source in September. Neon Postgres for enquiries, Resend for notifications, sharp for blur placeholders. Every image lives in a registry with a required width, height and alt, so layout shift is impossible by type.

Typed content. One MDX file per page, one dynamic route per collection, frontmatter validated by Zod with 60- and 160-character SEO budgets. Malformed content fails the build and names the field. The legal pages are structured blocks (paragraph, subheading, list, callout) rather than prose, so a table of contents can never point at a heading that does not exist.

A facts registry with null. Founding year, street address, phone, the person who catches RFQs: every value the source material contradicted is null in one TypeScript file, with the evidence for each candidate written above it. A template that renders a null fact renders nothing. When the client confirmed the email address on 18 August, one line changed and every page followed.

Gates. check:links builds the route set from the page files and the content slugs and fails on any href outside it; on its first run it found 13 broken internal links and 23 lists keyed by href, which React would have silently mis-rendered. check:claims scans every content file for statements the client cannot make and skips a term that is named in order to deny it. check:enquiry holds 60 assertions on the map from nine forms across six pages to eight canonical database columns; it found two forms that would have posted empty. check:schema and check:blocks keep the Sanity schema and the block types in step with the code.

Enquiries. POST /api/enquiry validates, checks a honeypot, a time-to-submit floor and a per-IP rate limit, stores the raw payload as JSON in Postgres, and only then emails and forwards to a webhook seam for the client’s CRM. The durable copy is written before anything unreliable runs.

The claims gate, with a stand-in registry. Type marketing copy; the gate flags what the registry cannot support and lets through a term that is named in order to deny it.

$ npm run check:claims -- --strict

✗ line 1  "Founded in 2005"
  founding year while null: foundingYear is null in the registry: the source material gave five different years. Blocked until confirmed in writing.

✗ line 1  "60M pieces per year"
  capacity mismatch: Registry capacity is 6 million a year (500,000 a month). The proposal front page said 60M, which is a typo its own expansion section contradicts.

✗ line 1  "MOQ of 100"
  MOQ mismatch: MOQ is 500 pieces per SKU in the registry. One comp shows 100.

✗ line 1  "within 24 hours"
  response promise: The only promise the client can keep is 1 business day (IST). Nothing faster.

✗ line 1  "cutting-edge"
  marketing register: Banned register. The voice is factual-engineer; buyers who check do not trust superlatives.

✗ line 1  "Rated 4.9/5"
  fabricated social proof: Ratings and order counts with no system behind them. Explicitly banned.

2 terms named in order to deny them, skipped: "IATF 16949", "CE marking"

6 hits · exit 1  (build blocked)

I declined to draft legal copy and left those pages as structured blocks for the client’s counsel. Founding year and export counts stayed null until the client confirmed them, and the site shipped without them rather than with a guess. A capacity figure on the proposal’s front page was ten times the figure in its own expansion section; the gate bans the larger one. Where the comps invented certifications, the certifications page states plainly what is held, and the gate makes sure nothing else claims more.