# Zendi brand implementation checklist

Apply the Zendi brand system consistently across product interfaces and websites. Use `tokens.css`, `design.md` and the supplied asset masters as the shared implementation resources.

## Preserve

- Logo geometry and original lettering; use the supplied SVGs.
- Search, discovery, location context, listing facts and property-detail organization.
- English and Colombian Spanish, local place names and explicit currency and metric formatting.
- Functional behavior, URL state, listing actions, data provenance and access controls.

## Map visual tokens

| Role | Standard | Implementation |
| --- | --- | --- |
| Primary action | Cherry #B52B46 / white | Hover #96233A; distinguish destructive actions through wording and context |
| Secondary CTA | Charcoal #1A1F2B / white | Neutral outlines for lower emphasis |
| Text / headings | Charcoal #1A1F2B | Inter throughout |
| Page | Warm White #FAFAF9 | White for utility and card surfaces |
| Decorative border | Soft Gray #E5E7EB | Use stronger contrast for functional input boundaries |
| Functional boundary | Slate #6B7280 or charcoal | Check actual backgrounds and states |
| Supporting text | Slate #6B7280 | Full opacity on white or warm white; charcoal on soft gray |
| Body link | Underlined cherry | White underlined links on charcoal |

Keep semantic aliases distinct. Component frameworks may use `accent` for quiet interaction surfaces; keep those surfaces neutral. Check whether the consuming styles expect literal CSS colors, HSL components, RGB components or OKLCH before importing `tokens.css`.

## Apply component standards

1. Use cherry for primary actions and the logo dot, with the supplied exports and tokens.
2. Keep large surfaces neutral or charcoal, with restrained cherry accents.
3. Use opaque white or charcoal listing badges. Verification badges require a documented basis.
4. Use Inter and the responsive type scale in `design.md`.
5. Apply the 8 px layout rhythm, 8 px control corners and 12 px card corners.
6. Use an angled hero crop only where it serves the photograph and responsive layout.
7. Provide recognizable links, neutral secondary controls, persistent form labels, clear errors, loading, empty and saved states.
8. Keep map/list selected states connected and distinguish them through more than color. Preserve location accuracy and privacy.

## Match arrows to behavior

- **↓**: scroll or jump to content on the current page.
- **→**: same-site navigation or a CTA action in the current browser tab.
- **↗**: open a new browser tab, usually for an external site or a same-site PDF or document.

An external address alone does not justify a diagonal arrow. Match the icon to actual tab behavior in both working interfaces and visual examples. Hide decorative arrows from assistive technology, announce new-tab behavior in the accessible name, and use `target="_blank"` with `rel="noopener noreferrer"`. Downloads and copy controls use clear labels without page-jump arrows.

## Keep claims and content accurate

Use real partner endorsements and supported verification, market and coverage claims. Label illustrative card values, approximate locations, price conversions and timestamps. The brand guide’s example property and schematic map use demonstration data.

## Validate the implementation

- Supplied SVGs remain undistorted at desktop and mobile navigation sizes.
- Text meets the intended contrast level in default, hover, focus and selected states.
- Keyboard and touch complete primary flows, with visible and unobscured focus.
- Narrow layouts and 200% zoom preserve content and controls.
- Arrows match page-jump, same-tab and new-tab behavior; body links remain recognizable without color.
- Each badge has an accurate definition and enough photographic separation.
- Loading and failure preserve input and prevent duplicate submissions.
- Locale, currency, units, separators and accent characters are correct.
- Existing routes, application behavior and data permissions retain regression coverage.
