Every word, edited by the client. 

A full-bleed hero with the company's positioning, two calls to action and a stats bar, followed by who they are, why them, vision and mission, philosophy, the problem they solve, services, how they work, who they serve, partners and clients, the market opportunity, the team and a contact section.

Built with Next.js, with every section's text, images and stats loaded from the CMS. Reveal animations play as sections enter the viewport, and the header turns solid once the hero scrolls away.

Seed companies judge a trial partner on credibility before they ever call. A clear story, real market numbers and named partners do that work up front.

The whole site in Arabic: navigation, hero, stats and every section, mirrored for right-to-left reading, with Arabic-Indic numbers where the editor entered them.

Each field holds an English and an Arabic value. The language switch sets the document language and direction, and components read the matching value, so there is one layout, not two sites.

In Egypt, decision-makers at local seed companies read Arabic first, while international partners read English. Both deserve a native experience, not a translation widget.

Field trial management, integrated trial management, screening and early evaluation, reports and decision support, technical and commercial consulting, and training — each with an icon, a title and a short description.

Service cards are a list in the CMS, each with its own icon and bilingual title and text, so adding or reordering a service needs no code.

Services evolve as the business finds its market. Letting the client reshape the offer keeps the site honest about what they actually sell.

A market-opportunity headline, a lead paragraph and cards per crop (tomato, cucumber, sweet pepper and more), each with an image and label/value rows. The first three show on the homepage, and a "View More" button opens a dedicated market page with all of them.

Market items are stored with up to ten bilingual label/value rows each. The homepage takes the first three, and the /market page renders the full list automatically when more are added.

Market figures date fast. Making them structured data, not text in a design file, means the numbers on the site can keep up with the market.

An overview with message counts and the latest message, and a card for each content section: hero, about, why us, mission and vision, philosophy, problem we solve, services, how we work, who we serve, partners, clients, market, team, contact and footer, plus messages and settings.

The dashboard lives under /dashboard on the same Next.js app, behind an admin login, and talks to a separate API at api.oneto-one.com.

Non-technical editors think in terms of what they see on the page. A dashboard laid out like the site removes the guesswork of where to change something.

The hero editor: eyebrow, main heading, subheading and both call-to-action buttons in English and Arabic, a stats bar with a separate number and label per language, and the background image with its recommended size and alt text in both languages.

Every text field is a pair, with required fields marked and Arabic inputs set right to left. Image slots state the expected dimensions and format, so uploads look right on the site.

When the two languages are edited on separate screens, one always falls behind. Side by side, the editor sees the gap immediately.

Brand identity (name, primary and accent colours), contact details, social links and logos for light and dark backgrounds, plus email delivery (Gmail app password or a custom SMTP server) and Telegram bot settings with a guided setup.

Contact submissions are stored for the Messages page, emailed through the configured SMTP account and posted to a Telegram chat by a bot registered with a webhook. Saved secrets are never shown again: fields read "saved — leave blank to keep".

A lead answered in minutes is worth more than one found days later in a dashboard. Sending it to the tools the team already watches closes that gap.