Skip to case study
All projects
Selected work01 / 04 · 4 min read

Project case study ↘

Dulces-Flares · PURO DOCE

A brand experience from craving to order preparation.

PURO DOCE pairs a cream, caramel and cocoa identity with a lightweight shopping journey: discover products, adjust the cart and prepare a WhatsApp message. The implementation balances expressive design, browser state and resource loading.

Conceptual system sketch · not a product screenshot
My role
Frontend developer · personal project
Context
Brand experience and digital catalog for a confectionery
Project status
Public demo · order preparation for WhatsApp
Period
2026

The challenge

Start with the problem.

The problem

An image-rich, animated page still needs to help visitors find products and assemble an order on a phone. The technical challenge is preserving its visual personality without loading every interaction on arrival or losing the cart on reload.

The approach

Use App Router and server-rendered sections, with small client islands for navigation, cart and effects. Centralize products in typed data, persist cart lines and generate the order summary as a message for WhatsApp.

My contribution

From idea to implementation.

01 /

Visual identity and product catalog

Responsive composition with expressive typography, color tokens and fluid sizing. A six-product catalog combines BRL prices and statically imported WebP images to populate the product cards.

02 /

A cart that remembers the selection

Centralized Zustand state for adding products, increasing quantities, removing lines and deriving totals. Persistence saves cart lines in localStorage; drawer visibility and form steps remain interface state.

03 /

From cart to conversation

A cart, form and final-screen flow. The customer name, neighborhood, products and quantities become a message containing subtotals and a total, encoded in a wa.me link that opens WhatsApp to continue the order.

04 /

Motion loaded when needed

A drawer imported on demand, CSS reveals through a shared IntersectionObserver and a decorative cursor deferred until the first fine-pointer movement. The cursor requires a fine pointer, ignores touch movements and respects reduced-motion preferences.

Architecture

How the pieces connect.

A Next.js App Router frontend with Server Components for content, focused client components and separate modules for catalog, state and order composition. The journey ends in a WhatsApp link; order confirmation happens outside the site.

  1. Page and catalog data

    Sections consume typed products from lib/products.ts. Prices, identifiers and images share one source; rendering the visual content does not depend on a remote content manager.

  2. Cart state and interaction

    lib/cart-store.ts centralizes actions and persists cart lines. DeferredCartDrawer loads the panel on first opening and keeps it mounted for subsequent interactions.

  3. Order composition

    lib/order.ts separates money formatting and message generation from the interface. CartDrawer coordinates the steps, opens WhatsApp and clears the selection when initiating that handoff.

  4. Visual layer and resource contracts

    CSS and a shared observer coordinate reveals. Tests using node:test check image, server-section and cursor-behavior contracts; build tests inspect preloads and initial JavaScript limits.

Tools of the build

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Zustand
  • CSS Animations
  • IntersectionObserver
  • WebP

Decisions

The thinking behind the code.

01

Separate server content from client interaction

Keep visual sections as Server Components and defer the cart drawer and decorative cursor.

Why this choice / trade-off

This reduces initial interaction work, but requires explicit server/client boundaries and a panel download on first opening.

02

Typed catalog and local persistence

Keep products in source code and persist only cart lines with Zustand, separating shopping data from drawer presentation state.

Why this choice / trade-off

Deployment stays simple and the same browser retains the selection. Catalog changes require redeployment, and the cart does not sync across devices.

03

Continue the order through WhatsApp

Generate a structured message rather than building proprietary order and payment infrastructure.

Why this choice / trade-off

The site prepares the order, but opening WhatsApp does not confirm sending or acceptance. The cart clears when the link opens; confirmation and payment remain part of the conversation.

04

Protect the design with technical budgets

Use WebP, CSS reveals and optional cursor loading alongside tests that establish image, preload and JavaScript limits.

Why this choice / trade-off

Effects require custom logic, and budgets must be maintained as resources change. These contracts specify constraints; they do not replace current measurements of the real experience.

The result

What the project delivers.

  • A public demo connecting a distinctive visual identity with a six-product catalog and responsive navigation.

  • Cart quantities, removal, totals and selection recovery from browser storage.

  • Order-message preparation containing customer details, line items and a total for continuing through WhatsApp.

  • Separated content and interaction, deferred loading and performance-contract tests available in the repository.

What I learned

Visual immersion also depends on when each effect loads and runs. Separating catalog, state and message composition makes the journey easier to evolve; an explicit WhatsApp handoff distinguishes a finished interface from an order that has actually been confirmed.

Keep exploring

Let’s build something useful.

Get in touch