A meet the team page with real people, kept up to date
A team page answers a visitor's quiet question: who will I actually deal with? Show real names, real roles and photos each person agreed to, with a sentence or two that helps someone pick the right contact. Keep the people in a CMS collection, so adding a starter or removing a leaver is one edit rather than a redesign.
What visitors use a team page for
For a clinic, an agency, a law firm or a trades business, a team page for a website does real work. People check it before booking or calling, to see whether the person they'll meet seems competent and approachable, and sometimes to find a specific person they've been referred to. Job applicants read it to picture working there. None of them want a wall of identical headshots with job titles like "Ninja".
The fields for each person
| Field | Guidance |
|---|---|
| Name | As they want it shown; some prefer first name only |
| Role | A title an outsider understands: "Senior physiotherapist", not "Movement lead" |
| Bio | Two to four sentences: what they do for clients, their background, one human detail if they want |
| Specialisms | For a clinic or firm, what to come to them for |
| Photo | Recent, consistent in style, with their agreement |
| Contact | Optional; a role address is safer than a personal one |
| Order | A number, so the list sorts the way you intend |
Write bios in the third person or the first, but use the same for everyone. Keep them a similar length so nobody's reduced to one line next to a colleague's three paragraphs.
Consent and privacy
An our team page publishes personal information, and in many places that needs a lawful reason and the person's agreement, especially for photos. Ask each person in writing whether they're happy to appear, with which name and which photo. Some staff have good reasons not to be findable online. Offer options: a photo or an illustration, a full name or a first name, or not appearing at all. Remove someone promptly when they leave, and don't keep a former employee's photo up as if they still worked there.
- Don't publish personal phone numbers or home towns unless the person asks.
- Use a role or shared email address for contact.
- Check bios for details that could be used against someone, such as children's names.
Photos that look like one team
Mismatched photos (a wedding crop, a holiday snap, a studio portrait) make a staff page look neglected. Shoot everyone against the same background, at the same distance, in the same light, ideally in one session. If people join later, note the setup so you can match it. Upload the photos to the build; the model sees them and places them, and alt text should say the person's name and role rather than "headshot".
Building it with a CMS collection
Describe the page: "a meet the team page for our physiotherapy clinic with eight practitioners, each with name, role, specialisms, a short bio and a photo, in a people collection". The people live in a CMS collection with typed fields that you edit in the dashboard. The collection is served at its own address, such as /team/ for the list and /team/aisha-patel for a person's own page, which helps when clients search for someone by name.
When someone joins, add an entry; when someone leaves, remove theirs. Surrounding text, such as an introduction above the team, can be edited in place in the visual editor. The page from the design engine runs no scripts, so profiles open as plain pages rather than pop-ups, which are easier to link to and to read with a screen reader. For the page that sits beside it, see writing an about page.
Limits
- No staff logins. Team members can't edit their own profile on the published site; whoever manages the project updates the collection. On a Team workspace, several colleagues can share that job.
- No booking per practitioner with separate calendars. The booking calendar books a service by day and time; it has no staff rotas.
- No embedded video introductions. Link to a video hosted elsewhere.
- No hidden staff directory. Everything published is public, so an internal phone list belongs elsewhere.
If the page is part of hiring, the careers page covers roles and applications.
Questions people ask
Should every employee be on the team page?
Only those who agree, and usually those clients deal with. Large teams can show leadership and client-facing staff, and describe the rest by team.
Can each person have their own page?
Yes. Each entry in the collection can be served at its own address, which suits practitioners clients look up by name.
What if someone doesn't want a photo online?
Use a consistent illustration, initials, or no image for everyone in that row. Don't pressure people into a photo.