Bilingual, fast, no ceremony.

The brief

glassollogy.com is a glass and aluminium workshop in Amman. The owner makes windows, balustrades and custom storefronts — objects with a weight and a finish, measured before they are cut, installed in buildings people walk past every day. The work is physical and specific. The page was not allowed to be vague.

The brief was short, because the business is easy to state: one page, two languages, no ceremony. A workshop does not need a content operation. It needs a page someone can open, read, and act on.

Language was part of the brief from the start. Work from the Amman office runs in English by default and in Arabic when the client prefers it. Here both languages sit on the page, so the same address serves an Arabic-speaking homeowner and an English-speaking contractor.

What we did

We built one page around what the workshop actually makes. No invented positioning, no stock language about craftsmanship, nothing on the page that the owner could not stand behind in a conversation on site.

• One page. The workshop's output — windows, balustrades, custom storefronts — written plainly in one place.
• Two languages on the same page: English and Arabic, from an office that runs engagements in both.
• Weight treated as a design decision. The page had to open quickly on a phone, so nothing went in that slowed it down.
• Direct from the operator. Scoped, written and built by the same person, in Amman.
• Handed over as a page, not a system — nothing the owner has to keep feeding after launch.

The same discipline that runs through Trilot’s long engagements ran through this one at a smaller scale: decide what the business is, write that down, and cut whatever does not survive the test.

What shipped

A bilingual page at glassollogy.com, built for a workshop in Amman. It describes windows, balustrades and custom storefronts in English and Arabic, and it loads without ceremony.

The build was deliberately small: one page, one owner, one city. There is no second site to keep in sync, no translation fork to maintain, and no feature on the page whose only justification is that a template had room for it.

Nothing on the page claims a number we cannot show. The workshop’s reputation is carried by the work, not by a statistic about it.

What it proves

The same discipline scales down. Most of what Trilot builds is long-form — platforms with a six-month minimum and a handover document. This one is a single page, and it still went through the first question in the same order: what is this business, in one paragraph, in two languages? The answer took a page.

It also makes the language question concrete. A workshop in Amman deals with Arabic-speaking customers and English-speaking contractors in the same week. A page that reads in only one language only serves part of them.

And a project this small is still the operator’s own work — no account manager, no junior, no delegation. The scope is smaller here; the person doing it is not.

Engagement notes

Work like this is scoped by subtraction. The first questions are how little the site can be, which languages its customers read, and what the owner will realistically maintain after handover. At glassollogy the answer was one page in two languages, built from the Amman office at St. Kraim Al-Dayyaty.

It sits outside the normal shape of web & software development in one specific way. That service line is long-form: custom platforms, web applications, internal tools, six-month minimums, decision logs from week one. Marketing landing pages and template reskins are explicitly out of scope — real markets, just other people’s markets. A single page for a small workshop is the small exception, taken when the operator can build it directly and honestly.

If the work needs a platform — something that has to survive a personnel change, an acquisition, a pivot — that is a scoped engagement with a six-month minimum. If the work needs one accurate page in two languages, say so on the first call and it will be treated as exactly that.