Lázeňská káva - contributing developer on the brand ecosystem
Contributing developer role on the Lázeňská káva brand ecosystem covering pestik.cz (grower brand page), greenplantation.eu (plantation export for the EU market), and eshop.lazenskakava.cz (B2C e-shop). Worked alongside the wider team on frontend implementation and selected commerce features.
3 sites, 1 brand
Brief
Lázeňská káva needed to unify three digital touchpoints into a single ecosystem without making each one a generic copy of the others. Three sites, three roles:
- pestik.cz - grower brand page, coffee tree story and grower communication
- greenplantation.eu - plantation export for the EU market, B2B-friendly presentation
- eshop.lazenskakava.cz - main B2C e-shop for end customers
Goal: a shared design language and component library, but each site with its own content strategy and conversion funnel.
Architecture
The project uses a monorepo with a shared design system. Each site has its own package with config, pages, and content modules, while UI components (button, card, hero, navbar, footer) and design tokens (colors, typography, spacing) are shared across all three. Change the accent button color or card radius once, it propagates everywhere.
The e-shop is the heaviest piece: product catalog, variants (weight, grind), cart, checkout, Stripe payments, order tracking, and inventory sync with the back office. The marketing sites (Pěstík + GreenPlantation) are static builds with localized content.
My contribution
I worked alongside the wider team on selected slices of the stack: frontend implementation of shared UI components and page templates, integration touches on the e-shop side, and content plumbing for the marketing sites. Architectural direction and the overall ecosystem brief were owned by the broader Lázeňská káva team and partners.
Key technical decisions
Shared components, separated content. Each site has its own content structure (CS for Pěstík, multi-language EN/DE for GreenPlantation, CS for the e-shop). No monolithic CMS - content lives in git and deployment is git push.
Stripe Checkout instead of a custom cart. PCI compliance is on their side; line items and success_url are passed through. Desktop conversion is strong, mobile holds up thanks to Apple/Google Pay support.
Vercel Edge cache for the product catalog. Products change once a day; catalog pages are ISR with revalidate 1h, so regular traffic is almost always a cache hit.
Takeaway
Three sites for one brand is essentially three times more discipline, not three times more code. A shared design system handles 80 % of the work, but the rest - content strategy, localization, tone of voice - each site has to solve on its own.