Giomar Maestre
ES / ENMenu
FINAL REFINEMENT

CASE · LOGISTICS AND LEADSCASE STUDY · LOGISTICS AND LEAD GENERATION

BM Envios: bilingual logistics with verifiable privacy.BM Envios: a bilingual logistics experience with privacy that is verifiable by design.

I turned an early web presence into a bilingual system for services, destinations, and demonstration journeys, backed by an inspectable Next.js architecture.BM Envios needed to evolve from a basic digital presence into a platform for US-to-Latin-America shipping and a Miami mailbox service. I led discovery, information architecture, brand direction, UX/UI, bilingual strategy, and the Next.js implementation architecture.

ROLE AND SCOPE

Product Designer & UX Engineer

Research · IA · UX/UI · i18n · accessibility · SEO · QA · Next.js · React · MUIResearch, IA, UX/UI, responsive system, localization, accessibility, SEO, and QA · Spanish default + complete English support · Next.js 16, React 19, TypeScript, MUI, next-intl, Vitest, and Playwright

The challenge

Show complete journeys without inventing rates, timing, certifications, or a real backend.Rates, transit times, country availability, and legal language were unconfirmed. The experience had to demonstrate quote, contact, and registration journeys without inventing operations, certifications, or a backend integration.

My responsibility

I structured services, destinations, bilingual routes, content states, responsive design, architecture, and QA.I defined services, destinations, navigation, bilingual routes, components, content states, and publication boundaries. I directed Figma, Next.js architecture, accessibility, indexing, and QA.

Coherence and privacy by architecture.The system protects coherence, privacy, and publication.

  1. Spanish firstSpanish first, full EnglishComplete, equivalent English.Both locales retain equivalent routes, metadata, content, and behavior.
  2. Typed registryRoutes, content, and metadata.One source connects route keys, content, metadata, and templates without duplicated trees.
  3. Verifiable content statesNo unconfirmed claims.Public, proposed, and unconfirmed information stay explicitly separated.
  4. Zero transmissionNo fake transmissionInspectable local forms.Validation and recovery remain local with no fetch, XHR, cookies, or storage.
  5. Safe noindexSafe indexingPublication only by authorization.Noindex by default; conversion and legal-notice routes stay excluded.

An inspectable public experience.A bilingual platform inspectable through code and tests.

Approved repository screenshot.The visual selection uses only screenshots already present in the approved public repository.

Mobile English mailbox-registration demonstration with disclosure, form fields, zero-transmission acknowledgement, and a local-only completion path.
English BM Envios Services page with navigation, service overview cards, and the responsive public-site layout.
English mailbox registration demo on mobile.English Services page documented in the public repository, showing the bilingual page system.

Zero transmission

Local validation with no fetch, XHR, cookies, or storage.

REPO ed44c8e · APPROVED

Inspectable privacy

Tests instrument network and storage primitives during real interactions: the demo validates and recovers states without transmitting or persisting data.

SOURCE · PUBLIC REPO ed44c8e · APPROVED CAPTURE

Reproducible QA in the public baseline.Architecture and privacy are backed by reproducible tests.

Local refinements excluded.Public baseline ed44c8e; later local refinements are not represented as published.

42
localized canonicals
46
static pages
184
unit tests
608
Playwright
0
serious/critical axe
0
vulnerabilities
42
localized canonical pages
46
generated static pages
184
unit and component tests
608
passing Playwright tests
0
reported serious/critical axe findings
0
known vulnerabilities in audits

Product, content, and QA connected.A strong demonstration of Product Design and UX Engineering.

The public baseline is solid; local refinements remain separate.The project connects research, content, bilingual interface design, frontend architecture, and reproducible QA. Remaining visual refinements are not represented as published until their own approval flow is complete.

Limitations

No backend, payments, tracking, authentication, or real operations. No unconfirmed claims.

Inspect the baseline.

Public code and evidence.

Declared limitations

No backend, CRM, payments, tracking, authentication, or real quote/mailbox creation. No unconfirmed rates, timing, certifications, or availability. No claim of a full manual screen-reader audit or Lighthouse score.

Inspect the public baseline.

Architecture, documentation, screenshots, and reproducible tests.