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

This reverts commit 6d0efb5.

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>

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**
 

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).

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.
 

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>
 

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 [email protected]), 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 [email protected]), 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?
 

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.
 

contents/blog/hosthog-blog.md

@@ -36,15 +36,15 @@ 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?
 
 This is a free event with limited capacity, so we very strongly encourage that you RSVP in order to secure your spot. We will do our best to accommodate, but in the event we’re over-attended, we will give priority to those who have RSVPed. 
 
 ## 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...
 

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.

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.	
 

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.
 

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: [[email protected]](mailto:[email protected]) or join [our community page](/posts).
 
 <ArrayCTA />

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?

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.

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).
 

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

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. 
 

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:
 

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.