Organizations publish roster pages constantly: team rosters, cohort rosters, chapter directories, board lists, fellowship classes. Each one is a defined group of members with a group label, cohort or year, and a curated member list. A single member can appear in multiple rosters (current team + 2026 cohort + chapter A) without being canonically homed to any one.

SleekRank reads a rosters sheet keyed by slug with columns for label, group_type (team, cohort, chapter, board), period, intro, and the included member slugs. A separate members sheet holds member-level columns (name, role, avatar, bio). Each roster row drives /roster/{slug}/ with list mapping over the filtered members sheet rendering each member card.

Adding a new roster (a 2027 cohort, a new chapter) is one row in the rosters sheet plus member slugs. The base WordPress page is auto-noindexed; only the roster pages compete in search. Editing a roster's member list is a single cell edit, and the next cache flush propagates the change.

Most organizations publish their members on a single team page that lists everyone with role and avatar. The page grows, gets unwieldy, and starts to hide context: which team is this person on, what year did they join, which cohort or chapter does this fellow belong to. When a fellowship's class graduates, the team page either stays bloated with every alum or loses them entirely.

There is no surface for a journalist or recruiter looking for the 2023 cohort or the Austin chapter. SleekRank handles rosters as first-class editorial objects. The rosters sheet defines each group: per-team, per-cohort, per-chapter, per-year.

The members sheet holds canonical member rows referenced by slug from any roster. List mapping joins them at render time, so each /roster/{slug}/ shows only the members in that group, with the group's intro, period, and status. The same member appears on multiple rosters by slug reference, never by duplication.

Past cohorts stay live as alumni rosters with an inactive or alumni banner. New cohorts are a row append plus member slugs. Member data updates (a name change, a new bio) happen in the members sheet once and flow to every roster that references that member.

The structural pattern is two sheets, one URL per group, one URL per member, and a join that scales without manual cross-linking. That is the difference between programmatic rosters and a single team page that conflates everything into one URL.