Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bug Report: "how NRR/ commissions are calculated" link on CS How we work page 404s

Open Beginner friendly
  • Is something wrong?
#21,523 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
documentation

Research direction

Start with the CS “How we work” page and find the “how commissions are calculated” link in its “How NRR is calculated” section. Check the repository for the current commissions page path and update the link if the page moved; done when the link opens the page explaining the NRR and commission method instead of returning a 404.

Written by the indexing model from the issue text.

Description

Report

I was reading the CS "How we work" page (https://posthog.com/handbook/cs-and-onboarding/how-we-work) and clicked "how commissions are calculated" in the "How NRR is calculated" section. It goes to:

https://posthog.com/handbook/growth/revops/commissions

and returns a 404.

To reproduce:

  1. Go to /handbook/cs-and-onboarding/how-we-work
  2. Scroll to "How NRR is calculated"
  3. Click "how commissions are calculated"

What I checked:

  • /handbook/growth/revops/commissions and /handbook/growth/sales/commissions both 404
  • I didn't find an existing issue or PR mentioning commissions

Technical info

Chrome 155.0.8059.85 (arm64) on macOS 26.7.1.

Expected outcome, or solution

I'd expect the link to go to the page explaining how the NRR/commission method works.

If the page moved, the link just needs the new path.

/handbook/growth/revops/commissions
Image

/handbook/growth/sales/commissions
Image

Dominant language
TypeScript
Stars
1.2k
Forks
932
Avg merge
1d 10h
Merged PRs (30d)
666

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PostHog/posthog.com

All issues in PostHog/posthog.com

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.