contact — Lattice component
Lattice

contact

StatementPanelStructure

An identity card that encodes a vCard: name, title and contact lines beside a QR that saves the presenter to a phone.

Open in Playground

Use as the "scan to add me" close or a speaker-intro slide. The QR encodes a vCard the audience saves in one tap, or, with qr: tel, a link that dials; the card shows the name as hero with title/org and a contact ledger. Author the fields as a postfix-key list. It reflows by canvas (side by side, then stacked) and holds at every venue.

referenceonboardingkickoff

When to use

  • The scan-to-add-me close. End a pitch or intro with a code the audience scans to save your contact, instead of trading business cards.
  • Show what you choose, encode the rest. Every non-empty field goes into the vCard; the card foregrounds the name, title and org and lists email/phone/url beneath.
  • A hall or conference room. A full vCard is a dense code (55-67 modules wide) and the back row cannot resolve it. Add - tel qr` or - url qr`: the code carries only a phone link or a web address (27-35 modules, about 2.5 times larger per module) and the ledger still shows every field.
  • Phone numbers that differ. Write each line with its own key (mobile, office, phone). Each becomes its own typed TEL entry in the vCard, and the card lists them in the order written.

When not to use

  • Not a team roster. One card is one person. For a set of people use an inventory layout; a contact card is a single identity.
  • Don't bold the field values. The value leads and the key trails as a small tag — name last, never first. Writing the key first, bolded, breaks the transform's postfix read.

Common mistakes

  • No field is tagged with the name key. Every contact card needs exactly one field trailing ` name ` — without it the vCard has no identity and the hero name area renders empty.
  • The trailing key doesn't match a supported alias, e.g. ` position instead of title/role `. Only the documented keys are recognized (name, title|role, org|company, email, phone|tel|voice, mobile|cell, office|work, url|web|site, qr, caption) — an unrecognized key isn't mapped to any card field, so the whole bullet is silently dropped from both the rendered card and the vCard, not merely misplaced.
  • A full vCard QR on a venue: hall deck. The code is dense and the room is far. Add - tel qr` (the code dials the first phone line) or - url qr`; the card still lists everything.

Authoring

<!-- _class: contact -->

## Add me.

- Full Name `name`
- Title `title`
- Organization `org`
- name@example.com `email`
- Scan to add me `caption`

Slots

SlotSelectorRequiredDescription
titleh2noOptional framing heading; the person's name is the visual hero, drawn from the name field.
fieldsul > liyesOne field per bullet in postfix-key form — value first, trailing inline-code names the field: - Sharmarke Aden name`. Keys: name (required), title|role, org|company, email, phone|tel|voice, mobile|cell, office|work, url|web|site. Phone keys are separate lines, each typed in the vCard, and the ledger lists every line in the order you wrote it. Optional keys: caption (CTA under the QR) and qr (what the code carries: vcard, tel or url`).
captionul > linoOptional call-to-action under the QR, as a postfix-key bullet: `- Scan to add me caption `.

Related

  • wifithe card is a network to join rather than a person