Revert "Removing Slack more (#7662)" (#7809)

This reverts commit 6d0efb558f.
2026-02-04 03:11:21 +01:00 · 2024-02-14 13:45:46 +00:00
parent e795817f5a
commit 145ee353a6
43 changed files with 122 additions and 151 deletions
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@
 <p align="center">
  <a href='http://makeapullrequest.com'><img alt='PRs Welcome' src='https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=shields'/></a>
  <img alt="GitHub contributors" src="https://img.shields.io/github/contributors/posthog/posthog.com"/>
-  <a href='https://posthog.com/questions'><img alt="Join Community" src="https://img.shields.io/badge/slack%20community-join-blue"/></a>
+  <a href='https://posthog.com/slack'><img alt="Join Slack Community" src="https://img.shields.io/badge/slack%20community-join-blue"/></a>
  <img alt="GitHub commit activity" src="https://img.shields.io/github/commit-activity/m/posthog/posthog.com"/>
  <img alt="GitHub closed pull requests" src="https://img.shields.io/github/issues-pr-closed/posthog/posthog.com"/>
 </p>
--- a/STYLEGUIDE.md
+++ b/STYLEGUIDE.md
@@ -70,7 +70,7 @@ We talk a lot about "third-party cookies". And that's how we spell them. Same fo

 Don't just write "You can contact us to learn more" and not link it to anything.

-Write "To learn more, [join our community](https://posthog.com/questions)."
+Write "To learn more, [join our  community](https://posthog.com/questions)."

 **The backtick is your friend**

--- a/contents/application-received.md
+++ b/contents/application-received.md
@@ -20,4 +20,4 @@ We will email you within 48 hours to confirm your application is accepted.

 ## Questions?

-Feel free to [send us feedback](https://app.posthog.com/home#supportModal), [ask questions](/questions), or join [our community](/questions).
+Feel free to [send us feedback](https://app.posthog.com/home#supportModal), [ask questions](/questions), or join [our community page](/posts).
--- a/contents/blog/aruba-hackathon.md
+++ b/contents/blog/aruba-hackathon.md
@@ -57,7 +57,7 @@ On the whole, Max gives useful answers – even when dealing with complex questi

 ![maxai](../images/blog/aruba/max-ai.jpeg)

-That said, Max isn't immune to hallucinating solutions – or even URLs for docs that don't exist – if it doesn't know the answer. It's a work in progress, but we've released Max in our community as a beta.
+That said, Max isn't immune to hallucinating solutions – or even URLs for docs that don't exist – if it doesn't know the answer. It's a work in progress, but we've released Max on [our community page](/posts) as a beta. Drop him a DM! 

 Check out the [MaxAI repo](https://github.com/PostHog/max-ai) for more info.

--- a/contents/blog/collaborating-on-posthog.md
+++ b/contents/blog/collaborating-on-posthog.md
@@ -83,7 +83,7 @@ A very user-friendly way of keeping users updated on these metrics is by integra

 You've seen the typical Medium post with a graph, well we have too and we hate they're not PostHog graphs. But aside from that superficial argument, teams have different workflows and tools where product context is shared (e.g. an intranet, Notion, Google Docs, code repositories, blog posts). Usually product decisions are at least data-informed (and we do hope this will help drive this behavior further), so we want to make sure that the context from product data is properly shared, accessible and preserved. In particular, we also want to make sure these context remains up-to-date.

-As always, we welcome and highly encourage you to share any feedback you may have about this or any other feature. Give us a shout in our [community](/questions) or join us directly for a [call](https://calendly.com/posthog-feedback) with our Product or Engineering team.
+As always, we welcome and highly encourage you to share any feedback you may have about this or any other feature. Give us a shout in [our community page](/posts) or join us directly for a [call](https://calendly.com/posthog-feedback) with our Product or Engineering team.

 <div style="border: 1px solid #D9D9D9; margin-bottom: 16px; margin-top: 16px;"></div>

--- a/contents/blog/customer-support-at-posthog.md
+++ b/contents/blog/customer-support-at-posthog.md
@@ -42,7 +42,7 @@ Its core UX is delightful and straightforward to use, making it easy to onboard
 It syncs all support tickets to Slack so our team can respond directly from the platform. Customer support teams are exempt from our [meeting-free days](https://posthog.com/blog/meetings) policy.
 It tracks stats around the number and types of tickets we receive (about 30 a day), how long it takes us to close each ticket (about an hour on average, accounting for complexity and time zones), and other useful analytics.

-Beyond Papercups and our [community](https://posthog.com/questions), we also receive support queries via email (sent to hey@posthog.com), GitHub (where our team spends most of their time), and very rarely via [social media](https://twitter.com/PostHog). We’ve found that within the context of businesses like ours, social media queries are usually a sign that normal communication or helpdesk channels have failed - and startups should avoid this as much as possible.
+Beyond Papercups and our [external Slack channel](https://posthog.com/slack), we also receive support queries via email (sent to hey@posthog.com), GitHub (where our team spends most of their time), and very rarely via [social media](https://twitter.com/PostHog). We’ve found that within the context of businesses like ours, social media queries are usually a sign that normal communication or helpdesk channels have failed - and startups should avoid this as much as possible.

 ## Are open-source support models expensive?

--- a/contents/blog/group-analytics-launch.md
+++ b/contents/blog/group-analytics-launch.md
@@ -47,7 +47,7 @@ You can even use groups with [feature flags](/docs/user-guides/feature-flags) to

 Group Analytics has been released as a [premium feature](/pricing) and is available now for both PostHog Scale, PostHog Enterprise, and PostHog Cloud users. If you’re on PostHog Cloud you can get started with groups immediately, while self-hosted instances will first need to be updated to the latest version. We’ve prepared some [documentation to help you get started with the new group types](/docs/user-guides/group-analytics) and illustrate some popular use-cases. 

-As always, we welcome any feedback you have as an issue in [the GitHub repo](https://github.com/PostHog), or in the [PostHog community](/questions).  
+As always, we welcome any feedback you have as an issue in [the GitHub repo](https://github.com/PostHog), or in [our community page](/posts).  

 > PostHog is an open source analytics platform you can host yourself. We help you build better products faster, without user data ever leaving your infrastructure.

--- a/contents/blog/hosthog-blog.md
+++ b/contents/blog/hosthog-blog.md
@@ -36,7 +36,7 @@ There’s no dress code, but we will expect everyone to adhere to [our standard

 ## I don’t live in London. Where will the next HostHog be?

-We definitely plan to host more events in the future, but we don’t yet know when or where they will be. If you’d like to suggest a location, or have any other feedback then just let us know in [the PostHog community](/questions). 
+We definitely plan to host more events in the future, but we don’t yet know when or where they will be. If you’d like to suggest a location, or have any other feedback then just let us know in [our community page](/posts). 

 ## Do I need to RSVP?

@@ -44,7 +44,7 @@ This is a free event with limited capacity, so we very strongly encourage that y

 ## Did you say free drinks and pizza?

-Yes! The offers a great selection of beers, wines and cocktails, as well as non-alcoholic options and tasty food. We can’t guarantee we can accommodate for any allergies or intolerances, but let us know in [the community](/questions) and we’ll try our best.
+Yes! The offers a great selection of beers, wines and cocktails, as well as non-alcoholic options and tasty food. We can’t guarantee we can accommodate for any allergies or intolerances, but let us know in [our community page](/posts) and we’ll try our best.

 ## I have another question...

--- a/contents/blog/how-to-work-out-what-users-need.md
+++ b/contents/blog/how-to-work-out-what-users-need.md
@@ -54,7 +54,7 @@ Another option to a scaled survey is to hold a focus group - a cross between the
 ### How does PostHog do this?
 In addition to collecting user feedback through direct conversations, we occasionally run surveys via our Slack community to find out how we're doing. We use this primarily as a tool for collecting ideas on topics outside of our core product, such as new community or marketing iniatives. 

-Want to find out more about our community? You can [join the PostHog questions](/questions) today!
+Want to find out more about our community? You can join [our community page](/posts) today!

 ## Metrics
 Monitor how people are using your product,  as they may be getting stuck when trying to accomplish something. You can piece together key pieces of information from success metrics to see what differs between users who are successful and those who are not, to shed light on unmet user needs.
--- a/contents/blog/open-source-business-models.md
+++ b/contents/blog/open-source-business-models.md
@@ -24,7 +24,7 @@ Just one thing: **you need to build a community.**

 Open-source requires a decently-sized, highly engaged community for any business model to work. People have to believe in your solution enough to contribute code, comments, or cash to it. If money is a priority for your business, open-source might not be the path for you.

-At PostHog, we’ve been fortunate enough to build an engaged community of contributors over the years, and we celebrate our top contributors with each new release. You can check out our [contributor page](/contributors), see our [GitHub repo](http://github.com/PostHog/), and join our [community](/questions) of users.
+At PostHog, we’ve been fortunate enough to build an engaged community of contributors over the years, and we celebrate our top contributors with each new release. You can check out our [contributor page](https://posthog.com/contributors), see our [GitHub repo](http://github.com/PostHog/), and join our [Slack community](https://posthog.com/slack) of users.

 Let’s now look at how we’ve managed to turn a buck with PostHog over the past few months — plus 3 other business models to explore for your own product.	

--- a/contents/blog/posthog-altinity-announce.md
+++ b/contents/blog/posthog-altinity-announce.md
@@ -30,7 +30,7 @@ In addition to providing training and support, Altinity can also offer [Altinity

 We think this partnership with Altinity is exciting because, while self-hosted deployments offer many unique benefits — such as better data capture and [data control](/customers/vendasta) — they can also be challenging to set up and maintain. Altinity is the ideal middle ground, enabling you to retain full control over your data while experts manage your ClickHouse for you!

-You can find out more about our partnership with Altinity in the PostHog marketplace, where we’ll soon add even more exciting partners to help you get even more from your PostHog deployment. Until then, we’d love to hear your feedback in [the community!](/questions)
+You can find out more about our partnership with Altinity in the PostHog marketplace, where we’ll soon add even more exciting partners to help you get even more from your PostHog deployment. Until then, we’d love to hear your feedback in [our community page](/posts).

 > PostHog is an open source analytics platform you can host yourself. We help you build better products faster, without user data ever leaving your infrastructure.

--- a/contents/blog/secrets-of-posthog-query-performance.md
+++ b/contents/blog/secrets-of-posthog-query-performance.md
@@ -177,6 +177,6 @@ Some projects currently in the pipeline are:
 -   **Smart caching time-series queries** - PostHog dashboards continually refresh data to show up-to-date graphs. However this results in a lot of repeated work, slowing down queries. By changing semantics around user properties and identifying users, we will be able to start smartly re-using past results when re-calculating queries.
 -   **Better JSON support in ClickHouse** - [This feature](https://github.com/ClickHouse/ClickHouse/issues/23516) has been experimentally released in ClickHouse 22.3 and will unlock the benefits of materialized columns with much less complexity.

-> Interested in chatting about ClickHouse performance or working on similar problems? Join our [community](/questions).
+> Interested in chatting about ClickHouse performance or working on similar problems? Send me an email: [karl+perf@posthog.com](mailto:karl+perf@posthog.com) or join [our community page](/posts).

 <ArrayCTA />
--- a/contents/blog/seed-grow-scale-devrel.mdx
+++ b/contents/blog/seed-grow-scale-devrel.mdx
@@ -58,7 +58,7 @@ PostHog has seen significant growth over the past year resulting in a [Series B
 In the near term, our AAARRRP goals are Activation, Retention, Referral, and Product. Instead of narrowing in on specific activities, we've broadly mapped the priorities as:

 1. **Oversee documentation**: This isn't about dictating how documentation is written or being a gatekeeper. It's about encouraging and enabling consistency, having the time to iterate on content that could otherwise become stale, and identifying gaps based on analysis, feedback, or utilizing team experience. DevRel, much like our [amazing design team](/handbook/small-teams/website-docs), can function as a service team with people deployed to the small team that most requires them at that time.
-2. **Catalyze our community**: We have a thriving community across [our GitHub repos](https://github.com/posthog) and the [PostHog community](/questions). On GitHub, we reward contributions with thanks on our READMEs, a listing on the [Contributors page](/contributors) of our website, and credit for our [merch store](/merch). But we want to do more to build upon this fantastic foundation because [community is core to our business](/handbook/strategy/business-model#why-would-you-work-on-the-community-edition).
+2. **Catalyze our community**: We have a thriving community across [our GitHub repos](https://github.com/posthog) and the [PostHog community page](/posts). On GitHub, we reward contributions with thanks on our READMEs, a listing on the [Contributors page](/contributors) of our website, and credit for our [merch store](https://merch.posthog.com). But we want to do more to build upon this fantastic foundation because [community is core to our business](/handbook/strategy/business-model#why-would-you-work-on-the-community-edition).
 3. **Engage with broader developer communities**: Right now, the only community we actively engage with is the one we've built. We need to expand our reach and build relationships within communities that will benefit from the PostHog platform.

 ## What Developer Relations roles do you need?
--- a/contents/blog/sessions-removal.md
+++ b/contents/blog/sessions-removal.md
@@ -47,7 +47,7 @@ From the context above, we decided to take the following actions:
 In addition to the changes above, we're also significantly improving recordings ingestion and the playback experience. This will make sure more sessions are captured and that you can seamlessly find the relevant parts of a recording.


-> 💡 **Not seeing these changes yet?** We're A/B testing some of these changes in PostHog Cloud, you may still not be in the release group. Please [contact us](/questions) if you'd like to be included. If you're on a self-hosted deployment of PostHog please keep an eye out for the next release.
+> 💡 **Not seeing these changes yet?** We're A/B testing some of these changes in PostHog Cloud, you may still not be in the release group. Please [contact us](/posts) if you'd like to be included. If you're on a self-hosted deployment of PostHog please keep an eye out for the next release.

 ## What's next?
 We are considering full support for session-based behavioral analytics and want to gather more context on the use cases for this. In particular, we want to make sure users have flexibility around their own concept of sessions, support a full range of analytics (e.g. session count, duration, multi-device sessions), etc.
--- a/contents/blog/the-posthog-array-1-0-11.md
+++ b/contents/blog/the-posthog-array-1-0-11.md
@@ -100,7 +100,7 @@ For a full breakdown of the changes and updates, please see our [changelog](http

 ### [Filtering by date and events in funnels](https://github.com/PostHog/posthog/issues/444)

-This was one of 4 issues raised by [jeremynevans](https://github.com/jeremynevans) at Savvy – it was raised in the [community](/questions) and resulted in an excellent conversation with Tim resulting in more feature requests which is amazing.
+This was one of 4 issues raised by [jeremynevans](https://github.com/jeremynevans) at Savvy – it was raised in [our community page](/posts) and resulted in an excellent conversation with Tim resulting in more feature requests which is amazing.

 He is also using PostHog for analytics on [Crowd Cure](https://crowd-cure.com/) to help build the largest clinical trial dataset to yet to help with the Coronavirus crisis – check it out on [Producthunt](https://www.producthunt.com/posts/crowdcure-covid-19).

--- a/contents/blog/the-posthog-array-1-14-0.md
+++ b/contents/blog/the-posthog-array-1-14-0.md
@@ -74,7 +74,7 @@ Prior to this version, we denoted the importance of this in our Docs, but did no

 Many of our deployments generate and set this key by default, so that you will not need to worry about it. This is the case with our [Heroku One-Click deployment](/docs/self-host/deploy/heroku), for example. However, other methods may not automatically do this (we're working on it!). As such, if you run into any issues when updating PostHog, make sure you have a unique `SECRET_KEY` set. 

-You can find more information about this on our ['Securing PostHog' page](/docs/self-host/configure/securing-posthog#secret-key) and should always feel welcome to ask any questions on our [community](/questions).
+You can find more information about this on our ['Securing PostHog' page](/docs/self-host/configure/securing-posthog#secret-key) and should always feel welcome to ask any questions on our [our community page](/posts).


 ## Bug Fixes and Performance Improvements
--- a/contents/blog/the-posthog-array-1-17-0.md
+++ b/contents/blog/the-posthog-array-1-17-0.md
@@ -100,7 +100,7 @@ A roadmap for various retention improvements that will significantly increase th

 ## PostHog News

-Our community continues to be as awesome as ever, providing valuable feedback and helping out with issues, pull requests, and discussions on our [community](/questions).
+Our community continues to be as awesome as ever, providing valuable feedback and helping out with issues, pull requests, and discussions on [our community page](/posts).

 This week, we want to give a special shoutout to [Adam](https://github.com/adamb70), who got 2 PRs merged and wrote an article about integrating PostHog on their website. 

--- a/contents/blog/the-posthog-array-1-29-0.md
+++ b/contents/blog/the-posthog-array-1-29-0.md
@@ -86,7 +86,7 @@ If you're interested in better measuring your user engagement, DAU/WAU, WAU/MAU

 ### Deprecation notice

-1. We're deprecating the sessions page and fully removing it in PostHog 1.30.0. Read more about it, [in this blog post](/blog/sessions-removal). If you have any feedback on this change, please [reach out](/questions).
+1. We're deprecating the sessions page and fully removing it in PostHog 1.30.0. Read more about it, [in this blog post](/blog/sessions-removal). If you have any feedback on this change, please [reach out](/posts).

 2. In PostHog 1.30.0 we will be introducing major improvements to the experience of using PostHog with multiple projects and that requires us to rework part of the API structure. Hence, in PostHog 1.29.0 the following API paths are deprecated, with straightforward replacements:

--- a/contents/blog/the-posthog-array-1-34-0.md
+++ b/contents/blog/the-posthog-array-1-34-0.md
@@ -105,7 +105,7 @@ Want to get involved? [Email us to schedule a 30 minute call](mailto:hey@posthog

 ## Contributions from the community

-Want to help improve PostHog? We always welcome contributions from our community! Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions).
+Want to help improve PostHog? We always welcome contributions from our community! Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts).

 We would also specifically like to thank PostHog team members [@hazzadous](https://github.com/hazzadous), [@guidoiaquinti](https://github.com/guidoiaquinti) and [@liyiy](https://github.com/liyiy) for their efforts on this particularly stubborn release.

--- a/contents/blog/the-posthog-array-1-35-0.md
+++ b/contents/blog/the-posthog-array-1-35-0.md
@@ -99,7 +99,7 @@ We always welcome contributions from our community and this time we want to than
 - [Joe Trollo](https://github.com/joetrollo), for Kafka and SASL support
 - [Björn and the rest of the Avo team](https://github.com/bjornj12), for the Avo plugin

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog
 Want to join us in helping make more products successful? We're currently hiring for remote candidates in any of the following roles:
--- a/contents/blog/the-posthog-array-1-36-0.mdx
+++ b/contents/blog/the-posthog-array-1-36-0.mdx
@@ -135,7 +135,7 @@ When self-hosting PostHog, it's crucial that all components are up and running,

 Restack is a platform for deployiong open-source software stacks on Kubernetes and is run by a team of open-source enthusiasts. It's a natural match for the PostHog Marketplace, where we've steadily grown the number of businesses offering services and support over the last few months.

-Restack enables you to deploy and benefit from a self-hosted PostHog instance, but without the maintenance busy work. Best of all, Restack Console can ensure deployments are [HIPAA](/docs/privacy/hipaa-compliance), FISMA and SOC2 compliant — handy if you deal with a lot of [PII](/blog/what-is-personal-data-pii). Find out more in [the Marketplace, or head to Restack's store listing for PostHog](https://www.restack.io/store/posthog) to find more great videos like the one above!
+Restack enables you to deploy and benefit from a self-hosted PostHog instance, but without the maintenance busy work. Best of all, Restack Console can ensure deployments are [HIPAA](/docs/privacy/hipaa-compliance), FISMA and SOC 2 compliant — handy if you deal with a lot of [PII](/blog/what-is-personal-data-pii). Find out more in [the Marketplace, or head to Restack's store listing for PostHog](https://www.restack.io/store/posthog) to find more great videos like the one above!

 ### Other improvements & fixes

@@ -171,7 +171,7 @@ We always welcome contributions from our community and this time we want to than
 -   @ParthGandhi for fixes to PostHog.com
 -   @JDConley for corrections to PostHog docs

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog

--- a/contents/blog/the-posthog-array-1-37-0.mdx
+++ b/contents/blog/the-posthog-array-1-37-0.mdx
@@ -142,7 +142,7 @@ We always welcome contributions from our community and this time we want to than
 -   @MichaelLampe for a correction to PostHog docs
 -   @girlProg for corrections to PostHog.com

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog

--- a/contents/blog/the-posthog-array-1-38-0.mdx
+++ b/contents/blog/the-posthog-array-1-38-0.mdx
@@ -136,7 +136,7 @@ We always welcome contributions from our community and this time we want to than
 - [@rafalmierzwiak](https://github.com/rafalmierzwiak), for adding some missing packages
 - [@hakubo](https://github.com/hakubo), for fixing the seemingly endless typos on the site

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog
 Want to join us in helping make more products successful? We're currently hiring for remote candidates in any of the following roles:
--- a/contents/blog/the-posthog-array-1-39-0.mdx
+++ b/contents/blog/the-posthog-array-1-39-0.mdx
@@ -135,7 +135,7 @@ We always welcome contributions from our community and this time we want to than
 - [@danielthedifficult](https://github.com/danielthedifficult) for fixing some issues with our open source version. 
 - [@nemobsis](https://github.com/nemobis) for adding to our GA site.

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog
 Want to join us in helping make more products successful? We're currently hiring for remote candidates in any of the following roles:
--- a/contents/blog/the-posthog-array-1-40-0.md
+++ b/contents/blog/the-posthog-array-1-40-0.md
@@ -78,7 +78,7 @@ We always welcome contributions from our community and this time we want to than
 - [Thebigbignooby](https://github.com/Thebigbignooby) for correcting an error in our documentation.
 - [Klamas1](https://github.com/klamas1) for adding nodeSelector and tolerations to hooks. 

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog
 Want to join us in helping make more products successful? We're currently hiring for remote candidates in any of the following roles:
--- a/contents/blog/the-posthog-array-1-41-0.md
+++ b/contents/blog/the-posthog-array-1-41-0.md
@@ -173,7 +173,7 @@ We always welcome contributions from our community and this time we want to than

 - [@jacobwgillespie], co-founder of [Depot](https://depot.dev/), for [moving us from Yarn 1 to Yarn 3](https://github.com/PostHog/posthog/pull/12520). A great PR!

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog
 Want to join us in helping make more products successful? We're currently hiring for remote candidates in any of the following roles:
--- a/contents/blog/the-posthog-array-1-42-0.md
+++ b/contents/blog/the-posthog-array-1-42-0.md
@@ -107,7 +107,7 @@ We always welcome contributions from our community and this time we want to than
 - @Demivan for [fixing a broken URL](https://github.com/PostHog/posthog.com/pull/4682)
 - @DavidODonovan for [fixing social sharing](https://github.com/PostHog/posthog.com/issues/4669)

-Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community](/questions). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!
+Do you want to get involved in making PostHog better? Check out our [contributing resources](/docs/contribute) to get started, or head to [our community page](/posts). We also have a [list of Good First Issues](https://github.com/PostHog/posthog/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) for ideas on where you can contribute!

 ## Open roles at PostHog
 Want to join us in helping make more products successful? We're currently hiring for remote candidates in the following role:
--- a/contents/customers/wittyworks.md
+++ b/contents/customers/wittyworks.md
@@ -53,6 +53,6 @@ While ready-made integrations were available for many tools, such as Sentry and

 [Witty Works’ Property Filter app](/integrations/property-filter) does this by deleting all configured properties inside an ingested event so that PostHog doesn’t collect any unwanted data. Running this app last in a chain makes sure that it applies to data bought in by any other apps too.

-This whole process was achieved with just 26 lines of code and was released to all PostHog users as a community app. Plus, because the app is open source like PostHog, the community has been able to enhance it even further — [the current version is now 44 lines of code and even came with tests](https://github.com/witty-works/posthog-property-filter-plugin/blob/dev/index.js) made by [the PostHog community](/questions)!  and has now been released to all PostHog users as a community app after a quick review from PostHog’s team. 
+This whole process was achieved with just 26 lines of code and was released to all PostHog users as a community app. Plus, because the app is open source like PostHog, the community has been able to enhance it even further — [the current version is now 44 lines of code and even came with tests](https://github.com/witty-works/posthog-property-filter-plugin/blob/dev/index.js) made by [the PostHog community](/posts)!  and has now been released to all PostHog users as a community app after a quick review from PostHog’s team. 

 “One of the advantages of being an open-source product is that we can collaborate with users and help them build exactly what they need,” said PostHog Software Engineer Yakko Majuri. “By building their own apps and contributing to [our library](/integrations), Witty Works has helped make PostHog a better product for everyone!”
--- a/contents/docs/apps/build/index.md
+++ b/contents/docs/apps/build/index.md
@@ -89,4 +89,4 @@ That's all for the crash course. There's a lot you can do with apps, such as run

 1. For in-depth information on all the special functions, check out [the developer reference docs](/docs/apps/build/reference).
 2. For building your own app from start to finish, check out [our tutorial](/docs/apps/build/tutorial).
-3. To ask questions or collaborate with others in the community, join [our community](/questions).
+3. To ask questions or collaborate with others in the community, join [our community page](/posts).
--- a/contents/docs/cdp/build/index.md
+++ b/contents/docs/cdp/build/index.md
@@ -91,4 +91,4 @@ That's all for the crash course. There's a lot you can do with apps, such as run

 1. For in-depth information on all the special functions, check out [the developer reference docs](/docs/apps/build/reference).
 2. For building your own app from start to finish, check out [our tutorial](/docs/apps/build/tutorial).
-3. To ask questions or collaborate with others in the community, join [our community](/questions).
+3. To ask questions or collaborate with others in the community, join [our community page](/posts).
--- a/contents/docs/glossary.mdx
+++ b/contents/docs/glossary.mdx
@@ -165,11 +165,11 @@ Insights are a core feature of PostHog which enable you to query analytics and d
 Users within your team. Often you'll want to remove internal users from your analysis to avoid swaying results with biased data. [Find out how to filter internal users from your PostHog insights](/tutorials/filter-internal-users).

 #### Issues
-What we use to log bugs, discuss ideas and make decisions on Github. Issues are better than a Slack message, but worse than a [pull request](/manual/glossary#pull-request). 
+What we use to log bugs, discuss ideas and make decisions on Github. Issues are better than a [community question](/posts), but worse than a [pull request](/manual/glossary#pull-request). 

 ## J 

-> We couldn't think of anything which begins with a J. If you can think of something which should go here, let us know by [making a GitHub issue](https://github.com/PostHog) or [sending us a message](/questions)!
+> We couldn't think of anything which begins with a J. If you can think of something which should go here, let us know by [making a GitHub issue](https://github.com/PostHog) or join [our community page](/posts).

 ## K

@@ -339,7 +339,7 @@ Analytics services which focus on tracking anonymous users and how they interact

 ## X 

-> We couldn't think of anything which begins with an X. If you can think of something which should go here, let us know by [making a GitHub issue](https://github.com/PostHog) or [sending us a message](/questions)!
+> We couldn't think of anything which begins with an X. If you can think of something which should go here, let us know by [making a GitHub issue](https://github.com/PostHog) or join [our community page](/posts).

 ## Y 

@@ -348,4 +348,4 @@ Year-on-Year. Normally this is used to track your performance from one year to t

 ## Z 

-> We couldn't think of anything which begins with a Z. If you can think of something which should go here, let us know by [making a GitHub issue](https://github.com/PostHog) or [sending us a message](/questions)!
+> We couldn't think of anything which begins with a Z. If you can think of something which should go here, let us know by [making a GitHub issue](https://github.com/PostHog) or join [our community page](/posts).
--- a/contents/docs/self-host/index.mdx
+++ b/contents/docs/self-host/index.mdx
@@ -104,7 +104,7 @@ docker logs <container_name>

 The best place to start looking is in the `web` container, which runs all the database migrations and will produce an error if any have failed.

-> Running into issues with deployment? Ask a [question here](/questions) or check out our [community](/questions) to get help.
+> Running into issues with deployment? Ask a [question here](/questions) or check out [our community page](/posts) to get help.

 ## Upgrading

--- a/contents/docs/session-replay/mobile.mdx
+++ b/contents/docs/session-replay/mobile.mdx
@@ -2,7 +2,7 @@
 title: Mobile Recording
 ---

-> 🚧 **NOTE:** Mobile Recording is currently **only available on iOS** and is considered `alpha`. We are keen to gather as much feedback as possible so if you try this out please let us know and reach out in our [community](/questions) to share your experience with it.
+> 🚧 **NOTE:** Mobile recording is currently **only available on Android** and is considered `beta`. We are keen to gather as much feedback as possible so if you try this out please let us know. You can send feedback via the [in-app support panel](https://us.posthog.com#panel=support%3Afeedback%3Asession_replay%3Alow) or one of our other [support options](/docs/support-options).


 # Overview
@@ -11,134 +11,101 @@ Mobile Session Recording allows you to record user sessions on mobile devices. T

 ## How it works

-We have taken our time to make sure that we can provide a useful and detailed recording experience whilst keeping the performance and security of your app as a top priority. By default the configuration is somewhat resritive with automatic masking and wifi-only uploads to ensure that we don't negatively impact the user experience. This can then be configured to be more or less restrictive depending on your needs.
+We have taken our time to make sure we provide a useful and detailed recording experience whilst keeping the performance and security of your app as a top priority. By default, the configuration is restrictive with automatic masking.

 #### Screen recording

-Mobile Recording is primarily done using native APIs to grab an image copy of the primary View in the app. This is done carefully so as not to affect performance in any way a user may notice and at a rate of 1 frame per second, so as not to generate too much data. The image is compressed and uploaded to PostHog, by default only over wifi to ensure we aren't negatively impacting the users data plan. 
+Mobile recording is primarily done using native APIs to grab the view hierarchy state when the screen is drawn. This is done carefully so as not to affect performance in any way a user may notice.

-If a `redactionMode` is specified, the image is then processed to remove sensitive information. The different modes work as follows:
-* `selective` (default) - Only redact views with an accessibilityId matching what is specified in `redactionTags`.
-* `automatic` - Redact all views with the name matching `redactionViews` and all classes matching `redactionClasses`. Some sensible defaults are provided to capture anything Text like.
-* `wireframe` - Renders a "wireframe" representation of the views instead of an captured image. This is great for highly sensitive environments where you still wan't to get a sense of user behaviour but don't want to capture any sensitive information.
+The view hierarchy is transformed to a JSON data structure and later rendered as a HTML [wireframe](https://www.figma.com/resource-library/what-is-wireframing/). Since it is a wireframe, the UI won't have the original look and feel but it should be close enough to understand the user's behaviour.

 #### Network recording

-Network requests are recorded using the "swizzling" technique to intercept all `UrlSession` requests - the basis of all network requests in iOS. Only metric-like data is currently gathered to give a picture of speed, size and response code. No data is captured from the request or response body.
+Network requests are recorded using the `PostHogOkHttpInterceptor` interceptor ([OkHttp only](https://github.com/square/okhttp/)). Only metric-like data is currently gathered to give a picture of speed, size and response code. No data is captured from the request or response body.

 # Installation

-### Via Swift Package Manager
-
-Currently the only way to install the `beta` of the PostHog Recording iOS SDK is via Swift Package Manager. To do so, follow these steps:
-
-1. In Xcode, select File > Add Packages.
-2. Enter `https://github.com/posthog/posthog-ios` in the search bar.
-3. Select the dependency rule `branch` and enter `feat/mobile-recordings` as the value.
-4. Select the your project to add it to and click **Add Package**
-
-
-### Setup with Objective C
-
-
-In your AppDelegate file add the following:
-
-```objc
-#import "AppDelegate.h"
-// ...
-
-@import PostHog; // Add this import
-
-
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
-{
-    // ...other code
-
-    PHGPostHogConfiguration *configuration = [PHGPostHogConfiguration configurationWithApiKey:@"YOUR_API_KEY" host:@"https://app.posthog.com"];
-
-    // Any standard PostHog config options
-    configuration.captureApplicationLifecycleEvents = YES; // Record certain application events automatically!
-    configuration.captureScreenViews = YES; // Capture screen views automatically!
-    
-    // Any Recording specific config options
-    configuration.recording.screenRecordingEnabled = YES; // Record the screen
-    configuration.recording.networkRecordingEnabled = YES; // Record network requests
-    configuration.recording.redactionMode = ScreenRecorderMaskingModeAutomatic; // Mask screen recordings automatically
-
-    [PHGPostHog setupWithConfiguration:configuration];
-}
-
+Add the dependency.

+```gradle_kotlin file=app/build.gradle.kts
+implementation("com.posthog:posthog-android:$latestVersion")
 ```

-### Setup with Swift
+Initialize the SDK in the `Application` class.

+```android_kotlin
+import android.app.Application
+import com.posthog.android.PostHogAndroid
+import com.posthog.android.PostHogAndroidConfig

-```swift
-// AppDelegate.swift
-import Foundation
-import UIKit
-import PostHog
+class SampleApp : Application() {

-class AppDelegate: NSObject, UIApplicationDelegate {
-    func application(_: UIApplication, didFinishLaunchingWithOptions _: [UIApplication.LaunchOptionsKey: Any]? = nil) -> Bool {
-        let configuration = PHGPostHogConfiguration(apiKey: "<ph_project_api_key>", host: "<ph_instance_address>")
+    companion object {
+        const val POSTHOG_API_KEY = "<ph_project_api_key>"
+        // usually 'https://app.posthog.com' or 'https://eu.posthog.com'
+        const val POSTHOG_HOST = "<ph_instance_address>"
+    }

-        configuration.captureApplicationLifecycleEvents = true; // Record certain application events automatically!
-        configuration.captureScreenViews = true; // Capture screen views automatically!
-        
-        configuration.recording.screenRecordingEnabled = true
-        configuration.recording.logRecordingEnabled = true
-        configuration.recording.networkRecordingEnabled = true
-        configuration.recording.redactionMode = .automatic
+    override fun onCreate() {
+        super.onCreate()

-        return true
+        val config = PostHogAndroidConfig(
+            apiKey = POSTHOG_API_KEY,
+            host = POSTHOG_HOST // TIP: `host` is optional if you use https://app.posthog.com
+        )
+        config.sessionReplay = true
+        PostHogAndroid.setup(this, config)
    }
 }
 ```

+Add the OkHttp Interceptor.

-#### SwiftUI
-If you haven't already, crate the `AppDelegate.swift` file mentioned above and then in your `App` file add the following:
+```android_kotlin
+import com.posthog.PostHogOkHttpInterceptor
+import okhttp3.OkHttpClient

-```swift
-import SwiftUI
-
-@main
-struct AboutMeApp: App {
-    @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate // Add this if not already there
-    
-    var body: some Scene {
-        WindowGroup {
-            ...
-        }
-    }
-}
+private val client = OkHttpClient.Builder()
+    .addInterceptor(PostHogOkHttpInterceptor(captureNetworkTelemetry = true))
+    .build()
 ```

+# Limitations
+
+* Requires the PostHog Android SDK version >= [3.1.0](https://github.com/PostHog/posthog-android/releases/tag/3.1.0) - use the latest version.
+* Requires Android API >= 26, otherwise it's a NoOp.
+* Not compatible with Jetpack Compose.
+* Generates wireframe representations of a users screen, not a video recording or a screenshot.
+  * Custom views are not fully supported.
+* WebView is not supported, a placeholder will be shown.
+* React Native and Flutter for Android aren't supported.
+* [Authorized Domains for Replay](https://us.posthog.com/settings/project-replay#replay-authorized-domains) has to be disabled, for now, or create a new testing project to not disrupt your current project configuration.
+* Let us know when you're ready to view the recordings. While replay is in beta there's still some setup on our side before you can playback the sessions. You can send feedback via the [in-app support panel](https://us.posthog.com#panel=support%3Afeedback%3Asession_replay%3Alow) or one of our other [support options](/docs/support-options)

 # Recording specific configuration

-```swift
-// The values shown are the defaults
-let config = PostHogRecorderConfig(
-    // Whether to enable recording. If false, all other options are ignored
-    screenRecordingEnabled: true,
-    // Whether to enable log recording. Logs with OSLog will be automatically recorded or you can log directly with PostHog.shared.recorder.log()
-    logRecordingEnabled: true,
-    // Records network requests via swizzling of NsUrlSession.
-    networkRecordingEnabled: true,
-    // What level of redcaction to perform
-    // -> .selective = only redact manually specified views with an accessibilityId matching what is specified in `redactionTags`.
-    // -> .automatic = redact all views with the name matching `redactionViews` and all classes matching `redactionClasses`
-    // -> .wireframe = renders a "wireframe" of the view, without any text or images
-    redactionMode: .selective,
-    redactionTags: ["ph-no-capture"],
-    redactionViews: PostHogRecorderConfig.DefaultRedactionViews,
-    redactionClasses: PostHogRecorderConfig.DefaultRedactionClasses,
-    // Hosts to ignore when recording network requests. By default the PostHog API host is ignored
-    ignoreNetworkHosts: []
-)
+SDK configurations during the SDK initialization.
+
+```android_kotlin
+val config = PostHogAndroidConfig(apiKey = POSTHOG_API_KEY).apply {
+    // enable session recording, requires enabling on the project configuration as well.
+    sessionReplay = true
+    // all texts are masked (default is enabled)
+    sessionReplayConfig.maskAllTextInputs = false
+    // all images are placeholders (default is enabled)
+    sessionReplayConfig.maskAllImages = false
+    // capture logs automatically (default is enabled)
+    sessionReplayConfig.captureLogcat = true
+}
 ```

+[View](https://developer.android.com/reference/android/view/View) configuration, if setting the [View#tag](https://developer.android.com/reference/android/view/View#tags) to `ph-no-capture`, the image will be a placeholder.

+```xml
+<ImageView
+    android:id="@+id/imvProfilePhoto"
+    android:layout_width="200dp"
+    android:layout_height="200dp"
+    android:tag="ph-no-capture"
+/>
+```
--- a/contents/faq.mdx
+++ b/contents/faq.mdx
@@ -66,7 +66,7 @@ PostHog is a [well-funded](/handbook/strategy/investors) project with [thousands

 Yes. We release new versions about every two weeks and have a world-class team working daily on making the product better. It's [easy to update](/docs/runbook/upgrading-posthog), and the software will alert you to new updates within the application.

-Pro-tip: follow us on [Twitter](https://twitter.com/PostHog) or join our [community](/questions) to keep up with our latest features. You can also [sign up to our newsletter](https://newsletter.posthog.com/subscribe)!
+Pro-tip: follow us on [Twitter](https://twitter.com/PostHog) or join [our community page](/posts) to keep up with our latest features. You can also [sign up to our newsletter](https://newsletter.posthog.com/subscribe)!

 ### How many companies use it / How many well-known companies use it?

@@ -134,7 +134,7 @@ The cool thing about PostHog is that you can go live into production without hav

 ### What's the community like?

-Active and growing! We have thousands of stars on GitHub (<span className="relative top-2"><StarRepoButton /></span> to be exact). There is a [forum](/questions) with daily conversations, and our repos have [issues](https://github.com/PostHog/posthog/issues) raised every day.
+Active and growing! We have thousands of stars on GitHub (<span className="relative top-2"><StarRepoButton /></span> to be exact). There is a [community page](/posts) with daily conversations, and our repos have [issues](https://github.com/PostHog/posthog/issues) raised every day.

 ### How is this different from the other product analytics tools?

--- a/contents/founders/making-something-people-want.md
+++ b/contents/founders/making-something-people-want.md
@@ -98,7 +98,7 @@ The reason they were willing to let us implement something with so little value,

 ### 3. User uses it and gives feedback

-We set up a [community](/questions) group.
+We set up a [community Slack](../slack) group.

 When new customers joined, we'd create a private channel. In the early days when we were a team of two, this is where users went from my responsibility, to Tim's.

--- a/contents/founders/story-about-pivots.md
+++ b/contents/founders/story-about-pivots.md
@@ -8,7 +8,9 @@ featuredImageType: full
 tags:
  - Founders
  - Product-market fit
-  - Product  
+  - Product
+crosspost:
+  - Blog    
 ---

 PostHog has pivoted _a lot_.
@@ -174,7 +176,7 @@ When did we know this idea was right?

 When we saw real life actual people on the internet start using our thing, without us having to manually get them to do so.

-Even better was seeing a community starting to appear. We got [our first ever issue from someone else](https://github.com/PostHog/posthog/issues/100) on February 15th, and our first community discussion [on the 23rd](https://github.com/PostHog/posthog/issues/149). This started to spiral. We now get a stream of issues every day in our [PostHog community](/questions) or the [repo](https://github.com/posthog/posthog).
+Even better was seeing a community starting to appear. We got [our first ever issue from someone else](https://github.com/PostHog/posthog/issues/100) on February 15th, and our first community discussion [on the 23rd](https://github.com/PostHog/posthog/issues/149). This started to spiral. We now get a stream of issues every day in [our community page](/posts) or the [repo](https://github.com/posthog/posthog).

 Growth suddenly went from being the hardest part of what we were doing, to being quite easy - we started getting swamped with product work. The problem was keeping up rather than getting something to happen.

--- a/contents/handbook/company/brand-assets.md
+++ b/contents/handbook/company/brand-assets.md
@@ -29,7 +29,7 @@ The @2x version of PNGs are designed for [hi-dpi (or "Retina") screens](https://

 ![Logo usage examples](/brand/logo-usage.png)

-If you have any questions or need clarification about which version to use, ask Cory, or reach out in the [PostHog community](/questions) and we'll be happy to help.
+If you have any questions or need clarification about which version to use, ask Cory, or reach out in [our community page](/posts) and we'll be happy to help.

 ## Typography

--- a/contents/handbook/growth/sales/sales-operations.md
+++ b/contents/handbook/growth/sales/sales-operations.md
@@ -32,7 +32,7 @@ For customers that sign up themselves, and begin using the product, we provide a
 1. [Docs](/docs)
 1. [Tutorials](/tutorials)
 1. [Pre-recorded demo](/book-a-demo)
-1. [Community](/questions)
+1. [Community page](/posts)

 Additionally, all users can contact us for support/bugs/feedback using the `?` icon in the top right of the PostHog app. This is routed to the appropriate team in Zendesk.

--- a/contents/tutorials/build-site-app.md
+++ b/contents/tutorials/build-site-app.md
@@ -11,7 +11,7 @@ Site apps make it quick and easy to add features such as forms and banners to yo

 In this tutorial, we’ll teach you how to build a site app. If you're looking for a broader overview of apps, you can find it [in our docs](/docs/apps). Our app will show up on our product site as button users can click to send us a customizable message captured as a PostHog event. To complete this tutorial, you only need [Node installed](https://nodejs.org/en/download/) to build and run the app.

-> PostHog Cloud users cannot currently add custom or third-party apps for security reasons. Have an app you want to add to PostHog? [Let us know](/questions)!
+> PostHog Cloud users cannot currently add custom or third-party apps for security reasons. Have an app you want to add to PostHog? [Let us know](/posts)!

 ## Basic setup

--- a/contents/tutorials/build-your-own-posthog-app.md
+++ b/contents/tutorials/build-your-own-posthog-app.md
@@ -143,7 +143,7 @@ Finally, however you create your app, [let us know that it's ready for review](h

 ### Further reading

-Want to know more about building your own apps? Join [the PostHog community](/questions), where thousands of developers share ideas and app-building advice. 
+Want to know more about building your own apps? Join [our community page](/posts), where thousands of developers share ideas and app-building advice. 

 Alternatively, check out the following tutorials for more information in the mean time…

--- a/src/components/NextSteps/Steps.js
+++ b/src/components/NextSteps/Steps.js
@@ -89,8 +89,8 @@ export const InstallingPostHog = () => {
                    <h5>Hosting or deployment questions?</h5>
                    <p>
                        Join our{' '}
-                        <Link to="/questions" event="next steps - installing posthog: forum">
-                            community
+                        <Link to="/slack" event="next steps - installing posthog: Slack">
+                            Slack
                        </Link>{' '}
                        to ask questions directly to the PostHog team - or search for similar questions from others in
                        the community.
--- a/src/components/Startups/index.tsx
+++ b/src/components/Startups/index.tsx
@@ -148,7 +148,7 @@ export default function Startups() {
                                    follow steps 1-2 above!
                                </p>
                                <p className="mb-0">
-                                    In the meantime, why not join <Link to="/questions">our community</Link>?
+                                    In the meantime, why not join <Link to="/slack">our Slack community</Link>?
                                </p>
                            </>
                        }
--- a/src/pages/roadmap/sidecar.tsx
+++ b/src/pages/roadmap/sidecar.tsx
@@ -64,7 +64,8 @@ export default function RoadmapPage() {
                        <h3 className="font-bold text-5xl mb-8 xl:mt-0">How to install</h3>
                        <ol>
                            <li>
-                                Join our <Link to="/questions">community</Link>, and ask us for it.
+                                Join our <Link to="/slack">community chat</Link>, and join the #team-website-and-docs
+                                channel - the zip file is pinned in the channel.
                            </li>
                            <li>Download the zip file and unzip it.</li>
                            <li>
@@ -111,7 +112,8 @@ export default function RoadmapPage() {
                        </h3>

                        <p>
-                            For feedback, please join our <Link to="/questions">community</Link>, and post it there.
+                            For feedback, please join our <Link to="/slack">community chat</Link>, and post it in the
+                            #team-website-and-docs channel.
                        </p>
                        <p>
                            For bugs, <Link to="https://github.com/PostHog/sidecar/issues/new">create an issue</Link> in