S/05 · Services
Web platforms
Fast for everyone, in every language.
Websites and web apps that load instantly, rank well and work for everyone — on any device, in any language, right-to-left included. Built on your API, so a redesign never means a rebuild.
- Built with
- Next.js, React, TypeScript
- Targets
- Green Core Web Vitals
- Languages
- Any, including RTL
- 01
Your site is slow, hard to update or invisible in search.
- 02
You need it in Persian, Arabic or English — properly, not machine-flipped.
- 03
Marketing wants changes faster than developers can make them.
- 04
The website and the product have drifted apart.
- D/01
Design system
We define the type, colour and spacing once, as tokens, and build every button, field and dialog from them. New pages are assembled from parts that already work, so the site stays consistent and a change of colour is one line, not a hunt through every page.
Included
- Design tokens for colour, type and spacing
- A component library in React, with every state
- A living catalogue your designers and developers share
- Light and dark themes, and right-to-left from the start
src/ - src/
- styles/
- tokens.csscolour, type, spacing
- components/
- ui/
- button.tsx4 variants · 3 sizes
- field.tsxlabel, hint, error
- dialog.tsxfocus-trapped
- date-picker.tsxGregorian · Jalali
- table.tsxsortable
- button.stories.tsxcatalogue
- D/02
Performance
Pages are rendered on the server, cached at the edge and sent with as little JavaScript as possible. We measure on a mid-range phone over a slow connection, because that is where most of your visitors decide whether to stay.
Included
- Green Core Web Vitals on the pages that matter
- Server rendering and caching tuned per page
- Images and fonts sized and loaded for each device
- A performance budget checked on every change
lighthouse · example.com (mobile) Performance
98
mid-range phone, slow 4G
LCP
1.4 s
good · under 2.5 s
INP
80 ms
good · under 200 ms
CLS
0.01
good · under 0.1
JavaScript
74 KB
home page, compressed
TTFB
120 ms
served from the edge
- D/03
SEO foundations
We give search engines what they need to understand every page: clear titles, structured data, sitemaps and the links between language versions. When you are moving from an old site, every old address gets a redirect, so the ranking you have built is not thrown away.
Included
- Titles, descriptions and social previews for every page
- Structured data for your organisation, products and FAQs
- Sitemaps and hreflang for every language
- A redirect map from the old site to the new one
seo-audit · example.com - Unique title and description on every page212 pages
- hreflang pairs between English and Persiandone
- Structured data: Organization, Product, FAQvalid
- Sitemaps split per languagedone
- Images without alt text on 14 pagesmedium
- 38 old URLs without a redirectbefore launch
- D/04
Accessibility
Everything works with a keyboard and a screen reader, and text has enough contrast to read in sunlight. We test it automatically on every change and by hand on the flows that matter, because a form some people cannot finish is a form that loses customers.
Included
- Automated checks on every page, on every change
- Keyboard-only runs through the key flows
- Screen reader testing in both reading directions
- A report of what is fixed and what is left
e2e/a11y.spec.ts $ npx playwright test e2e/a11y.spec.ts
Running 24 tests using 4 workers
✓ home · axe: 0 violations
✓ booking form · keyboard only, 11 steps
✓ checkout · focus returns after the dialog
✓ fa/home · reading order follows RTL
! pricing · muted text contrast 4.1:1 (AA needs 4.5)
23 passed, 1 warning (12.4s)
- D/05
Multilingual & RTL
Each language is built as a site of its own, not a translation laid over English. Right-to-left layouts are mirrored properly, and digits, dates, calendars and fonts follow the reader’s language, so a Persian visitor never sees a page that feels flipped by a machine.
Included
- Layouts that mirror cleanly for right-to-left
- Local digits, dates and calendars
- Fonts chosen and tuned for each script
- A translation workflow your team can keep up with
src/i18n/locales.ts Locale Direction Digits Calendar Font en ltr 0–9 Gregorian Inter fa rtl ۰–۹ Jalali Vazirmatn ar rtl ٠–٩ Hijri / Gregorian Noto Naskh Arabic de ltr 0–9 Gregorian Inter - D/06
Editable content
Your team edits pages, posts and prices in a CMS, previews them as drafts, and publishes without asking a developer. The site refreshes only the pages that changed, so updates go live in seconds and the site stays fast.
Included
- A CMS shaped around your content, not a generic one
- Draft previews before anything goes live
- Roles for writers, editors and translators
- A short guide and a session with your editors
docs/content-flow.mmd
- 01
Map
Audiences, journeys and content, so the structure follows what people come for.
- 02
Design
A design system and key pages, reviewed in the browser rather than as pictures.
- 03
Build
Pages on top of your API, tested on real devices and slow connections.
- 04
Launch & measure
Redirects, monitoring and analytics, then tuning based on real use.
A typical website or web app takes eight to twelve weeks from the first workshop to launch. You see working pages in the browser from the second or third week, not a set of pictures at the end.
- Week 1
Workshops on your audiences, their journeys and your content, and an audit of the current site.
- Weeks 2–3
The design system and the key pages, built in code and reviewed in the browser.
- Weeks 4–8
The rest of the pages on top of your API, with the CMS and every language in place.
- Weeks 9–10
Content entry, translation review, and accessibility and performance testing on real devices.
- Weeks 11–12
Launch with redirects, monitoring and analytics, then tuning based on how people use it.
The source code
The whole site in your repository, with a README and a pipeline that deploys it.
The design system
Tokens, components and the catalogue, ready for the next page or the next product.
A CMS your team runs
Accounts for your editors and a short guide to publishing, in every language.
The SEO groundwork
The redirect map, sitemaps and structured data, documented so nothing is lost on the next move.
Analytics and monitoring
Dashboards for traffic, Core Web Vitals and errors, under your own accounts.
A check a month after launch
We review real-user speed, search coverage and errors, and fix what turned up.
- Next.js
- React
- TypeScript
- Tailwind CSS
- Core Web Vitals
- Schema.org
- i18n & RTL
- Playwright
Can you redesign without rebuilding everything?
Usually yes. When the content and logic live behind an API, the front end can change freely.
Do you write the copy and translations?
We work with your writers or bring our own, and treat each language as a first-class site.
Will we be able to edit it ourselves?
Yes. Every site comes with a way for your team to manage its content.
How long does it take?
Eight to twelve weeks for most sites. A single landing page, or a speed fix on an existing site, can take two to four.
Will we lose our search ranking when we move?
We map every old address to its new one with a permanent redirect, and watch Search Console for weeks after launch. Some movement is normal; losing pages to broken links is not.
Tell us what you are building.
Every project starts with a consultation: you bring the idea and everything you know, we turn it into a design you can build on.
Book a consultation