Case Record

ZEA MAYS FOODS

CLIENTZea Mays Foods

STATUSLIVE

SCOPEPositioning / Branding / Website

ZEA MAYS FOODS case cover

A heritage corn brand built into the presence its work already demanded: cultural weight, product craft, bilingual architecture and commerce held as one system.

Food / Culture / Commerce
2026

Reading

SEVA separated the work into two layers: an editorial surface for story, product and discovery, and a commerce layer on Shopify for payment and operation.

ZEA MAYS FOODS supporting case image

ZEA MAYS FOODS — Food, 2026

Context

Zea Mays did not need a prettier site. It needed a presence able to hold cultural history, visible craft, and real commerce without diluting any of the three.

The previous experience still read as a prototype: temporary assets, unfinished routes, commerce in mockup, and a story that had not yet become public infrastructure.

Decision

The editorial layer kept full control over art direction: ingredient-led imagery, heritage texture, recipe pages, legal pages, bilingual EN/ES routes, structured metadata, canonicals, hreflang, sitemap, and social previews.

The commerce layer handled the transaction where it belonged. Product and cart flows stayed connected to the brand surface, while checkout moved through Shopify infrastructure.

That separation protected the brand from a generic storefront and protected the operation from a purely decorative editorial site.

Outcome

Production-ready editorial site live on zeamaysfoods.com.mx.

Shopify checkout connected through shop.zeamaysfoods.com.mx.

Static bilingual EN/ES architecture, without an automatic translation widget.

Recipe metadata, legal pages, sitemap alternates, canonicals, and public discovery files in place.

Lighthouse validation: 97/100 desktop, 90/100 mobile, SEO 100.

Closing Record

The work holds when the system can carry it.

The public surface and the operating layer must hold the same standard.