Keep the meaning.
Prepare the brief.
We built the agency presentation around parallel-language layouts and an editorial localisation record.
The visitor can see the kind of work being discussed before describing a translation requirement.
Explore the work ↓- PROJECT TYPE
- Website design & front-end development
- DOMAIN
- Translation and localisation agency
- DESIGN FOCUS
- Collecting the context that a translation brief needs
A translation request needs its audience.
The brief brings audience, tone and review context together. We kept those questions ahead of a quotation so the request concerns the intended use, not only a word count. The website explains the service design without claiming a real translation commission or certified result.
The pages we designed.
The build brings home, language services, editorial localisation, build a language brief and discuss your brief into one website.
Language services
View the screen ↓Editorial localisation
View the screen ↓Build a language brief
View the screen ↓Discuss your brief
View the screen ↓Project scope.
We designed and built 9 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The shortlist and planning notes stay within the browser session. Enquiries produce a local preview; no request, payment or booking is sent.
The gallery shows our rendered pages with identifying details masked.
A closer look.
Page by page.
Start with the home page, then explore the details. These are screenshots of the original website, with names, contact details and identifying information blurred for privacy.
5 views Select any view to exploreHave a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.




