Manufacturer J — An Overseas English Brand Site Built from Zero
The overseas brand lived as a section of the parent company's legacy site, with no site of its own and no English content. Starting from a single Word document, we delivered a self-maintainable English brand site and 39 pieces of content.
When a Taiwanese manufacturer launches an overseas brand, the usual first move is to give it a section inside the parent company's website. Early on that makes complete sense: cheap, fast, done. It stops working sooner than people expect, because the parent site is written for domestic customers — capacity, certifications, contract manufacturing history — while the overseas brand needs to talk to North American buyers about applications, specification equivalence, and why they should choose you over a supplier down the road.
One site trying to do both usually does neither well.
The challenge: one Word document and an old logo
When we picked this up, the overseas brand had exactly two assets: a Word document in Chinese, and an old brand mark. No site of its own, no English content, and no back end anyone could update. For a brand aiming at North America, that is starting from zero.
What we did
1. Rewrite, not translate
We started from our own site template, rebuilt the colour system, and turned nine pages of Chinese draft copy into English. Rewrote, deliberately, rather than translated. Copy for North American readers follows a different order of argument than a Taiwanese product catalogue: the local convention opens with company history and factory footprint, while the buyer abroad wants to know what problem this solves, whether the specifications line up, and whether you can supply reliably. Invert that order and you have two genuinely different documents.
2. Make the site buildable without the CMS
The first delivery was 21 pages. The content architecture was split in two on purpose: static copy stays in the codebase, while dynamic collections — solutions, industries, insights, FAQs, site settings — come from the CMS, with a local seed dataset sitting behind them. In practice that means the site still builds and deploys even when the CMS is not yet connected or is temporarily unreachable. During handover that matters more than it sounds; you do not want a client's first attempt at editing to be the thing that breaks the website.
3. Real photography first, generated imagery always labelled
The first pass used placeholder visuals, which we later replaced with real product photography recovered from the parent company's legacy site. Where generated imagery genuinely could not be avoided, every instance is labelled as an illustrative render. Industrial buyers look closely, and a photo that appears to show a real facility but does not is the kind of thing that, once noticed, discounts everything else you say.
4. Content from zero to 39 articles
The second phase was content. The site grew from around twenty pages to 39 articles plus 25 structured FAQ entries, with new industry pages and full sitemap coverage. For a newly launched overseas brand, content is the only thing that can put you in front of a buyer's search before anyone knows your name.
Along the way we standardised technical claims, aligning descriptions of the same material specification that had drifted apart across pages. That kind of inconsistency is hard to avoid when copy is written in batches by different people, but the moment a buyer sees one specification described two ways, trust starts leaking. Across the site, image slots ended up with zero duplicates and zero missing files, and none of the 39 article covers repeat.
Results
The site is live on its production domain with every page verified, the content library went from nothing to 39 articles and 25 FAQ entries, and the client now maintains the back end themselves.