Team Cards block + photos

Show your team with names, roles, bios, and photos uploaded inline.

The Team Cards block displays a grid of team-member cards on your contact page. Each card has a photo (or initial fallback), name, role, and short bio.

Adding the block

In the contact-page editor, click + Add blockTeam cards. The block lands with one empty member entry.

Filling in a member

Each member is a row inside the block:

  • Name — the person's name as visitors should see it.
  • Role — their title (e.g. "Head of Support", "Senior Engineer").
  • Bio — a short blurb. Two or three sentences max — this is a card, not a profile page.
  • Photo — upload below.

Uploading a photo

Click the Choose file input on the empty avatar circle. Your browser's file picker opens. Pick a square-ish image — we recommend at least 400×400 px for crispness on retina displays.

The upload happens immediately:

  1. We accept JPG, PNG, WebP, or GIF, up to 4 MB.
  2. The file gets stored under uploads/<tenant>/<uuid>.<ext> on our public file store.
  3. The card updates with the photo URL — no page reload.

If the upload fails (wrong type, too big, network issue), an alert message tells you what happened. Try again with a smaller / valid file.

No photo, no problem

Members without a photo render with their first initial on a gray background. Cleaner than a generic placeholder face.

Removing a member

Each member row has a Remove member link. Click it; the row disappears immediately (but the change isn't persisted until you save the page).

Removing a member doesn't delete the uploaded photo file — it just removes the reference. The orphan file stays in storage. We may add a cleanup job later; today it's harmless.

When to use Team Cards

  • Small / mid-size teams where visitors care who they're talking to.
  • Agencies, consultancies, service businesses where the team IS the value.
  • "About us" feels heavyweight; Team Cards on the contact page is friendlier.

Skip it if:

  • The team changes constantly — maintenance burden.
  • You'd rather direct visitors to the chat / form than at specific people.