Skip to content

Live · client self-publishing

Global Jute Trading

Editorial export site for Global Jute Trading Ltd — a Dhaka-based sourcing & exporting house with 26 years as a company and 35 years of jute trading under its principals. Built to support their push into deeper international markets, with a particular focus on Toronto, Canada.

Role
Lead Architect & Engineer
Period
2025 — 2026
Stack
TanStack Start · React 19 · TypeScript · Tailwind v4 · and 6 more
Place
serving global importers
Homepage — "Bangladesh jute, sourced to spec." Editorial hero with the Dhaka warehouse floor and the 35 yrs / 7 lines / 4 continents stat band.

Homepage — "Bangladesh jute, sourced to spec." Editorial hero with the Dhaka warehouse floor and the 35 yrs / 7 lines / 4 continents stat band.

26Years (founded 2000)

Bangladesh jute is one of the most specification-sensitive commodities in global trade — GSM ladders, hessian vs sacking vs felt, treatment, certification, packaging, lamination. A serious importer in Canada or Switzerland can't evaluate a supplier from a brochure of stock photos and a phone number.

01 / 03

The problem

Global Jute Trading needed an editorial-grade catalogue that read like a specification sheet, not marketing — one a procurement lead could send up the chain at a mill, cooperative, or geotextile contractor.

Markets — "Four continents. 18+ countries." d3-geo + topojson maps with Americas & Canada called out as the growth corridor.
02 / 03

What I built

  • Specification-first product catalogue. MDX-authored product pages with GSM bands (Light, Heavy, Industrial), certifications, mill provenance, and per-category process notes — every claim sourceable.
  • Markets directory. A per-country / per-vertical map of where the company ships and to whom across five continents (Africa, North and South America, Europe, Asia and Australia), with bag, sacking and cloth programme specifications per region, built from a topojson world atlas and editable content data.
  • Process page. The full sample-first workflow: bale sample → swatch approval → grade certificate → phytosanitary → container booking. Buyers can read the answer before asking.
  • AVIF + WebP responsive image pipeline. Editors drop in a photo and a GitHub Action makes every size: 480, 768, 1200 and 1920 widths in AVIF and WebP, with a blur placeholder, so no one on the client team installs a build tool.
  • TanStack Start on Cloudflare Workers. SSR-rendered at the edge with file-based routing and JSON-LD baked in for every product and market — built to be readable by importers and indexed by everyone.
  • A Claude-powered natural-language CMS. Instead of a traditional CMS, the client describes the change they want in plain English; Claude turns it into a pull request and the CI/CD pipeline ships it to production. Self-serve content and marketing edits with no developer middleman — every change stays inside Git, reviewable and revertible. The ownership team can refresh brand offerings and go-to-market copy on the spot, without a ticket queue or a business-team handoff. In its first eight working days the client team shipped 36 changes this way without a developer edit, and four CI gates (content schemas, type checks, tests and a prerender build) guard every one.
  • Pages that answer the buyer. A founder story, case studies, an HS-code specifications page and a page per trade membership.
Specifications — HS code reference. Spec-first IA: every product line listed against its six-digit international classification and product description.
03 / 03

What I learned

A 25-year-old trading house has more institutional knowledge than any tech-first brand I've worked with.

My job was to translate that into a surface — not to invent positioning, but to organise it: principles, mill specialisations, sample workflow, documentation guarantees.

International expansion isn't a homepage problem; it's a specification problem. The pages that did the most work were the GSM bands, the markets index, and the process page — the ones that let a procurement lead self-qualify before sending an email.

The legacy-to-AI shift landed emotionally, not just technically. The client team rejoiced once they realised they could go from thought to market-ready content on their own — the eye-opener wasn't the model, it was removing the old dependency on developers and business desks for every brand change.

Contact — "Source your next shipment." Forest-deep contact surface with WhatsApp + email CTAs, office address, and trade-body footer signals (BJGEA · EPB · SCB · DCCI).

Decisions and why

  1. MDX over a headless CMS

    WhyA 25-year trading house edits its catalogue in months, not minutes. Authoring in MDX keeps every spec change inside Git, reviewable, and free of CMS lock-in.

  2. A Claude-powered natural-language CMS on top of MDX

    WhyRather than teach the client Git or hand them a heavyweight CMS, a Claude layer turns plain-English edit requests into pull requests that trigger the CI/CD deploy. The client self-serves marketing and content changes — from thought to market-ready pages without waiting on developers — while every change still lives in Git, consistent and revertible. For a legacy export house, that independence was the real adoption win.

  3. Edge SSR on Cloudflare Workers

    WhyBuyers land from Africa, the Americas, Europe and Asia. Static SSR at the edge gives every region the same first-paint, with zero origin server to babysit.

  4. Specification-first IA, not marketing-first

    WhyThe visitors who matter (procurement, mills, contractors) want GSM and certification before brand story. Information architecture inverts the typical homepage hierarchy on purpose.

Technical highlights

  • 01

    TanStack Start (file-based routing + SSR) on Cloudflare Workers — global edge delivery.

  • 02

    MDX content pipeline with remark-frontmatter for editorial product pages.

  • 03

    Sharp-driven AVIF + WebP responsive image pipeline, run in CI so editors never install Node.

  • 04

    d3-geo + topojson world atlas for the live international markets map.

  • 05

    Tailwind CSS v4 with a custom forest-deep / paper palette tuned for editorial weight.

  • 06

    Zod content schemas and four CI gates on every pull request.

Impact

  • Supports a deliberate push into deeper international markets — Toronto, Canada especially — with a surface importers can self-qualify on.
  • Reduced the buyer onboarding loop: spec, process, and markets are documented enough to short-circuit early discovery calls.
  • Established a modern editorial brand for a 25-year-old trading house without abandoning the trust signals (founding year, address, principals) that anchor B2B credibility.
  • Gave the client team self-serve publishing: thought to market-ready content without developer queues or business-team handoffs for every brand change — the legacy-to-AI transition became a genuine eye-opener for how they operate day to day.
Outcomes

By the numbers.

7
Product categories
18+
Countries shipped to
Visit project

See it in the wild.

This case study covers how Global Jute Trading was built — these links open what ships today: the live product, repo, demos, and supporting material.

↗ Next case study

TagRamp

A new LinkedIn for orgs that actually deal. TagRamp connects organizations from goals to meaningful business deals through AI-mediated intros. Built solo during the World's Largest Hackathon (May 2025) by Bolt.new and submitted to Y Combinator. The build is paused, and the intro reply rate it reached is what the experiment proved.