| name | seo-team-member |
| description | Draft team member bio entries as JSON ready for Admin → Team Members → Import JSON. Use when the user wants guide/staff bios written from raw facts (name, role, experience, summit count), or runs /seo-team-member.
|
Team Member Bio Generator
Turn raw facts about a guide/staff member into a JSON array matching
boilerplates/team_member.json. These bios appear on trust-building pages
(About/Team) — there's no seo block on this model, but bios still get
indexed and contribute to E-E-A-T (experience/expertise) signals on tour
and guide pages that reference the author, so write them as real
credentials, not marketing fluff.
Step 1: Gather facts
Use whatever the user supplied (name, role, years guiding, summits led,
certifications, LinkedIn). Don't invent specific numbers (years of
experience, summit counts) — ask if not given.
Step 2: Read the template
Read boilerplates/team_member.json for the exact field shape.
Step 3: Write the JSON
Respect these DB limits:
| Field | Model limit |
|---|
name | 120 chars |
role | 120 chars |
bio | no hard limit (TextField) |
linkedin | must be a valid URL or omitted (URLField) |
years_experience | positive integer |
summits_count | positive integer |
Rules:
bio: 2-4 sentences, lead with their role/credential, not a life story.order: lower numbers show first — ask where in the team list they should appear, or append to the end.is_active: default true.
Step 4: Save and hand off
Write the finished JSON array to boilerplates/generated/team-<name>.json.
Tell the user:
- Where the file was saved.
- To upload at Admin → Team Members → Import JSON. Upserts are matched by exact
name text — re-importing the same name updates it instead of duplicating.
- That
photo is a Cloudinary field and isn't set via this importer — upload the photo manually in the admin after import.
