Managing small teams

Last updated:

|Edit this page

Small team pages are managed in a few places:

  1. MDX files in the repo under /contents/teams/{team-name}
    • Quarterly goals, team-specific handbook content
  2. Team records in our CMS, with all fields editable directly on the small team page
    • Team photo, mission, crest
  3. Small team FAQs
    • Aggregated from team member profiles, and from our CMS

Team page content

Any MDX files in the repo will display below the team members and recently shipped sections.

Quarterly goals

We're moving toward having quarterly goals in their own MDX files, like 2024-Q1.mdx. This will allow us to show the current team goals, while displaying previous goals in an accordion.

Until then, when adding quarterly goals for a new quarter, add them to the index.mdx file and move the previous goals into a section below them (rather than deleting):

## Previous goals
<details>
<summary>Q3 2024 goals</summary>
### Goal 1
- Details
- More details
### Goal 2
- Details
- More details
</details>

See the Website & Vibes team's small team page as an example of how it will look.


Team management

Creating a new small team

Website steps

  1. Make sure you're logged in to your community account
  2. Navigate to /teams
  3. Click the New team button
  4. Fill in all fields
  5. Click Save & publish

Repo steps

  1. Create a directory for the team in /contents/teams/{team-name} and duplicate index.mdx and objectives.mdx from another team as a starting point
  2. Add the team's name to src/navs/index.js under the companyMenu section in alphabetical order under the Engineering or Not engineering heading

The new team will be added to the Teams page on the next build.

Editing a small team

  1. Make sure you're logged in to your community account
  2. Navigate to the small team page you wish to edit
  3. Click the Edit button (bottom right corner)
  4. Edit the desired fields
  5. Click Save

Add content to the small team's page

Visit the new small team page to:

  1. Add team members (Login, click the Edit button bottom-right)
  2. Assign the team lead (click the crown icon)
  3. Update the team photo and caption (click the team photo to upload)
  4. Update the team's mission
  5. Update the team crest (click Edit crest to customize your team's crest)

Other tasks

  1. Request a custom team crest from Lottie. Describe your team with a few adjectives, maybe physical tools that can be used in an illustration, and a sentence or two about what you do. She'll create two versions: a large one (for your small team's page) and a miniature version used in other places (like the careers page).
  2. Add the team's feature ownership to the feature list
  3. Create a new team on GitHub and remove the new members from their previous team
  4. Give that newly-created team Direct Access with Write permission to the posthog and posthog.com repositories, as well as any other repos they will be contributing to frequently. This allows team members request review from their team instead of having to tag members individually.
  5. Create the new feature/team-{team-name} labels on GitHub
  6. On Slack, create a new channel called #team-{team-name}. Add a new People > User group with the handle @team-{team-name}-folks. Add / Remove people from other groups as necessary.
  7. If there are existing forum topics or roadmap items, re-assign them to the new team.
    • Make sure there's a group in Zendesk for the new team, and add the zendeskGroupID to the team's record in Strapi so community questions are routed to the right team in Zendesk. (Ask the Website & Docs team for help here.)
  8. Update small team names in Ashby. These are used to categorize jobs by team on the careers page.

Managing a small team

To manage content on the small team page, see the Add content to the small team's page section above.

Removing a small team

Ask the Website & Docs team for help.

Questions?

Was this page useful?

Next article

Managing the company roadmap

Creating a new roadmap item Log in to Strapi Click Roadmap in the sidebar Click New Roadmap fields Title* The title of the roadmap item. Self-explanatory. Description A brief description of what the roadmap item intends to accomplish. Projected completion date / Date completed The projected completion/completion date of the roadmap item. If the “Complete” checkbox is checked, this field label will change from “Projected completion date” to “Date completed”. This field also controls where the…

Read next article