Add Discord goal to Q2 IRL Events objectives

[Zaltsman]

Changes

• Adds a new Q2 objective to team IRL objectives
• Introduces Discord as a live channel experiment for builder community engagement

Related to community thread

Checklist

• I've read the docs and/or content style guides.
• Words are spelled using American English
• Use relative URLs for internal links
• I've checked the pages added or changed in the Vercel preview build
• If I moved a page, I added a redirect in vercel.json

[github-actions]

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Apr 20, 2026 03:35PM

[github-actions]

Vale prose linter → found 4 errors, 7 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/teams/irl-events/objectives.mdx — 4 errors, 7 warnings, 0 suggestions

Line	Severity	Message	Rule
10:25	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
18:48	warning	'Luma' is a possible misspelling.	PostHogBase.Spelling
56:105	warning	Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept.	PostHogBase.ProductNames
56:183	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
56:203	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
63:29	warning	Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept.	PostHogBase.ProductNames
70:84	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
86:3	warning	'Templatized' is a possible misspelling.	PostHogBase.Spelling
86:45	warning	'collab' is a possible misspelling.	PostHogBase.Spelling
95:5	warning	'Sidequests' is a possible misspelling.	PostHogBase.Spelling
97:1	warning	'Sidequests' is a possible misspelling.	PostHogBase.Spelling

[joethreepwood]

Sounds great.

One thing I think might be worth thinking about early on though is: if it is successful and good stuff keeps happening in Discord, how can we be surfacing that elsewhere.

If users start sharing good feedback, for example, how do we flow that through to engineers. If they start sharing ideas for content, how do we capture that? If there are best practices and so on, how do we make that AI/Google indexable?

We don't need to worry too much here (the answer is something something AI, probably) but this was a key reason why I pushed us to move away from Slack and I think it'll be worth reflecting on lightly.

[Zaltsman]

To the first point about surfacing thing to our team - we're going to get a discord bot going in slack that will pipe content into our slack so that engineers who dont want to go to the discord can see / be tagged in relevant content.

The indexing question is a bigger one. I think we'll have to play around with the tools out there and learn as we go. Though, to be fair, we might just want to reframe our expectations. Just like our internal discussions in Slack are the non-indexed version of our culture/handbook, the discord can be the non-indexed version of our community (as opposed to social media, reddit, the forum, etc.)