Stage 4 migrate posts, more link fixes

valencik · valencik · commit 3b629341b1eb · 2026-02-16T12:30:04.000-05:00
diff --git a/src/blog/call-for-code-of-conduct-committee-members.md b/src/blog/call-for-code-of-conduct-committee-members.md
@@ -34,7 +34,7 @@ Accepted candidacies will be public, but we will not disclose the identity of an
 
 The call will be open for three weeks, closing on September 14th 2024.
 
-[new-coc]: https://typelevel.org/blog/2024/03/11/code-of-conduct.html
+[new-coc]: code-of-conduct.md
 [enforcement-policy]: https://github.com/typelevel/governance/blob/main/ENFORCEMENT-POLICY.md
 [otter-tech-training]: https://otter.technology/code-of-conduct-training/
 [steering-committee]: https://github.com/typelevel/governance/blob/main/STEERING-COMMITTEE.md
diff --git a/src/blog/call-for-steering-committee-members.md b/src/blog/call-for-steering-committee-members.md
@@ -61,6 +61,6 @@ welcome two to six new members this cycle, and consider more as
 ambitions and capacity warrant.
 
 [committee]: https://github.com/typelevel/governance/blob/main/STEERING-COMMITTEE.md
-[governing documents]: https://typelevel.org/blog/2022/01/19/governing-documents.html
+[governing documents]: governing-documents.md
 [governance discussions]: https://github.com/typelevel/governance/issues
 [volunteeer@typelevel.org]: mailto:volunteer@typelevel.org
diff --git a/src/blog/edsls-part-2.md b/src/blog/edsls-part-2.md
@@ -112,7 +112,7 @@ import cats.Monad
 import cats.implicits._
 
 trait SetLang[F[_]] {
-  // See: https://typelevel.org/blog/2016/09/30/subtype-typeclasses.html
+  // See: subtype-typeclasses.md
   // for why the `Monad` instance is defined as a member as opposed to inherited
   def monad: Monad[F]
 
diff --git a/src/blog/evolving-typelevel.md b/src/blog/evolving-typelevel.md
@@ -7,7 +7,7 @@
 # Evolving Typelevel
 
 In recent years, Typelevel has existed in a somewhat grey area legally. We have long managed a good deal of intellectual
-property (the Organization Libraries) and raised funds. In 2022, [we adopted a Charter](/blog/2022/01/19/governing-documents.html) establishing our governance.
+property (the Organization Libraries) and raised funds. In 2022, [we adopted a Charter](governing-documents.md) establishing our governance.
 However, we have not had a well-defined legal status.
 
 We have decided it is time to become a legally-recognized organization. To that end, we have formed the Typelevel
diff --git a/src/blog/fibers-fast-mkay.md b/src/blog/fibers-fast-mkay.md
@@ -51,7 +51,7 @@ The most direct and naive way to approach this is to allocate one thread per con
 ### Unbounded Threads
 
 <!-- loads of threads diagram -->
-![]({{ site.url }}/img/media/fibers/many-threads.png)
+![](/img/media/fibers/many-threads.png)
 
 Implementation-wise, this is very easy to reason about. Your code will all take on a highly imperative structure, with *A* followed by *B* followed by *C*, etc, and it will behave entirely reasonably at small scales! Unfortunately, the problem here is that threads are not particularly cheap. The reasons for this are relatively complex, but they manifest in two places: the OS kernel scheduler, and the JVM itself. 
 
diff --git a/src/blog/gsoc-2024.md b/src/blog/gsoc-2024.md
@@ -26,7 +26,7 @@ Lastly, we were surprised by the breadth of the response we got to our announcem
 
 [Scala Center]: https://scala.epfl.ch/
 [GSoC]: https://summerofcode.withgoogle.com/
-[ideas]: /gsoc/ideas
+[ideas]: /gsoc/ideas.md
 
 [apply]: https://summerofcode.withgoogle.com/get-started
 [Discord]: https://discord.gg/hAKabfGjUw
diff --git a/src/blog/gsoc-2025.md b/src/blog/gsoc-2025.md
@@ -25,8 +25,8 @@ Our program culminated in a [virtual meetup][meetup] where each of them gave a l
 Finally, we are making a broad call for any and all new contributors. Even if you are not eligible to participate in GSoC, you are *always* welcome to join the Typelevel community and contribute to our projects!
 
 [GSoC]: https://summerofcode.withgoogle.com/
-[feral-blog]: /blog/2024/12/22/gsoc24-going-feral-on-the-cloud.html
-[ideas]: /gsoc/ideas
+[feral-blog]: gsoc24-going-feral-on-the-cloud.md
+[ideas]: /gsoc/ideas.md
 
 [apply]: https://summerofcode.withgoogle.com/get-started
 [Discord]: https://discord.gg/hAKabfGjUw
diff --git a/src/blog/http4s-error-handling-mtl-2.md b/src/blog/http4s-error-handling-mtl-2.md
@@ -6,7 +6,7 @@
 
 # Error handling in Http4s with classy optics – Part 2
 
-This is a continuation of my [previous blog post](https://typelevel.org/blog/2018/08/25/http4s-error-handling-mtl.html). Make sure you have read that one before continuing here.
+This is a continuation of my [previous blog post](http4s-error-handling-mtl.md). Make sure you have read that one before continuing here.
 
 I recently gave a 20 minutes talk on `classy optics` at the unconference of [Scale by the Bay](http://scale.bythebay.io/) where I also talked about this error handling technique and on my way back home I was still thinking of different ways of doing this. So, after some exploratory work, I came up with a few different alternatives.
 
diff --git a/src/blog/http4s-error-handling-mtl.md b/src/blog/http4s-error-handling-mtl.md
@@ -306,4 +306,4 @@ I hope you have enjoyed this post and please do let me know if you know of bette
 
 And last but not least I would like to thank all the friendly folks I hang out with in the `cats-effect`, `cats`, `fs2` and `http4s` Gitter channels for all the time and effort they put (*for free*) into making this community an amazing space.
 
-**UPDATE:** See the new article [Error handling in Http4s with classy optics – Part 2](https://typelevel.org/blog/2018/11/28/http4s-error-handling-mtl-2.html).
+**UPDATE:** See the new article [Error handling in Http4s with classy optics – Part 2](http4s-error-handling-mtl-2.md).
diff --git a/src/blog/intro-to-mtl.md b/src/blog/intro-to-mtl.md
@@ -192,7 +192,7 @@ Exactly like `ReaderT`, it also includes another type parameter `E`, that repres
 
 If you're wondering why `ApplicativeAsk` has an `Applicative` field instead of just extending from `Applicative`, that is to avoid implicit ambiguities that arise from having multiple subclasses of a given type (here `Applicative`) in scope implicitly.
 So in this case we favor composition over inheritance as otherwise, we could not e.g. use `Monad` together with `ApplicativeAsk`.
-You can read more about this issue in this excellent [blog post by Adelbert Chang](https://typelevel.org/blog/2016/09/30/subtype-typeclasses.html).
+You can read more about this issue in this excellent [blog post by Adelbert Chang](subtype-typeclasses.md).
 
 ### Effect type classes
 
diff --git a/src/blog/minicheck.md b/src/blog/minicheck.md
@@ -7,7 +7,7 @@
 # Let's build ourselves a small ScalaCheck
 
 _[ScalaCheck](http://scalacheck.org/) is a well-known property-based testing library, based on ideas from Haskell's [QuickCheck](https://hackage.haskell.org/package/QuickCheck).
-It is also a [Typelevel project](/projects).
+It is also a [Typelevel project](/projects/README.md).
 In this post, I'd like to show some of the underlying mechanisms, stripped down to the bare minimum._
 
 Testing with properties is well-understood in academia and widely used in parts of the industry – namely the parts which embrace functional programming.
diff --git a/src/blog/new-code-of-conduct-committee-members.md b/src/blog/new-code-of-conduct-committee-members.md
@@ -6,7 +6,7 @@
 
 # Code of Conduct Committee
 
-A few months back the Typelevel Steering Committee put out [a call for new members](https://typelevel.org/blog/2024/08/24/call-for-code-of-conduct-committee-members.html) to join the Typelevel Code of Conduct Committee. Thank you very much to all who applied, it's lovely to see folks interested in keeping our community safe.
+A few months back the Typelevel Steering Committee put out [a call for new members](call-for-code-of-conduct-committee-members.md) to join the Typelevel Code of Conduct Committee. Thank you very much to all who applied, it's lovely to see folks interested in keeping our community safe.
 
 Since that time, the Typelevel Steering Committee voted in three new members to the Code of Conduct Committee! The committee now has five members total.
 
diff --git a/src/blog/on-recent-events.md b/src/blog/on-recent-events.md
@@ -12,7 +12,7 @@ We stand with those who feel excluded by the notion of politics being somehow op
 
 The Scala Center, which has a long and celebrated history of success in education and technical improvement to the tooling we use daily, has repeatedly been expected to take on a community management role beyond its chartered goals, for which it is ill-equipped and underfunded. We acknowledge the challenges they face and we support the Scala Community Management and Governance strategy under consideration as a promising way forward.
 
-Typelevel has functioned with a not-very-formal governance structure of volunteers for some time. This group is known as the [Typelevel Steering Committee](/steering.html). In the coming weeks we will formalize how leadership is selected and what the roles and responsibilities are.
+Typelevel has functioned with a not-very-formal governance structure of volunteers for some time. This group is known as the [Typelevel Steering Committee](/steering.md). In the coming weeks we will formalize how leadership is selected and what the roles and responsibilities are.
 
 The Typelevel Steering Committee:
 * Ross A. Baker
diff --git a/src/blog/optimizing-tagless-final-2.md b/src/blog/optimizing-tagless-final-2.md
@@ -6,7 +6,7 @@
 
 # Optimizing Tagless Final – Part 2 – Monadic programs
 
-In our previous post on optimizing tagless final programs we learned how we could use the [sphynx library](https://github.com/LukaJCB/sphynx) to derive some optimization schemes for your tagless final code. In case you missed it and want to read up on it, you can find it [right here](https://typelevel.org/blog/2017/12/27/optimizing-final-tagless.html) or you can watch my presentation on the topic [here](https://www.youtube.com/watch?v=E9iRYNuTIYA), but you should be able to follow this blog post without going through it all in detail.
+In our previous post on optimizing tagless final programs we learned how we could use the [sphynx library](https://github.com/LukaJCB/sphynx) to derive some optimization schemes for your tagless final code. In case you missed it and want to read up on it, you can find it [right here](optimizing-final-tagless.md) or you can watch my presentation on the topic [here](https://www.youtube.com/watch?v=E9iRYNuTIYA), but you should be able to follow this blog post without going through it all in detail.
 
 ## Optimizing monadic programs
 
diff --git a/src/blog/scala-coc.md b/src/blog/scala-coc.md
@@ -10,7 +10,7 @@ A couple of days ago, the new [Scala Code of Conduct](https://contributors.scala
 It applies to all official Scala channels, including mailing lists, Gitter channels and GitHub repositories.
 We would like to take this opportunity to endorse this new Code of Conduct.
 From our perspective, it does a good job of listing encouraged behaviour, instead of just banning harassment: It reflects the goal of _actively_ creating a welcoming community.
-Also, we consider it to be a decent substitute of our own [Code of Conduct](/conduct.html).
+Also, we consider it to be a decent substitute of our own [Code of Conduct](/code-of-conduct/README.md).
 That means that Typelevel project maintainers are free to switch to the Scala Code of Conduct if they wish.
 
 For some more background, please see the [discussion on GitHub](https://github.com/typelevel/general/issues/51).
diff --git a/src/blog/summit_assistance.md b/src/blog/summit_assistance.md
@@ -40,7 +40,7 @@ We will assign a mentor to each participating speaker. Your mentor will be avail
 
 If you are planning on attending or speaking in Philadelphia or Oslo, and you would like to apply for any of the services above, please please fill out the application form linked at the top of the page.
 
-[code-of-conduct]: /conduct.html
-[summits]: /blog/2015/12/11/announcement_summit.html
+[code-of-conduct]: /code-of-conduct/README.md
+[summits]: announcement_summit.md
 [philadelphia]: /event/2016-03-summit-philadelphia/
 [oslo]: /event/2016-05-summit-oslo/
diff --git a/src/blog/support-typelevel-thanks-to-triplequote-hydra.md b/src/blog/support-typelevel-thanks-to-triplequote-hydra.md
@@ -8,7 +8,7 @@
 
 Hello Community!
 
-As you all know, back in April we announced the [Typelevel Sustainability Program](https://typelevel.org/blog/2019/04/24/typelevel-sustainability-program-announcement.html) and we have been delighted by the overwhelming support we received both from companies and individuals: thank you all!
+As you all know, back in April we announced the [Typelevel Sustainability Program](typelevel-sustainability-program-announcement.md) and we have been delighted by the overwhelming support we received both from companies and individuals: thank you all!
 
 In just a little bit more than one month we reached 10% of the fundraising goal we set to $150,000. While this is an excellent start, to successfully support the long term sustainability of our ecosystem, we need you to keep advocating for us.
 
diff --git a/src/blog/tagless-final-streaming.md b/src/blog/tagless-final-streaming.md
@@ -6,7 +6,7 @@
 
 # Tagless Final Algebras and Streaming
 
-There have been a couple of really [nice blog posts](https://typelevel.org/blog/2017/12/27/optimizing-final-tagless.html) about `Tagless Final` and some related topics. However, I have faced some design problems when writing some algebras and haven't seen anybody talking about. So please let me introduce this problem to you.
+There have been a couple of really [nice blog posts](optimizing-final-tagless.md) about `Tagless Final` and some related topics. However, I have faced some design problems when writing some algebras and haven't seen anybody talking about. So please let me introduce this problem to you.
 
 ### Algebra definition
 
diff --git a/src/blog/typelevel-sustainability-program-announcement.md b/src/blog/typelevel-sustainability-program-announcement.md
@@ -10,7 +10,7 @@ We are excited to announce the Typelevel sustainability program.
 The ultimate goal for this program is to provide ways for the user community to ensure the long-term sustainability of the development and maintenance of some Typelevel libraries.
 Currently, these libraries are maintained in their contributors' spare time. This arrangement has worked so far but we want to firmly secure their long term sustainability with an institution dedicated to supporting the maintenance of these mission critical libraries.
 
-Based on our [Cats ecosystem community survey](https://typelevel.org/blog/2019/01/30/cats-ecosystem-community-survey-results.html), roughly 70% of the users will gain more confidence
+Based on our [Cats ecosystem community survey](cats-ecosystem-community-survey-results.md), roughly 70% of the users will gain more confidence
 in the future of the ecosystem if there are compensated maintainers. We believe that our pure FP
 Scala ecosystem should have an institution supporting it, somewhat like the Scala Center
 supporting the language, and Lightbend supporting language as well as ecosystem libs. 
diff --git a/src/blog/typelevel-switches-to-scala-code-of-conduct.md b/src/blog/typelevel-switches-to-scala-code-of-conduct.md
@@ -14,7 +14,7 @@ new projects that join Typelevel to adopt the new code.
 The Scala Code of Conduct was developed by the Scala Center with input from
 Typelevel and Lightbend, and improves on Typelevel's original in several ways.
 It can be thought of as the "Typelevel code of conduct 2.0". We [endorsed it
-from the outset](https://typelevel.org/blog/2016/12/17/scala-coc.html) and have
+from the outset](scala-coc.md) and have
 decided that now the time is right to simplify things and move to the new code
 wholesale.
 
@@ -28,4 +28,4 @@ Days amongst many others. And now Typelevel and the Typelevel Summits.
 
 We'd love you to join us.
 
-[scoc]: /code-of-conduct.html
+[scoc]: /code-of-conduct/README.md
diff --git a/src/blog/typelevel_toolkit.md b/src/blog/typelevel_toolkit.md
@@ -6,7 +6,7 @@
 
 # Typelevel Toolkit
 
-Getting started in the wondrous world of functional programming using [Typelevel libraries](https://typelevel.org/projects) can be daunting. Before you can even write your first pure "Hello, World!" you'll need to install a Java runtime, editor tooling and build tools. Then you'll need to setup some project using [sbt](https://www.scala-sbt.org/) or [mill](https://github.com/com-lihaoyi/mill). As an added consequence, after all the setup, the idea of using these battle-tested libraries for small scripts will seem like a chore. This is where [Typelevel Toolkit](https://typelevel.org/toolkit/) comes in. It provides an easy start for beginning and experienced developers with Scala and functional programming.
+Getting started in the wondrous world of functional programming using [Typelevel libraries](https://typelevel.org/projects/README.md) can be daunting. Before you can even write your first pure "Hello, World!" you'll need to install a Java runtime, editor tooling and build tools. Then you'll need to setup some project using [sbt](https://www.scala-sbt.org/) or [mill](https://github.com/com-lihaoyi/mill). As an added consequence, after all the setup, the idea of using these battle-tested libraries for small scripts will seem like a chore. This is where [Typelevel Toolkit](https://typelevel.org/toolkit/) comes in. It provides an easy start for beginning and experienced developers with Scala and functional programming.
 
 # scala-cli to the rescue
 
diff --git a/src/blog/welcoming-new-steering-committee-members.md b/src/blog/welcoming-new-steering-committee-members.md
@@ -53,7 +53,7 @@ These new members are excited to continue Typelevel's efforts to foster an inclu
 [jasna]: https://github.com/JasnaMRB
 [jetbrains]: https://jetbrains.co
 [justin]: https://github.com/jducoeur
-[last-post]: https://typelevel.org/blog/2022/04/01/call-for-steering-committee-members.html
+[last-post]: call-for-steering-committee-members.md
 [querki]: https://querki.net/
 [sam]: https://github.com/samspills
 [shopify]: https://www.shopify.com

Original file line number	Diff line number	Diff line change
`@@ -306,4 +306,4 @@ I hope you have enjoyed this post and please do let me know if you know of bette`
`306`	`306`
`307`	`307`	And last but not least I would like to thank all the friendly folks I hang out with in the `cats-effect`, `cats`, `fs2` and `http4s` Gitter channels for all the time and effort they put (for free) into making this community an amazing space.
`308`	`308`
`309`		`-UPDATE: See the new article [Error handling in Http4s with classy optics – Part 2](https://typelevel.org/blog/2018/11/28/http4s-error-handling-mtl-2.html).`
	`309`	`+UPDATE: See the new article [Error handling in Http4s with classy optics – Part 2](http4s-error-handling-mtl-2.md).`