Bilingual industrial platform
Gulf Rakza
I designed and built a bilingual platform for a Dammam industrial business, covering products, brands, technical services, specifications, and enquiries.
- Period
- Corporate website and catalogue
- Role
- Information architecture · product design · full-stack build
- Field
- Product catalogue · service architecture · CMS · localisation
Built a bilingual product and services website for customers in Saudi Arabia.
Gulf Rakza operates across product supply and project services. The site had to serve visitors who arrive with very different intentions: a precise item, a safety or mechanical category, a technical service, a brand, or a project requirement that needs a quotation. The solution is part catalogue, part service atlas, and part qualified enquiry system.
How it works
Every route begins with customer intent.
The platform translates a wide offer into searchable entities and bilingual editorial routes. A content system keeps product and service detail maintainable while inquiry paths preserve the context of what the visitor was trying to solve.
- 01Language
Locale-aware routing establishes English and Arabic context before content is presented.
- 02Catalogue
Products carry category, brand, status, description, technical specifications, and media.
- 03Find
Search, filtering, categories, and brand routes narrow a broad industrial inventory.
- 04Explain
Service pages translate technical capability into scope, applications, and project relevance.
- 05Enquire
Quote and contact routes retain enough product or service context for a useful conversation.
- 06Publish
Sanity, metadata, verification, and indexing workflows keep a changing catalogue discoverable.
The condition
Industrial buyers do not all enter through the company story.
Some visitors know the exact component they need. Others know only the category, brand, safety requirement, or site problem. A project team may need a service capability rather than a product. The information architecture therefore cannot assume one linear marketing journey.
The platform organises products and services as distinct but related systems, then creates multiple paths through category, brand, search, and direct inquiry.
The catalogue
Product data became the foundation of the interface.
Product records carry the attributes needed for discovery and qualification: category, brand, availability or status, media, description, and technical specifications. Filters and search operate on that structure rather than on page copy alone.
This makes the catalogue useful to both a visitor and the team maintaining it. New products do not require inventing a new page design; they strengthen the same searchable system.
Bilingual by architecture
Arabic and English are routes, not late-stage translations.
Locale-aware routes shape navigation, content delivery, metadata, and page relationships. The bilingual requirement is treated as part of the application architecture so both audiences receive a coherent site rather than one primary experience and one patched copy.
The system also respects the different density of product language and service explanation, allowing structured facts and longer editorial content to coexist across locales.
The build
A CMS-backed system keeps the public surface alive.
The application uses Next.js and React with Sanity as the content system. Dynamic locale, product, and service routes share structured data while retaining page-level metadata and enquiry context. Framer Motion supports transitions without turning industrial information into spectacle.
Search verification and IndexNow workflows help changing catalogue records reach search engines. The architecture connects content operations, technical discovery, and sales inquiry rather than treating them as separate websites.
What I learned
Key lessons from the project.
Intent before narrative
A catalogue should help a buyer find the right object or capability before asking them to admire the brand.
Localisation begins in routing
Language affects structure, metadata, direction, and maintenance—not only translated strings.
Structured facts earn trust
Industrial users need specification and status to sit beside persuasive explanation.
An inquiry needs context
A contact form becomes useful when it carries the product, service, or requirement that produced it.