Build a team directory page from a Google Sheet

A team page that stays current

A staff directory is the page most likely to be wrong. Someone joins, someone changes title, someone leaves — and updating a grid of hard-coded cards is a developer chore that slips. HR knows the roster; they just have no way to edit the page.

Give them a Google Sheet instead. One row per person — name, role, department, photo URL, and a short bio — and PasteSheet publishes it as JSON. Your directory page fetches the rows, filters by department, and renders the cards. HR edits a cell; the page catches up on the next cache refresh, no deploy in the loop.

What a directory row holds

A single tab with a column per field powers the whole page:

• name, role, and department for the card and filtering.
• photo holding a headshot URL your front end renders.
• bio for a short blurb and email or links for contact.
• order to control how people rank within a team.

Filter the directory by department

Pass a department to filter and a column to sort — build a tabbed directory without any query language:

curl "https://pastesheet.com/your-endpoint/Team?department=Engineering&sort=name"

{
  "data": [
    {
      "name": "Marco Silva",
      "role": "Staff Engineer",
      "department": "Engineering",
      "photo": "https://cdn.example.com/marco.jpg",
      "bio": "Works on the query layer and caching.",
      "email": "[email protected]"
    }
  ]
}

Read-only, so it is safe to publish

Because the endpoint is read-only by design, it is safe to expose publicly or hand to a teammate: consumers can read and query the data but can never change the sheet. And there is no Google Cloud project, OAuth screen, or service account to set up — you paste a share URL and get a live API.

What it costs

Frequently asked questions

Sources

• Files you can store in Google Drive (size limits) — Google

Related use cases