This Site — Bilingual Studio Portfolio with a Build-Time Anonymity Guard
The site you are reading, and the invariant that stops it leaking a client’s name.
Built by us, for us — there is no client on this one
Overview
A bilingual English and Arabic portfolio built on Next.js with true right-to-left layout, generated artwork in place of client screenshots, and a build-time check that fails the build if an anonymous case study ever carries a client name or a live URL.
What this proves
That we hold ourselves to the standard we sell. Bilingual, accessible, tested in a real browser, and built so a privacy promise is enforced by the compiler rather than by memory.
Key features
Anonymity enforced at build time
Two clients asked not to be named, and their live URLs contain their brand names — so a stray link would leak the identity just as surely as the name would. A loop over the content throws if any anonymous project carries a client or a URL, which fails the build rather than shipping the leak.
Arabic as a first-class field
Every string in the content model is a pair of English and Arabic rather than a translation looked up at render time, so a missing Arabic string is a type error. Direction is handled with CSS logical properties throughout — the layout is genuinely right-to-left, not a mirrored left-to-right one.
Generated artwork instead of screenshots
Real screen captures carry client identity in navigation bars, packaging and map pins. Each project instead gets an abstract composition drawn from its own palette — privacy-safe by construction, and weighing nothing over the network.
A locale bootstrap that never flashes
The chosen locale is applied by a script that runs before first paint, so an Arabic visitor never sees the left-to-right layout appear and then flip. Reduced-motion preference is read only after mount, so the server and first client render agree and hydration cannot fail.
Stated limits on every project
Every case study carries a “not demonstrated” list, and no figure appears anywhere unless it was counted from the source. There are no traffic, revenue or conversion claims on this site because no evidence exists for any.
Why our own site is in the list
A studio portfolio that does not include itself is asking to be judged on work you cannot inspect. This one you can: it is the page you are on, in the language you chose, and every claim it makes about itself is verifiable by reading it.
Verification
A Playwright suite drives the real production build across every route in both locales at two viewport widths, asserting the document language and direction, exactly one first-level heading per page, no horizontal overflow, and no console errors. A second suite covers the video players. The editorial rule is documented in the repository: every figure on this site is counted from source, because the project dossiers turned out to be unreliable on numbers and several had to be corrected.
Not demonstrated by this project
Stated plainly, because a portfolio is more useful when it is precise about its limits.
- Self-initiated — this is our own site, not a client engagement
- No backend, database or authentication
- No content management — case studies are edited in TypeScript
- Contact is a WhatsApp and email link; no form submits anywhere
- Client screenshots are replaced by generated artwork pending sign-off
Portfolio assessment
- Visual design
- 8.0 / 10
- Technical complexity
- 6.0 / 10
- Interactivity
- 6.0 / 10
- Business value
- 6.0 / 10
- Portfolio appeal
- 7.0 / 10
