Agricultural Brand Platform
Agricultural enterprise · West Africa
A bilingual public platform for an enterprise reviving a crop its country had stopped growing — one hand-written source that is also the French edition, the printed profile and the business card.
No framework, and nothing to build on the host. Hand-written HTML, CSS and JavaScript, self-hosted fonts, and canvas scenes that stop when they scroll out of view; the page works with JavaScript switched off and is navigable by keyboard throughout. The French edition is generated from the English one by a script that maps sentence to sentence and names every one it could not match, so a translation cannot quietly drift from the page it mirrors. The same source produces a one-page profile that prints, the PDF that gets attached to emails, and a digital card reached by QR codes generated with the emblem embedded and handed to printers as vector. With no form endpoint configured, the enquiry forms open the visitor's own mail application with the message already written.
Outcomes
- One source behind the site, the French edition, the profile and the card
- Works with JavaScript off, by keyboard, and under reduced motion
- No enquiry accepted without somewhere for it to go
Engagement
Client named under NDA. Several engagements are active public-sector contracts, so we describe the mechanism rather than the customer.
Source, references and a walkthrough can be arranged for serious evaluation.
An enterprise built around a crop the country had effectively stopped growing, run by a founder whose case for reviving it existed in conversation, a written brief and a folder of photographs. Partners asked for a profile. Buyers asked for something to look at. There was nowhere to send either of them.
Three audiences who never meet in one place: a visitor on a phone paying for data, a partner who wants one page to print and file, and someone across a table who needs a card. The usual answer is three separate artefacts that disagree with each other inside a month. And because the organisation would be publishing claims about programmes, partners and grants, anything that could not be stood behind could not appear at all.
- 01
One source, three artefacts
The site, the printable profile and the digital card are generated from the same hand-written source. The profile prints to a single page and exports as the PDF that gets attached to emails; the card is an address behind a QR code produced with the emblem embedded and given to the printer as vector, so it survives being blown up on a banner. Three things that cannot contradict each other, because there is only one of them.
- 02
A translation that cannot drift
The French edition is generated from the English page by a script that maps sentence to sentence and reports every one it could not find. Change the English and it tells you exactly what is now unmatched. A second language maintained by hand goes wrong within a month, and the people who would notice are not the people who edit it.
- 03
No framework, because the visitor pays for it
Hand-written HTML and CSS, self-hosted fonts, WebP, and canvas scenes that pause the moment they leave the screen. On a metered connection a framework is a cost the reader carries for the developer's convenience, and the page has to survive with JavaScript switched off anyway — which, built this way, it does.
- 04
Only what can be stood behind
Partner logos stayed off until their use was authorised, so those organisations appear as plain text. Exact farm locations are not pinned. No finances beyond a published grant, no phone numbers, nothing about agreements still being negotiated. On a site for a young organisation, deciding what cannot appear is most of the work.
The technical dossier for this engagement
This page describes the shape of the work. The dossier describes how it was actually built — and goes to a named person at a named institution rather than onto a public URL.
- System architecture, including the integration boundaries and why they were drawn there
- The data model for the records the system is accountable for
- Security posture: authentication, authorisation, audit trail and key handling
- Deployment topology, failover behaviour and what happens during an outage
- The measured before-and-after, where the client has cleared it for release
- Named CVs for the engineers who did the work
Sent under a mutual NDA. Client names and locations are redacted unless that client has given written consent, which some have and some have not. Prepared individually — expect it within two working days, not instantly.
Next project
Operations Command Center
Start here
Bring us the problem nobody has solved.
A 30-minute technical briefing. We will tell you what we would build, roughly what it costs, and honestly whether we are the right people for it.
- ask@madsoftech.com
- Telephone
- +220 872841578
- Office
- Brusubi, The Gambia