docs: fix links to Slack

sitespeedio · Dec 20, 2023 · 067d6bf · 067d6bf
1 parent 8cc699d
commit 067d6bf
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/docs/_includes/footer.html b/docs/_includes/footer.html
@@ -29,7 +29,7 @@ <h3>Connect</h3>
 			<ul>
 				<li><a rel="me" href="https://fosstodon.org/@sitespeedio">Mastodon</a></li>
 				<li><a href="https://github.com/sitespeedio">GitHub</a></li>
-				<li><a href="(https://join.slack.com/t/sitespeedio/shared_invite/zt-296jzr7qs-d6DId2KpEnMPJSQ8_R~WFw">Slack</a></li>
+				<li><a href="https://join.slack.com/t/sitespeedio/shared_invite/zt-296jzr7qs-d6DId2KpEnMPJSQ8_R~WFw">Slack</a></li>
 		</div>
 		<div class="col-1-5">
 			<h3>sitespeed.io</h3>

diff --git a/docs/documentation/sitespeed.io/developers/index.md b/docs/documentation/sitespeed.io/developers/index.md
@@ -193,7 +193,7 @@ To be able to release a new version you new to have access to our Docker account
 
 To do a release you need to first install np (a better *npm publish*): <code>npm install --global np</code>
 
-Before you do a release, remember to let your latest code change run a couple of hours on our test server before you push the release (the latest code is automatically deployed on the test server). You will find errors from the test server on the [#alert channel on Slack](https://sitespeedio.herokuapp.com/).
+Before you do a release, remember to let your latest code change run a couple of hours on our test server before you push the release (the latest code is automatically deployed on the test server). You will find errors from the test server on the [#alert channel on Slack](https://join.slack.com/t/sitespeedio/shared_invite/zt-296jzr7qs-d6DId2KpEnMPJSQ8_R~WFw).
 
 Do the release:
 

diff --git a/docs/support/index.md b/docs/support/index.md
@@ -16,7 +16,7 @@ If you need help or support then:
 2. We try to document all the things, so read the [documentation](/documentation/). 
 3. We have a lot of documentation. Sometimes its hard to find the thing you need, try the [search](/search/).
 4. If you don't find what you need, [search GitHub open/closed issues](https://github.com/search?q=org+sitespeedio&type=Issues). The project been alive for many years and you can  get a lot of help in closed GitHub issues.
-5. If you still haven't found what you need, [join our Slack channel](https://sitespeedio.herokuapp.com/) and tell us about your problem.
+5. If you still haven't found what you need, [join our Slack channel](https://join.slack.com/t/sitespeedio/shared_invite/zt-296jzr7qs-d6DId2KpEnMPJSQ8_R~WFw) and tell us about your problem.
 
 
 If you have a bug, please read [How to do a reproducible bug report](https://www.sitespeed.io/documentation/sitespeed.io/bug-report/) and file your bug under the project you think match. If you don't know where to report the bug, [create the issue on the main sitespeed.io repo](https://github.com/sitespeedio/sitespeed.io/issues/new) and we will move the issue to the right place!