Hashi

WordPress 7.1 · per-demo theme on _chassis (paper + ink + vermilion; Bricolage Grotesque + IBM Plex Mono self-hosted, Noto Serif JP glyph-subset on Latin pages) · Polylang free · EN/ES/JA · animated homepage in editable core blocks · 5 pages × 3 + 3 case studies × 3 = 24 rows · Apache 2.4 + PHP 8.3 + MySQL 8 on EC2

Screenshot of the hashi demo homepage

A fictional cross-border design studio — Hashi 橋, with offices in Tokyo, Mexico City and Berlin — published in English, Spanish and Japanese. The demo for the request that sounds simple and is not: “can you build it in three languages?” Rebuilt September 2026 around an animated homepage, and repaired at the same time. Live at hashi.wp.philiprehberger.com.

The challenge

A multilingual site is usually sold as a translation problem and is actually a routing problem. The copy is the easy part. What breaks is everything around it: which URL a language lives at, whether a search engine can tell the three versions apart, whether the navigation knows it should point at /es/servicios/ rather than /practice/, and what happens to a page that has no translation yet.

Hashi is the worked example: three languages, locale-appropriate slugs rather than translated ones (/es/servicios/, /ja/サービス/), hreflang on every translated page, and a language switcher that offers the current page’s translations rather than generic language links.

What we found first

Before any redesign work: the multilingual layer was dead. /en/, /es/ and /ja/ were returning byte-identical English — 70,873 bytes each, html lang="en-US", no hreflang, no switcher in the markup. The Spanish and Japanese content was intact the whole time and simply unreachable.

Two causes, both from the host rebuild. Polylang was active but unconfigured — no default language, no terms, no post carrying a language. And underneath that, the real one: permalink_structure was empty. Polylang’s routing is rewrite-based, so with no structure there are no rules for /es/ and /ja/ to hang off, and WordPress serves the front page for every unmatched path. Three locales, one page, no error anywhere. The seed had only ever flushed rewrites and never set a structure, so a fresh install never had one; it does now.

The lesson worth keeping is the failure mode. A broken multilingual site does not 404. It returns 200 and looks fine, in one language, forever.

The approach

A per-demo theme on the platform chassis. Paper, ink and vermilion, with a city color each for Tokyo, Berlin and Mexico City that runs through the clock bar, the bridge arcs and the office cards.

Type is three faces doing three jobs: Bricolage Grotesque for display and body, IBM Plex Mono for the labels and clocks, Noto Serif JP for the Japanese. The first two are self-hosted. The third is not, and that is the interesting decision — Google ships Noto Serif JP as 124 unicode-range subsets per weight, and mirroring ~372 files to self-host a CJK face is the wrong trade when the dynamic subsetting is the whole value. The Japanese pages get the full request. The Latin pages, whose only Japanese is the 橋 seal, the 東京 label and three words in the marquee, ask for exactly those glyphs and get one small file: 89 KB of CSS and ~190 KB of subsets down to a couple of KB.

The homepage is a motion piece and still editable. Live office clocks in three time zones with a blinking colon; a 橋 that draws its own strokes and then fills; a dotted ring rotating behind it; three arcs drawing between the cities with lights running along them; count-up statistics; and a case-study list whose photograph wipes into a sticky preview on hover or keyboard focus. All of it sits on ordinary core blocks — only the SVG furniture is Custom HTML — and all three language versions are generated from one structure and three string sets, so Spanish and Japanese are the design rather than a translation of the English page’s leftovers.

What’s on the site

  • Home, in three languages. Clock bar, sticky header, the animated hero and 橋, the bridge band, a multilingual marquee, the practice statement with counting statistics, three office cards with live local time, the case-study list with its wiping preview, a vermilion contact panel, and an oversized Hashi 橋 footer
  • Studio, Practice, Work, Contact — five pages in each language, on locale-appropriate slugs
  • Three case studies, each in three languages, at URLs like /work/wayfinding-tokyo-modern-art-museum/ and /ja/事例/東京現代美術館-サイン計画/
  • Below 900px the navigation becomes a right-hand drawer over a blurred backdrop, with its own 橋 seal, numbered links and live clocks for all three offices

The stack in detail

  • _chassis parent theme, inherited from the platform via symlink
  • hashi per-demo theme — theme.json with the palette and the self-hosted faces; a tokens → motion → site cascade at priority 99; site.js for the clocks, the preview, the drawer, the count-up and the reveal fallback; and four PHP patterns for the clock bar, header, drawer and footer, every label and URL resolved through Polylang for the language being rendered
  • Polylang free, configured once by an admin-context bootstrap script rather than from runtime code — its options class fights repeated pageload writes
  • sfp-blocks/language-switcher, the shared block this demo drove
  • .scripts/verify-design.mjs (npm run verify) — 99 checks in a real browser across all three locales at 1440/820/390, asserting the routing, the hreflang triple, per-locale navigation, the drawer contract, reduced motion, scripting off, and that every Japanese string outside a Japanese page carries its own lang="ja"

Where we made tradeoffs

Fixing the delivered design rather than porting it. Its four statistics were counter() generated content — invisible to screen readers and crawlers, and rendering as 0 wherever @property is unsupported — which matters when all four are facts from the site’s own copy. Its hamburger border was 1.54:1 against white, under the 3:1 WCAG 1.4.11 asks of a control boundary, and Lighthouse does not test that rule. And every kanji on the English page was unmarked, so a screen reader pronounces 橋 and 東京 with an English voice — a pointed thing to get wrong on a demo about publishing in three languages.

Accepting one redirect hop. Polylang runs with the default language unprefixed, so / is the English home and /es/ and /ja/ reach their translations via a single 301. The symmetric alternative was tested and is worse: /en/work/ starts 404ing, because Polylang free will not map a non-default prefix onto a static front page translation. /en/ itself is the one URL the strategy strands, and a redirect handles it.

Not redesigning the other pages. The brief covered the homepage. Studio, Practice, Work and Contact inherit the new chrome, palette and type but keep their own layouts — which did surface one real problem worth naming: the chassis maps h2 to the xx-large preset, so sizing that preset for a 116px display headline rendered the founder names at 96px in a 233px column and broke them mid-word. The homepage components set their own sizes and use no preset at all; the presets went back to a general-purpose scale.

Outcomes

  • Three languages genuinely live again, each at its own URL with its own content, after an unknown period serving English to everyone
  • An animated homepage in all three languages, built from editable core blocks, that degrades cleanly: reduced motion stops everything, scripting off leaves the headline, the statistics and every case-study link intact, and the clocks show --:-- rather than a wrong time
  • Accessibility 100, best practices 100. Page weight 850 KB → 312 KB once the WebP sub-sizes were actually being generated and the CJK face was subset to the glyphs the Latin pages use; performance 62 → 84 with the shared analytics tag blocked
  • A committed 99-check harness that asserts the multilingual contract itself, so the next change has to prove the routing still works
  • Two platform-level bugs found and fixed for every demo, not just this one: the output-format filter that was silently never running, and a seed that flushed rewrites without ever setting a permalink structure

Tagged

Industry:
Builder:
Theme:
Features: , ,

Facts

80

100

92

100

13