---
name: Zendi
version: 1.1
updated: 2026-09-24
purpose: Brand and UI brief for designers, developers and AI design tools
---

# Zendi — design system brief

## Brand standards

Use the cherry and charcoal palette, supplied logo masters, Inter typography and specifications in this guide across every Zendi touchpoint. Apply the same standards to interface components, brand collateral and generated design assets.

Preserve the logo geometry and original lettering. Keep brand accents within the palette. Make verification claims only when they have a documented basis, and label illustrative content clearly.

## Brand positioning

Zendi is a real estate platform designed to help buyers, sellers, and real estate professionals make smarter property decisions in Medellín and Antioquia through verified listings, neighborhood-level intelligence, transparent market information, and intuitive tools to streamline the buying and selling of Colombian real estate.

The common goal is **reducing informational disadvantage** for buyers, sellers and industry professionals. The product vision is to build the most trusted real estate listing platform for Medellín and Antioquia. That is a vision, not a claim of achieved leadership.

### Philosophy

Real estate markets work better when trustworthy information is easier to access, easier to understand, and easier to act on. Better visibility, coordination and market transparency lead to better outcomes for buyers, sellers and professionals alike.

### Pillars

Trust; transparency; local intelligence; data integrity; accessibility of information; human expertise; thoughtful simplicity.

### Audiences

Serve foreign buyers, local buyers, foreign sellers and local sellers. Support agents, agencies and community collaborators. Do not position independent buyers or sellers as inferior participants.

### Emotional goals

Informed, calm, empowered, confident, guided, and capable of making smarter decisions.

## Visual direction

Architectural, minimal, premium but restrained, navigationally clear, map-oriented, information-rich without clutter, intentional whitespace, clean typography, restrained color and subtle motion. Do not turn useful property information into decorative marketing cards with missing context.

## Color palette

| Token | Value | Use |
| --- | --- | --- |
| `--z-cherry` | `#B52B46` | Logo dot, primary CTA, underlined body links, selected accents |
| `--z-charcoal` | `#1A1F2B` | Logo, headings, body text, secondary CTA, dark surfaces |
| `--z-warm-white` | `#FAFAF9` | Page backgrounds and quiet surface separation |
| `--z-soft-gray` | `#E5E7EB` | Dividers, decorative borders, neutral surfaces |
| `--z-slate` | `#6B7280` | Supporting text on white or warm white at full opacity |
| `--z-white` | `#FFFFFF` | Utility surface and text on filled CTAs |

Derived interaction shades: cherry hover `#96233A`; charcoal hover `#303745`. These are implementation states, not new accent colors.

White on cherry is 6.18:1; cherry on warm white 5.92:1; charcoal on white 16.47:1; slate on warm white 4.63:1. Slate on soft gray and cherry on charcoal fail 4.5:1 for normal text. A contrast table is not an accessibility certification.

Do not use pale-pink or red routine listing badges. Keep red purposeful rather than ubiquitous. On dark surfaces use white underlined links, not cherry body text. Do not map every framework `accent` surface to red.

## Logo system — exact masters

Use `01-vector-masters/` without redrawing, changing paths, moving the dot or replacing lettering with a font.

- Horizontal: the Z is the initial letter, followed by `endi`. Do not append another `z`.
- Stacked: symbol above the full wordmark.
- Icon-only: Z and its single cherry locator dot for avatars, apps and favicon use.
- Dark-background: supplied white/cherry master on charcoal.
- Monochrome: supplied masters for genuine one-color requirements.

The `00-original-dark-preserved/` directory is archival, not the production identity. The existing SVGs contain built-in whitespace; size against the visible artwork.

**Clear space:** at least one dot diameter around the visible mark. Minimum sizes: horizontal and stacked 120 px wide, general icon 32 px and above. Inspect at actual size. Use the dedicated favicon exports for 16–32 px.

Social presets use a Z at 68% of square height, with 16% top/bottom padding. Upload the complete square and inspect circular crop previews. Google OAuth: `04-google-oauth/zendi-google-oauth-120-white.png`, exactly 120 × 120 px, opaque PNG, 5,662 bytes.

## Typography

Use **Inter throughout**, with a system sans-serif fallback.

Use 400 for body, 500 for controls, 600 for headings, and 700 sparingly. Never imitate the logo using Inter.

| Role | Mobile / desktop | Weight / line height |
| --- | --- | --- |
| Display | 40 / 64 px | 600 / 1.08 |
| Page title | 32 / 48 px | 600 / 1.15 |
| Section | 24 / 32 px | 600 / 1.2 |
| Card heading | 18 / 20 px | 600 / 1.3 |
| Body | 16 px | 400 / 1.6 |
| UI / supporting | 14 px | 400–600 / 1.5 |
| Caption | 12 px minimum | 400–500 / 1.5 |

Use sentence case. Reserve uppercase/letter-spacing for short editorial labels. Use around 60–70 characters for reading columns and tabular figures for aligned data. Preserve ÁÉÍÓÚÜÑ, accents, ¿¡ and m². The compact labels in the documentation interface are not a reason to make platform body copy smaller.

## Geometry and patterns

Use an 8 px layout rhythm with 4 px increments for compact controls. Gutters: 16 px mobile, 32–48 px desktop. Start with 12/8/4 desktop/tablet/mobile columns, but prioritize content over mechanically enforcing a grid.

Radii: 4 px badges, 8 px controls, 12 px cards, 16 px feature containers. Circles belong to avatars and genuine circular controls, not every CTA. Borders precede shadows. Avoid ornamental gradients, glass surfaces and needless layered cards.

The three SVGs in `brand-assets/` are the decorative patterns: nested architectural frame, abstract parcel grid and locator grid. Do not present abstract geometry as real geography. Use patterns in spacious decorative fields, not behind reading text or as alterations of the logo.

Use angled photo crops selectively at roomy breakpoints; remove them when they harm a focal point or mobile layout.

## Components

### Actions and links

Primary: cherry fill, white text. Secondary: charcoal fill, white text. Lower emphasis: white fill, charcoal text and outline. Provide clear verbs and only one leading task per group.

Body links: cherry with a persistent underline; dark-background links: white with underline. Do not rely on bold alone. Use anchors for navigation and buttons for actions. Provide visible keyboard focus and a 44 × 44 CSS px minimum touch target.

### Navigation arrows

Use the same arrow meanings in interfaces, illustrations and visual assets:

- **↓ Down:** scroll or jump to content on the current page only.
- **→ Right:** same-site navigation or a CTA action that keeps the current browser tab, such as a contact form or account creation.
- **↗ Diagonal up-right:** a link or action that opens a new browser tab. This usually leads to an external site, but also applies to a same-site PDF or other document opened in a new tab. An external URL alone does not qualify.

Pair arrows with clear labels. Hide decorative icons with `aria-hidden="true"`. New-tab links use `target="_blank"` and `rel="noopener noreferrer"` and include “opens in a new tab” in their accessible name. Use explicit “Download” and “Copy” labels for utility controls; reserve down arrows for page jumps. Use words or punctuation, rather than arrows, for ranges and step sequences.

The brand guide presents each section as a distinct page in the same tab. Links between these sections use the right arrow; jumps within the visible section use the down arrow.

### Badges on photos

Routine labels (For sale, New listing, Price reduced): opaque white, charcoal text, 1 px charcoal outline. Selective emphasis (Verified, Featured): opaque charcoal with white text and an optional meaningful icon. Use 12–14 px medium text and a 4 px radius.

Prefer no more than two visible labels on a compact card. Avoid translucent pastels or warning-like red status. Verification must explain what was checked, by whom and when; it is not an unconditional guarantee. Featured describes placement, not trust or verification.

### Forms and feedback

Persistent visible labels, readable placeholders, functional borders and keyboard focus. Error feedback includes repair instructions and programmatic association (`aria-invalid`, `aria-describedby`); never convey it only by changing color. Neutral icon/text treatment avoids conflating brand red and errors.

Preserve entered data on failure. Loading states communicate work and prevent duplicates. Empty states explain what happened and offer a useful next step. Prefer contextual inline feedback for field errors and toasts for completed actions. Do not use browser alerts as the default feedback mechanism.

### Properties, maps and data

Order property details around four stages: orient, evaluate, investigate and act. Preserve location, gallery, price, essential facts, amenities, context, source/verification details and an identifiable contact route.

Use charcoal ordinary map markers, cherry active selection, and a second selected-state cue. Keep list/map selection synchronized; support keyboard and mobile interaction without hover dependency. Label approximate locations and respect location privacy.

Use the relevant municipality/barrio/vereda/community path without asserting that rural and urban administrative structures are interchangeable. Label currencies, units, time periods, data sources and sample sizes where relevant. Distinguish asking prices from sale prices, estimates from verified numbers and missing data from zero.

## Imagery and icons

Use credible architectural photography, natural color and useful property/neighborhood context. Do not substitute unrelated buildings for an actual listing. Label renders, virtual staging and materially altered imagery. Document usage rights; do not erase permanent defects or invent views.

Image ratios: 4:3 listing cards, 16:9 editorial features, 1:1 avatars. Preserve the focal point. Use a coherent 24 px icon grid with roughly 1.5–2 px strokes, accessible names for icon actions and text alongside unfamiliar symbols.

## Voice and localization

Be specific, locally grounded, informed and calm. No invented scarcity, guaranteed returns, unsupported superlatives or exoticizing Colombia. Do not overstate feature availability or verification.

Preserve local terms when translation would distort meaning. Use appropriate Colombian Spanish, not literal English constructions. Both local and foreign buyers/sellers belong in the language.

Metric first: m² for structures/small plots; hectares for large land; kilometers for distances. Imperial units are secondary. Label currencies explicitly and format numbers for the locale, e.g. English `COP 850,000,000`; Colombian Spanish `COP 850.000.000`.

## Motion and accessibility

Timing: 150 ms feedback, 220 ms ordinary transitions. Prefer opacity and transforms. Respect `prefers-reduced-motion`; no persistent logo pulses, autoplay parallax or animation delaying the primary task.

Check keyboard, touch, focus, contrast, headings, labels, screen-reader names, reduced motion, zoom and narrow layouts. W3C references: https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html and https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html.

## Implementation resources

- `tokens.css`: shared palette, spacing, corner, motion and semantic tokens.
- `ASSET-GUIDE.md`: export specifications, padding and web/native installation.
- `asset-index.json` and `asset-index.csv`: filenames, formats, dimensions and byte counts.
- `MIGRATION.md`: the brand implementation checklist.

Keep the brand name **Zendi**. Use the supplied artwork and stable asset paths. Preserve existing application IDs, URL state and functional behavior when integrating the brand system.
