The portfolio as an engineering artifact

Engineering a portfolio for eleven languages.

Public engineering ↑

Content last revised:

One registry, one content workflow

  1. Canonical English → AST string extraction
  2. Incremental translation → source hashes and provenance
  3. Catalog validation → coverage and editorial review
  4. Lazy locale catalogs → static localized routes and metadata

React and i18next use languages.json for locale order, direction, fonts, calendars and writing modes. URL, saved preference, browser preference and English fallback resolve language in that order. Switching preserves route, query and fragment.

Extraction, validation, coverage and prerendering are scripted. Translation sync requires configured authoring credentials; new case-study translations were generated directly by the coding assistant. They are machine-translated and await fluent editorial review.

Every non-English page retains the localized disclosure near navigation and a matching English-original link. Canonical URLs are locale-specific; reciprocal hreflang links and x-default connect equivalent pages. Translation is performed during authoring, never from visitor conversations.

Adaptive Preferences Across Scripts and Layouts

Hidden language and display menus made global preferences harder to discover. The utility rail exposes five controls while reusing the existing preference services; its own state only manages disclosures.

One nonmodal panel opens at a time. Focus enters the panel without a trap; Escape and Close return it to the trigger. Navigation and outside clicks dismiss it. Detailed controls load on demand, with a retry action if loading fails.

Logical docking places the rail on the right in LTR and left in Arabic. Compact screens use an expandable Settings entry. Controls remain horizontal in vertical CJK mode; saved indicators synchronize after hydration. Language switching preserves route, query and fragment.

Privacy UI reuses existing consent state: opening a panel does not enable analytics. DNT/GPC suppression remains separate from saved consent. Keyboard, locale and automated accessibility checks support the implementation; screen-reader, physical-device and fluent translation review remain pending.

Arabic utility rail with the language panel open on the left.
Local implementation capture: Arabic RTL docking and a horizontal language panel.

Inspect the portfolio source · Inspect the evidence

Direction follows the language

NAAE / TypeScript / v0.3.0

View evidence

Arabic changes inline alignment and reading direction; technical identifiers remain isolated. Japanese stays horizontal here. Logical spacing follows direction, while keyboard focus follows DOM order. Optional Japanese/Chinese vertical typography is limited to editorial text; controls stay horizontal.

A deliberate English-only boundary

PACE-RAG professional questions, answers and evidence remain English-only. Its region retains lang=en, dir=ltr, translate=no and horizontal writing. Surrounding notices are localized; changing locale preserves the assistant and conversation state.

Font fallbacks, text scaling, reduced motion and RTL are presentation responsibilities. Automated browser checks support regression detection; native-language review, physical-device coverage and actual screen-reader sessions remain separate work.

Inspect the portfolio source