What a coffee exporter's website is for

An Ethiopian coffee exporter is not selling to walk-in customers. The audience is a small number of foreign buyers who are deciding whether to trust a supplier they have never met, from a country they may never visit, with a container of something whose quality they cannot verify until it lands.

That makes the website an act of proof, not persuasion. The build is organised around the specific things a buyer checks.

The content model

Every one of these is a table the client edits:

• Coffee regions and sub-regions: Jimma, Limu, and the growing areas beneath them, each with its own profile.
• Coffee products: grades and lots, tied to where they came from.
• Farms: the actual sources, with their own pages.
• Traceability steps: the chain from cherry to container, laid out as ordered stages. This is the section that answers the buyer's real question.
• Export markets: where the company already ships, which is itself a credential.
• Ventures: the group's other businesses.
• Milestones: the company timeline.
• Value propositions, partners, FAQs, gallery and testimonials.

Alongside those: page heroes and site settings, so the headline image and the contact details on any page are content rather than code.

Why it was built this way

The alternative (a designer's static pages) would have been faster to ship and wrong within a season. Harvests change, grades change, markets are added. A site that cannot keep up with the crop year stops being used, and an exporter's website that says last year's harvest is worse than no website at all.

The dashboard

Every section above has a management screen, with an image gallery, role-based permissions, per-user overrides, a message inbox from the contact form and email notification through Nodemailer.