The public directory should follow the roster. A scheduled import updates the same WordPress pages when a title changes or someone should leave the site.
Who feels the pain
- Companies with frequent role changes
- Agencies listing specialists by practice area
- Nonprofits showing staff and board with different taxonomies
- Membership organizations publishing member spotlights from a base
Roster fields that map cleanly
| Airtable | WordPress |
|---|---|
| Full name | Title |
| Bio | Content or excerpt |
| Role or department | Taxonomy or ACF |
| Headshot | Featured image on Pro |
| Order or seniority | ACF number the template sorts on, Pro |
| Email, if it should be public | ACF or a mailto in the template |
| Publish? | Status: draft, publish, pending, private, or future |
Personal phone, compensation, and manager notes do not belong in the import view. A privacy mistake is harder to undo than a missed bio update.
Implementation pattern
Import with Integration for Airtable to posts, pages, or a Team custom post type on Pro.
Map Status to draft, publish, pending, private, or future, and keep those rows in the import so a later run can update them.
Featured images land in the Media Library when media mapping is available.
An ACF number is the usual seniority field. See mapping Airtable to ACF.
Daily or weekly on Free. Denser on Pro. Run Dry run before the first live import. Set Status to draft when someone should leave the public directory; the next run updates that page. On Pro, use delete-missing on a full-table import; with a view or filter, rely on Status instead. See scheduled publish without duplicates.
Free can prove a post-based directory. Pro adds a custom post type, ACF, and media for a polished team grid.
Users versus posts
| Destination | Best for |
|---|---|
| Posts or a Team CPT | Public marketing bios, theme templates, and SEO pages |
| WordPress users | Member login, internal directories, and avatars |
Pick one primary public representation. Maintaining user profiles and CPT bios side by side usually recreates the drift you were leaving.
Board versus staff
Use a Type select for Staff, Board, and Advisor, then separate WordPress taxonomies or templates. One Airtable table, two views, and two import connections (or one connection plus taxonomy mapping) keeps governance simple.
Related reading
Questions: support@ripplestep.com.
Draft one person and confirm the page updates
Import the roster, set one record to draft, and check that the same WordPress page changes on the next run.
Install Integration for Airtable free