Clement Yuen
← Back to articles
Architecture·Beginner

Notes on shipping a bilingual portfolio

2 Aug 2026 · 4 min read · Beginner

  • #Portfolio
  • #Accessibility
  • #Architecture

Share

Bilingual portfolios often bury the language toggle or translate only the nav. I keep EN / 中 next to theme controls and swap the about body, not the entire page structure.

Keep the first viewport simple

Hero content stays lean:

  • Name and role
  • One positioning paragraph
  • One clear CV action

Everything else (skills, timelines, contact CTA) lives below the fold.

Dark mode as a shell concern

Theme state lives in a small shared service on the host so the navbar and page panels stay in sync without prop drilling.

Small UX details compound into a site that feels intentional instead of assembled.

What not to translate first

Prioritize:

  1. Positioning statement
  2. Experience highlights
  3. Contact paths

Defer secondary marketing copy until the primary story reads well in both languages.

Related Articles