Updated Slack reference on our homepage and blog (#8)

content/blog/6k-stars-for-score/index.md

@@ -15,4 +15,4 @@ Keep an eye out on our blog and [socials](https://www.linkedin.com/company/score
 
 Thank you so much for your continued support and contribution – Score would not be possible without your involvement and your questions! 
 
-Happy new year by the Score Team! Keep up with us on [Slack](https://join.slack.com/t/scorecommunity/shared_invite/zt-1i2glkqkl-EnjSWSCgYUyaEGwmDYBZZQ), [GitHub](https://github.com/score-spec/spec/discussions) and on [our socials](https://www.linkedin.com/company/score-dev/).
+Happy new year by the Score Team! Keep up with us in the [#score channel on the CNCF Slack](https://slack.cncf.io), [GitHub](https://github.com/score-spec/spec/discussions) and on [our socials](https://www.linkedin.com/company/score-dev/).

content/blog/celebrating-500-stars-on-github/index.md

@@ -13,6 +13,6 @@ We are ecstatic that so many eyes are on our project so early on. This indicates
 
 Score is still a work in progress. We are excited for the work we will be doing in the next months and years to come.
 
-If you want to join the Score community, [connect with us on Slack](https://score.dev/slack-rd)!
+If you want to join the Score community, join the [#score channel on the CNCF Slack](https://slack.cncf.io).
 
 Thanks again, and see you really soon!

content/blog/how-is-score-different-from-other-tools/index.md

@@ -54,4 +54,4 @@ The [Open Application Model (OAM)](https://oam.dev/) and Score share a similar p
 
 We’re currently working on a blog article that explores the tools differences in more detail to help you understand which one is more suitable for your use case. Watch the [Score Blog](https://score.dev/blog) for updates.
 
-We hope this was helpful and answered your questions! If you would like to comment on any of the above named items or suggest a tool you’d like us to explore in comparison to Score, let us know via our [community Slack](https://join.slack.com/t/scorecommunity/shared_invite/zt-1i2glkqkl-EnjSWSCgYUyaEGwmDYBZZQ) or create a topic in our recently launched [discussion forum](https://github.com/score-spec/spec/discussions).
+We hope this was helpful and answered your questions! If you would like to comment on any of the above named items or suggest a tool you’d like us to explore in comparison to Score, let us know in the [#score channel on the CNCF Slack](https://slack.cncf.io) or create a topic in our recently launched [discussion forum](https://github.com/score-spec/spec/discussions).

content/blog/project-melody/index.md

@@ -37,7 +37,7 @@ We REALLY value your feedback and insights. It’s what shapes how we improve an
 
 - [Complete a survey](https://docs.google.com/forms/d/e/1FAIpQLSdaik3q4NerxbTDa7lRZiGw-B5INBWURsWXvwitf5wRM-qqyw/viewform?usp=sharing)
 
-- [Send us a Slack](https://join.slack.com/t/scorecommunity/shared_invite/zt-1i2glkqkl-EnjSWSCgYUyaEGwmDYBZZQ)
+- Ping us in the [#score channel on the CNCF Slack](https://slack.cncf.io)
 
 We can’t wait to hear from you! So please join our harmony and help make Project Melody a success! 🎵🎶
 

content/blog/score-applies-to-become-a-cncf-sandbox-project/index.md

@@ -38,4 +38,4 @@ On 23rd January 2024 we joined the [TAG App Delivery's WG Platforms](https://tag
 
 You can now [watch the recording](https://www.youtube.com/watch?v=P6otOxdOKDk&t=1260s) of the meeting and [access the slides](https://docs.google.com/presentation/d/1O8m2O1WAdUQU6-wcJiwBTiO24J6PBGob3Rqc31DOZEM/edit?usp=sharing) we presented. Additionally, you can [view the list of questions](https://docs.google.com/document/d/1UXJQFFYZOXaVNQVpD2wZcd5maYWIfrMvfeM1NbqOmVA/edit?usp=sharing) that were raised.
 
-The meeting sparked several follow-up discussions and engagements. If you have any further questions or would like to discuss anything related to Score, feel free to reach out to us on the [CNCF Slack channel](https://cloud-native.slack.com/?redir=%2Fmessages%2FCHY2THYUU) or our [Slack workspace](https://join.slack.com/t/scorecommunity/shared_invite/zt-2a0x563j7-i1vZOK2Yg2o4TwCM1irIuA).
+The meeting sparked several follow-up discussions and engagements. If you have any further questions or would like to discuss anything related to Score, feel free to reach out to us in the [#score channel on the CNCF Slack](https://slack.cncf.io).

content/blog/score-at-kubecon-eu-in-paris/index.md

@@ -74,4 +74,4 @@ If you're attending KubeCon this year, don't hesitate to stop by our booth D35 i
 
 À bientôt à KubeCon Paris!
 
-PS: If you aren’t attending KubeCon this year, we’ll be available in our [Slack community](https://join.slack.com/t/scorecommunity/shared_invite/zt-2a0x563j7-i1vZOK2Yg2o4TwCM1irIuA) to answer any questions. We are always open to chatting during our office hours (every Thursday, 3-4 pm CET).
+PS: If you aren’t attending KubeCon this year, we’ll be available in the [#score channel on the CNCF Slack](https://slack.cncf.io) to answer any questions. We are always open to chatting during our [monthly community meeting](https://github.com/score-spec/spec?tab=readme-ov-file#-get-in-touch).

content/blog/score-faq/index.md

@@ -7,7 +7,7 @@ image: 66607b6971de0ff6bd8063eb_ScoreFaq-p-800.png
 author: susa-tunker
 ---
 
-Our community is growing and so is the amount of questions we receive! A huge thank you to everyone who dropped questions in our [Slack](https://join.slack.com/t/scorecommunity/shared_invite/zt-1i2glkqkl-EnjSWSCgYUyaEGwmDYBZZQ), contributed to our [GitHub discussions](https://github.com/score-spec/spec/discussions) and raised [GitHub issues](https://github.com/score-spec/spec/issues) in the last few months. We’re excited to keep the discussion going and encourage everyone to keep asking questions and sharing your ideas with us. 🚀 In this article, we’re tackling the biggest questions raised so far. Let’s dive in.
+Our community is growing and so is the amount of questions we receive! A huge thank you to everyone who dropped questions in the [#score channel on the CNCF Slack](https://slack.cncf.io), contributed to our [GitHub discussions](https://github.com/score-spec/spec/discussions) and raised [GitHub issues](https://github.com/score-spec/spec/issues) in the last few months. We’re excited to keep the discussion going and encourage everyone to keep asking questions and sharing your ideas with us. 🚀 In this article, we’re tackling the biggest questions raised so far. Let’s dive in.
 
 ## What is Score?
 
@@ -64,4 +64,4 @@ From our experience, this is often the case in medium-sized and larger developme
 
 One of the main pain points that Score solves is configuration mismatch between environments that run on different platforms. For example: You might run Docker Compose locally while deploying to a Kubernetes based development environment. A Score  Implementation CLI allows you to translate your Score file into all kinds of configuration formats (Docker Compose, Helm, Kustomize, ECS etc.) and thereby ensure consistent configuration. In a single platform set up this translation element won’t come into effect. Whether adopting Score makes sense for you anyway depends on your teams set up. If you’re running into config bottlenecks and are wanting to abstract away the complexity of platforms such as Kubernetes from developers, Score might be worth investigating - at the very least as a source of inspiration for your team.
 
-In this article we looked at a set of questions related to Score, its capabilities, use cases and adoption. Is there anything we missed? Do you have a follow up question? Ping us anytime on [Slack](https://join.slack.com/t/scorecommunity/shared_invite/zt-1i2glkqkl-EnjSWSCgYUyaEGwmDYBZZQ) or [GitHub](https://github.com/score-spec/spec/discussions) and we’ll get back to you. 
+In this article we looked at a set of questions related to Score, its capabilities, use cases and adoption. Is there anything we missed? Do you have a follow up question? Ping us anytime in the [#score channel on the CNCF Slack](https://slack.cncf.io) or [GitHub](https://github.com/score-spec/spec/discussions) and we’ll get back to you. 

content/blog/score-is-trending-on-github/index.md

@@ -19,7 +19,7 @@ Quite an exciting way to end 2022!
 
 What’s coming next? We are expanding our opportunities to meet contributors at events, with quite a busy schedule in 2023 and also pushing further in our community effort to share the [roadmap](https://github.com/score-spec/spec/blob/main/roadmap.md) and vision with everyone who would like to participate in the Score journey.
 
-Thank you for your continuous support, let’s chat more on [Slack]((https://join.slack.com/t/scorecommunity/shared_invite/zt-1i2glkqkl-EnjSWSCgYUyaEGwmDYBZZQ)) or on the [discussion](https://github.com/score-spec/spec/discussions) tab on GitHub!
+Thank you for your continuous support, let’s chat more in the [#score channel on the CNCF Slack](https://slack.cncf.io) or on the [discussion](https://github.com/score-spec/spec/discussions) tab on GitHub!
 
 > ## The team behind Score
 > The idea for Score organically formed from looking at hundreds of delivery setups, across engineering orgs of all sizes (from startups to Fortune 100). We have all been involved in platform engineering and developer tooling for the past decade, in one way or another.Some of us built Internal Developer Platforms at the likes of Google, Apple or IBM, some come from the IaC side of things and played leading roles at companies like Hashicorp. <br><br>

content/blog/score-platform-engineering-meetup/index.md

@@ -13,6 +13,7 @@ On December 13, at 7 PM CET, two Score's main contributors and maintainers, Susa
 
 The conversation will last around 30 minutes and there will be space for community questions and feedback. 
 
-Thank you to the Platform Engineering community for hosting this discussion. Please, register at [this link](https://www.linkedin.com/events/oneyamltorulethemall-andprevent7000492721220030464/about/) to participate in the discussion on Zoom, the recording will be shared a day later both on [GitHub Discussions](https://github.com/score-spec/spec/discussions) and on the community Slack channel.
+Thank you to the Platform Engineering community for hosting this discussion. Please, register at [this link](https://www.linkedin.com/events/oneyamltorulethemall-andprevent7000492721220030464/about/) to participate in the discussion on Zoom, the recording will be shared a day later both on [GitHub Discussions](https://github.com/score-spec/spec/discussions) and in the [#score channel on the CNCF Slack](https://slack.cncf.io).
+
+Community active participation is strongly encouraged! See you there!
 
-Community active participation is strongly encouraged! See you there!

content/blog/thank-you-250-times/index.md

@@ -11,6 +11,6 @@ Folks, we are extremely happy to announce that as of today, one week after launc
 
 First, we would like to extend our gratitude to the fantastic open-source community and developers who have been of great help in giving us feedback early on and sharing the repositories with their peers. 
 
-Our [Slack channel](https://score.dev/slack-rd) is growing and we can’t wait now for our first community meeting: you can find all the relevant information in the #general channel!
+The [#score channel on the CNCF Slack](https://slack.cncf.io) is growing and we can’t wait for our first community meeting: you can find all the relevant information in the #score channel!
 
 To check what’s ahead of us, consult our [roadmap](https://github.com/score-spec/spec/blob/main/roadmap.md) and join our Slack channel, and don’t forget: comments, questions and any sort of feedback is greatly appreciated and can be sent directly to [team@score.dev](mailto:team@score.dev).

content/blog/whats-next-for-score/index.md

@@ -32,7 +32,7 @@ We discussed Score and our vision for workload-centric development in front of a
 * December 14: Score at [Cloud Native Live](https://www.youtube.com/watch?v=2EJ3irXaXYA&t=1093s)
 * December 21: We [trended on GitHub](https://twitter.com/_sujaya/status/1605568500571021312?s=20&t=SQb6ZjGTpWF0_9xBH7uNWA) for the first time
 
-If you’re interested in joining our upcoming events, keep an eye out on our [blog](https://score.dev/blog) and [community Slack](https://app.slack.com/client/T047EJ0JB3K) for updates.
+If you’re interested in joining our upcoming events, keep an eye out on our [blog](https://score.dev/blog) and the [#score channel on the CNCF Slack](https://slack.cncf.io) for updates.
 
 ### Community discussions
 
@@ -42,7 +42,7 @@ The future of Score depends on community input. We were excited to engage in fir
 * [What is the difference between Score and OAM (Kubevela)?](https://github.com/score-spec/spec/issues/23)
 * [How is Score different from other tools?](https://score.dev/blog/how-is-score-different-from-other-tools)
 
-You’ll find further discussion threads in our [community Slack](https://app.slack.com/client/T047EJ0JB3K). We’re looking forward to keeping the conversation going in 2023.
+You’ll find further discussion threads in the [#score channel on the CNCF Slack](https://slack.cncf.io). We’re looking forward to keeping the conversation going in 2023.
 
 ### Feature requests
 
@@ -69,7 +69,7 @@ Curious to explore one of these topics in more detail but aren’t sure where or
 
 All contributions are welcome. Playing around with the tool and providing feedback, engaging in discussions or simply sharing your questions with us is a huge help. If you’re interested in testing or adopting Score with your team we’re open to supporting you with the onboarding and integration of the tool.
 
-We’re excited to move things forward together with you and the rest of the community in 2023. It’ll be great to see where we’ll stand at the end of this quarter and year. If there’s something you’d like to discuss, drop in during our weekly office hours on Slack every Monday between 4 and 5pm CET. See you there!
+We’re excited to move things forward together with you and the rest of the community in 2023. It’ll be great to see where we’ll stand at the end of this quarter and year. If there’s something you’d like to discuss, drop in during our [monthly community meetings](https://github.com/score-spec/spec?tab=readme-ov-file#-get-in-touch). See you there!
 
 Happy 2023!
 

data/site.yaml

@@ -12,6 +12,6 @@ footer:
     title: Join the community
     text: Share best practices around config mgmt and learn how others integrate Score in their delivery workflows.
     button:
-      text: Join Score on the CNCF Slack
+      text: Join \#score on the CNCF Slack
       url: https://slack.cncf.io
       icon: svg/slack.svg

data/socials.yaml

@@ -3,7 +3,7 @@
   text: Share best practices around config mgmt and learn how others integrate Score in their delivery workflows.
   link:
     url: https://slack.cncf.io
-    text: Join *#score* on the CNCF Slack
+    text: Join \#score on the CNCF Slack
 - name: Twitter
   icon: /images/socials/twitter.png
   text: Follow us on Twitter for roadmap updates and live discussions with contributors and community members.