infonl · morrieinmaas · Aug 4, 2026 · Jul 31, 2026 · Jul 31, 2026 · Jul 31, 2026
diff --git a/radar/2020-09-01/azure-devops.md b/radar/2020-09-01/azure-devops.md
diff --git a/radar/2020-09-01/bitbucket-cloud-and-pipelines.md b/radar/2020-09-01/bitbucket-cloud-and-pipelines.md
diff --git a/radar/2020-09-01/cloud-native-platforms.md b/radar/2020-09-01/cloud-native-platforms.md
diff --git a/radar/2020-09-01/data-science-and-machine-learning.md b/radar/2020-09-01/data-science-and-machine-learning.md
diff --git a/radar/2020-09-01/data-streaming.md b/radar/2020-09-01/data-streaming.md
diff --git a/radar/2020-09-01/docker.md b/radar/2020-09-01/docker.md
diff --git a/radar/2020-09-01/java.md b/radar/2020-09-01/java.md
diff --git a/radar/2020-09-01/javascript.md b/radar/2020-09-01/javascript.md
diff --git a/radar/2020-09-01/kotlin.md b/radar/2020-09-01/kotlin.md
@@ -7,7 +7,7 @@ featured: true
 
 [Kotlin](https://kotlinlang.org/) is one of our preferred backend technologies.
 
-We see Kotlin as a logical evolution of [Java](/languages-and-frameworks/java) bringing increased agility to
+We see Kotlin as a logical evolution of Java bringing increased agility to
 development teams while requiring a minimal learning curve when coming from Java.
 When using Kotlin we prefer Ktor over Spring Boot as web framework.
 

diff --git a/radar/2020-09-01/microservices.md b/radar/2020-09-01/microservices.md
diff --git a/radar/2020-09-01/nodejs.md b/radar/2020-09-01/nodejs.md
@@ -13,6 +13,6 @@ When compared to [Kotlin](/languages-and-frameworks/kotlin) we prefer to use Nod
   overhead in setting things up, also with regards to the JVM runtime that is used.
 - Full-stack development is important. E.g. for smaller projects where developers need to be
   full-stack, Node.js would generally be preferred since Node.js developers can relatively easily do
-  frontend development as well, both being [JavaScript](/languages-and-frameworks/javascript) based.
-- Doing [serverless](/methods-and-patterns/serverless) development. Node.js is more often used in this area compared to Kotlin and fits
-  better with our preferred serverless frameworks
+  frontend development as well, both being JavaScript based.
+- Doing serverless development. Node.js is more often used in this area compared to Kotlin, where it
+  makes sense to use Node.js.
diff --git a/radar/2020-09-01/react.md b/radar/2020-09-01/react.md
diff --git a/radar/2020-09-01/serverless.md b/radar/2020-09-01/serverless.md
diff --git a/radar/2021-09-18/ai-as-a-service.md b/radar/2021-09-18/ai-as-a-service.md
diff --git a/radar/2021-09-18/aws-ci-cd-tools.md b/radar/2021-09-18/aws-ci-cd-tools.md
diff --git a/radar/2021-09-18/bitbucket-cloud-and-pipelines.md b/radar/2021-09-18/bitbucket-cloud-and-pipelines.md
diff --git a/radar/2021-09-18/content-as-a-service.md b/radar/2021-09-18/content-as-a-service.md
diff --git a/radar/2021-09-18/contentful.md b/radar/2021-09-18/contentful.md
diff --git a/radar/2021-09-18/cypress.md b/radar/2021-09-18/cypress.md
diff --git a/radar/2021-09-18/dependency-drift-fitness-function.md b/radar/2021-09-18/dependency-drift-fitness-function.md
diff --git a/radar/2021-09-18/docker-developer-environments.md b/radar/2021-09-18/docker-developer-environments.md
diff --git a/radar/2021-09-18/event-sourcing.md b/radar/2021-09-18/event-sourcing.md
diff --git a/radar/2021-09-18/express.md b/radar/2021-09-18/express.md
diff --git a/radar/2021-09-18/jamstack.md b/radar/2021-09-18/jamstack.md
diff --git a/radar/2021-09-18/javascript.md b/radar/2021-09-18/javascript.md
diff --git a/radar/2021-09-18/k6.md b/radar/2021-09-18/k6.md
diff --git a/radar/2021-09-18/low-code-no-code-development.md b/radar/2021-09-18/low-code-no-code-development.md
diff --git a/radar/2021-09-18/magnolia.md b/radar/2021-09-18/magnolia.md
diff --git a/radar/2021-09-18/micro-frontends.md b/radar/2021-09-18/micro-frontends.md
diff --git a/radar/2021-09-18/progressive-web-applications.md b/radar/2021-09-18/progressive-web-applications.md
diff --git a/radar/2021-09-18/run-cost-as-architecture-fitness-function.md b/radar/2021-09-18/run-cost-as-architecture-fitness-function.md
diff --git a/radar/2021-09-18/strapi.md b/radar/2021-09-18/strapi.md
diff --git a/radar/2021-09-18/support-for-ie11.md b/radar/2021-09-18/support-for-ie11.md
diff --git a/radar/2021-09-18/typescript.md b/radar/2021-09-18/typescript.md
@@ -5,11 +5,11 @@ quadrant: languages-and-frameworks
 featured: true
 ---
 
-We prefer TypeScript to [JavaScript](/languages-and-frameworks/typescript). Our decision in more detail:
+We prefer TypeScript to JavaScript. Our decision in more detail:
 
-In the context of creating user-interfaces with [React](/languages-and-frameworks/react) and back-end applications
+In the context of creating user-interfaces with React and back-end applications
 using [Node.js](/languages-and-frameworks/nodejs), facing the proliferation of different languages used within INFO and the engineering
-communities at large we decided for TypeScript as the preferred language in favor of [JavaScript](/languages-and-frameworks/javascript) and
+communities at large we decided for TypeScript as the preferred language in favor of JavaScript and
 neglected Flow and others languages, to achieve a common way of working that will allow software
 engineers to work on or maintain multiple code bases over multiple projects, accepting limiting the
 options for teams and individual engineers to select their tools.