scala · SethTisue · Sep 13, 2021 · Sep 13, 2021 · Sep 13, 2021 · Sep 13, 2021
diff --git a/_events/2013-07-17-scalapeno.md b/_events/2013-07-17-scalapeno.md
@@ -6,5 +6,5 @@ location: Tel Aviv, Israel
 description: Scalapeño is a full-day conference for software developers focused on the Scala programming language.
 start: 17 July 2013
 end: 17 July 2013
-link-out: http://www.2013.scalapeno.org.il/
+link-out: https://www.scalapeno2018.com/
 ---
diff --git a/_events/2014-09-22-scalapeno.md b/_events/2014-09-22-scalapeno.md
@@ -6,5 +6,5 @@ location: Ramat Gan, Israel
 description: The second annual Israeli Scala conference
 start: 22 September 2014
 end: 22 September 2014
-link-out: http://www.2014.scalapeno.org.il/
+link-out: https://www.scalapeno2018.com/
 ---
diff --git a/_events/2016-02-11-scalasphere.md b/_events/2016-02-11-scalasphere.md
@@ -6,5 +6,5 @@ location: Kraków
 description: "Let’s immerse ourselves into Scala DevTools"
 start: 11 February 2016
 end: 12 February 2016
-link-out: https://scalasphere.org/edition2016/
+link-out: https://sphere.it/event/scala-devtools-2016/
 ---
diff --git a/_events/2016-05-03-scalapeno.md b/_events/2016-05-03-scalapeno.md
@@ -6,5 +6,5 @@ location: Ramat Gan, Israel
 description: Scalapeño is an annual conference for software engineers focused on the Scala programming language.
 start: 3 May 2016
 end: 3 May 2016
-link-out: https://www.scalapeno.org.il/
+link-out: https://www.scalapeno2018.com/
 ---
diff --git a/_events/2017-03-02-scalasphere.md b/_events/2017-03-02-scalasphere.md
@@ -6,5 +6,5 @@ location: Kraków, Poland
 description: "Let’s immerse ourselves into Scala DevTools"
 start: 2 March 2017
 end: 3 March 2017
-link-out: https://scalasphere.org/edition2017/
+link-out: https://sphere.it/event/scala-devtools-2017/
 ---
diff --git a/_events/2018-04-15-scalasphere.md b/_events/2018-04-15-scalasphere.md
@@ -6,5 +6,5 @@ location: Kraków, Poland
 description: "Let’s immerse ourselves into Scala Dev Tools"
 start: 15 April 2018
 end: 17 April 2018
-link-out: https://2018.scala.sphere.it/
+link-out: https://sphere.it/event/scala-devtools-2018/
 ---
diff --git a/_events/2019-10-06-sphereit.md b/_events/2019-10-06-sphereit.md
@@ -6,5 +6,5 @@ location: Kraków, Poland
 description: "one conference, five spheres covering the emerging potential of software technology"
 start: 6 October 2019
 end: 9 October 2019
-link-out: https://archive.sphere.it/previous-editions/#2019
+link-out: https://sphere.it/event/scala-devtools-2019/
 ---
diff --git a/_posts/2013-03-20-gsoc13.md b/_posts/2013-03-20-gsoc13.md
@@ -39,7 +39,7 @@ The to goal of this project is to extend the desugaring of for-comprehensions in
 
 ### Alternative / social Scala documentation
 
-This project has two  parts. First you will work on generating alternative api documentation  formats for Scaladoc. You will need to hook into the scaladoc part of  the scala compiler, to access and work with Scaladoc's code model. We  have a small prototype you can use as a starting point. You should then  generate documentation in (non-framed, non-js) single/multi-page HTML,  PDF, CHM formats. The result should make sensible use of the scaladoc  @-commands and you should think about a good way to present apis  designed as in cake patterns. HTML-Formats should support external  linking to methods. You can use a documentation generator such as Sphinx  to help generating different formats. The second part of this project  concerns collaboration. You will need to come up with smart and simple  ideas and an implementation how to make Scala api documentation more  social, favorably in a way that can be shared between the different HTML  doc formats. It can be as simple as adding GitHub Links and Disqus or  more involved. Make sure to also review the work  that has been done on [Colladoc](https://colladoc.github.com/). We are very open for your own new or alternative ideas  regarding any aspect of this project.  Good knowledge of modern, accessible HTML/CSS and possibly JS will be  helpful. We want to work with you in an agile, ticket-based development  style with frequent communication and coordination.
+This project has two  parts. First you will work on generating alternative api documentation  formats for Scaladoc. You will need to hook into the scaladoc part of  the scala compiler, to access and work with Scaladoc's code model. We  have a small prototype you can use as a starting point. You should then  generate documentation in (non-framed, non-js) single/multi-page HTML,  PDF, CHM formats. The result should make sensible use of the scaladoc  @-commands and you should think about a good way to present apis  designed as in cake patterns. HTML-Formats should support external  linking to methods. You can use a documentation generator such as Sphinx  to help generating different formats. The second part of this project  concerns collaboration. You will need to come up with smart and simple  ideas and an implementation how to make Scala api documentation more  social, favorably in a way that can be shared between the different HTML  doc formats. It can be as simple as adding GitHub Links and Disqus or  more involved. Make sure to also review the work  that has been done on [Colladoc](https://colladoc.github.io/). We are very open for your own new or alternative ideas  regarding any aspect of this project.  Good knowledge of modern, accessible HTML/CSS and possibly JS will be  helpful. We want to work with you in an agile, ticket-based development  style with frequent communication and coordination.
 
 * * *
 
@@ -127,7 +127,7 @@ Skills required for this project are:
 
 \[2\] Lightweight Polymorphic Effects - [https://infoscience.epfl.ch/record/175240](https://infoscience.epfl.ch/record/175240)
 
-\[3\] Lightweight Modular Staging - [https://scala-lms.github.com/](https://scala-lms.github.com/)
+\[3\] Lightweight Modular Staging - [https://scala-lms.github.io/](https://scala-lms.github.io/)
 
 
 * * *

diff --git a/blog/_posts/2020-11-19-scala-3-forward-compat.md b/blog/_posts/2020-11-19-scala-3-forward-compat.md
@@ -318,7 +318,7 @@ to continue using implicit classes to encode extension methods.
 
 On the other hand, some features of Scala 3 are not mappable to features in Scala 2.13,
 and will cause a compile-time error when using them. A longer list can be seen in the
-migration guide, describing [how Scala 2 reacts to different Scala 3 features](https://scalacenter.github.io/scala-3-migration-guide/docs/compatibility.html#the-scala-2-tasty-reader).
+migration guide, describing [how Scala 2 reacts to different Scala 3 features](https://docs.scala-lang.org/scala3/guides/migration/compatibility-classpath.html#the-scala-213-tasty-reader).
 
 For unsupported features, a best effort is made
 to report errors at the use-site that is problematic. For example,

diff --git a/community/index.md b/community/index.md
@@ -154,7 +154,7 @@ items and opinions.  Ask your Scala friends who they follow on Twitter
 ## Community-Powered Learning Resources
 
 * [Scala Exercises](http://scala-exercises.47deg.com/)
-* [Scala School](https://twitter.github.com/scala_school/)
+* [Scala School](https://twitter.github.io/scala_school/)
 * [Scala Puzzlers](https://scalapuzzlers.com/)
 * [Scala Cookbook](http://www.scalacookbook.com/)
 * [Interactive Tour](https://scalatutorials.com/tour)