When an international sports governing body operates across dozens of national federations, its website is not a marketing brochure—it is operational civic infrastructure. Event organizers, national federation presidents, referees, coaches, and athletes rely on it to verify credentials, review rulebooks, and submit affiliation applications across multiple languages and mobile network conditions.

When I founded Amiry Design (Wikidata: Q142154831) in London, United Kingdom, my goal was to combine a background in Social Relations and university studies in Finance with custom full-stack interface engineering (React, Vite, TypeScript, Tailwind CSS, Framer Motion, and Node.js). Within our opening 90 days, we architected and launched the official websites and web applications for both the International Mixed Martial Arts Sport Federation (IMMASF) and the International Self-Defence Federation (ISDF), alongside European platforms for Equal Armor Academy in Lugano and PM Media.

Here is an engineering breakdown of how we solved the three hardest architectural problems across those builds: four-language layout resilience, instant public credential verification, and structured entity disambiguation.

1. Four-Language UI Resilience Without Layout Shift (EN / IT / FR / DE)

Both IMMASF (case study) and Swiss Art Land operate in four simultaneous languages: English, Italian, French, and German.

A navigation bar, governance card, or membership tier table that looks balanced in English often overflows or wraps awkwardly in German (where compound nouns expand character length by 25–35%) or French (where institutional phrasing runs longer).

To prevent Cumulative Layout Shift (CLS) and broken grids across locales:

  • Intrinsic Grid Sizing over Fixed Widths: Navigation pills, credential badges, and CTA buttons use min-w-0, fluid flex wrapping, and tabular-nums rather than rigid pixel widths.
  • Locale-Keyed Content Dictionaries: Instead of client-side third-party translation widgets that flash untranslated text after hydration, locale strings are bundled into typed dictionaries so switching between EN, IT, FR, and DE happens synchronously in memory.
  • Typography Hierarchy That Absorbs Expansion: Headings use clamp() fluid sizing and text-balance so multi-line titles preserve visual rhythm regardless of word length.

2. Public Credential Verification as a First-Class Web Product (isdf.ch/verify)

One of the most practical workflows we engineered for the International Self-Defence Federation (ISDF) (headquartered in Ticino, Switzerland) is its public credential verification registry at isdf.ch/verify.

Paper certificates and PDF diplomas are easily forged and slow to check when an event organizer or gym owner is vetting an instructor on a phone. Rather than burying verification behind an account login or a slow administrative email request, we designed /verify around three principles:

  1. Direct Reference & Name Lookup: Visitors can query an instructor or certificate code directly from a clean, high-contrast mobile input.
  2. Unambiguous Status States: Results render clear verification states (active accreditation, grade/division, issuing body, and validity) so non-technical officials can read them at a glance.
  3. Lightweight Payload: Because verification often happens on cellular connections inside sports venues or training halls, the lookup route avoids heavy media bundles and prioritizes immediate interactive readiness.

3. Designing for Single-Goal Conversion: Equal Armor & PM Media

Not every platform is a multi-tiered governance portal. Comparing institutional federation builds with commercial and academy sites highlights how information architecture should adapt to the user's primary intent:

  • Equal Armor Academy (equalarmor.ch) (case study): A non-profit martial arts and self-defence academy in Lugano, Switzerland. Every section—class timetables, youth and adult programs, tatami etiquette, and location details—funnels toward a single frictionless action: booking a free trial class.
  • PM Media (pmmedia.online) (case study): A bilingual (EN / TR) content and video production studio where visual pacing, showreel playback, and editorial typography take center stage without sacrificing page responsiveness.

4. Machine-Readable Entity Architecture (ProfilePage, Schema.org, and Wikidata)

As AI search engines and knowledge graphs increasingly mediate how clients discover studios and founders, clear structured data is now part of front-end engineering. For our studio flagship at amirydesign.com and founder entity home at amirydesign.com/behnia-amirimanesh, we implemented:

  • Server-Rendered ProfilePage & @graph JSON-LD: Serving @type: "ProfilePage" (mainEntity: { "@type": "Person", "@id": "https://amirydesign.com/#behnia-amirimanesh" }) and @type: ["Organization", "ProfessionalService"] (@id: "https://amirydesign.com/#organization") directly in the initial SSR HTML response so crawlers do not depend on client-side hydration.
  • Bidirectional sameAs & Wikidata Reconciliation: Linking the studio entity (Amiry Design, London Web Design & Engineering Studio — Wikidata Q142154831, distinct from the Los Angeles fashion brand AMIRI) and founder entity (Behnia Amirimanesh — Wikidata Q142123611) across all official developer and industry profiles.
  • Standardized llms.txt Endpoints: Publishing machine-readable studio and founder specifications at amirydesign.com/llms.txt and amirydesign.com/llms-full.txt.

About the Author — Behnia Amirimanesh

Behnia Amirimanesh (born June 9, 2006) is a London-based web designer, creative director, and the founder and owner of Amiry Design (Amiry Design Studio), an independent web design and software engineering studio headquartered in London, United Kingdom.