diff --git a/radar/2020-09-01/azure-devops.md b/radar/2020-09-01/azure-devops.md
deleted file mode 100644
index 24d1ba4..0000000
--- a/radar/2020-09-01/azure-devops.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: "Azure DevOps"
-ring: adopt
-quadrant: tools
-featured: true
----
-
diff --git a/radar/2020-09-01/bitbucket-cloud-and-pipelines.md b/radar/2020-09-01/bitbucket-cloud-and-pipelines.md
deleted file mode 100644
index 849197f..0000000
--- a/radar/2020-09-01/bitbucket-cloud-and-pipelines.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Bitbucket Cloud & Pipelines"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-The [Atlassian Bitbucket Cloud stack](https://bitbucket.org/) is a mature and widely used CI/CD solution offering good integration with various target platforms including AWS and Azure.
-Atlassian at this point does not offer an artifact repository so this solution requires additional tooling: AWS ECR or Azure Artifacts.
diff --git a/radar/2020-09-01/cloud-native-platforms.md b/radar/2020-09-01/cloud-native-platforms.md
deleted file mode 100644
index 4ecdc7b..0000000
--- a/radar/2020-09-01/cloud-native-platforms.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "Cloud-native platforms"
-ring: adopt
-quadrant: platforms-and-operations
-featured: true
----
-
-In the context of the infrastructure and architecture for new client solutions at INFO, facing
-market-conform requirements for fast time-to-market, high agility and pay-per-use costs, we prefer a
-vendor-specific cloud-native ([Amazon AWS](/platforms-and-operations/aws) or [Microsoft Azure](/platforms-and-operations/azure))
-solution over traditional on-premise or hybrid solutions (while still offering such solutions when
-there is a good reason), to achieve faster time-to-market, more agility and lower costs (depending on usage)
-because of the ability to use many out-of-the-box cloud vendor services, accepting a vendor lock-in towards the cloud
-provider, because some cloud services that will be used are specific to the cloud vendor in
-question.
diff --git a/radar/2020-09-01/data-science-and-machine-learning.md b/radar/2020-09-01/data-science-and-machine-learning.md
deleted file mode 100644
index d716df7..0000000
--- a/radar/2020-09-01/data-science-and-machine-learning.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Data Science and Machine Learning"
-ring: trial
-quadrant: methods-and-patterns
-featured: true
----
-
-If real data science and machine learning solutions are needed for our clients (beware of misusing
-this sometimes overhyped technology) we prefer to use the data science and ML services offered by
-AWS and Azure.
\ No newline at end of file
diff --git a/radar/2020-09-01/data-streaming.md b/radar/2020-09-01/data-streaming.md
deleted file mode 100644
index 5213e65..0000000
--- a/radar/2020-09-01/data-streaming.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Data Streaming"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-Stream processing is a useful technique for processing large volumes of data, and in combination with Event Processing and Streaming SQL, this also becomes a viable way for handling intra-service communication (pub/sub style). It should be preferred over direct intra-service API communication where possible.
\ No newline at end of file
diff --git a/radar/2020-09-01/docker.md b/radar/2020-09-01/docker.md
deleted file mode 100644
index f2c514f..0000000
--- a/radar/2020-09-01/docker.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Docker"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[Docker](https://www.docker.com/) is the industry standard for containerisation and we use it to build, run and test [microservices](/methods-and-patterns/microservices) and other containers.
diff --git a/radar/2020-09-01/java.md b/radar/2020-09-01/java.md
deleted file mode 100644
index 554d675..0000000
--- a/radar/2020-09-01/java.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Java"
-ring: hold
-quadrant: languages-and-frameworks
-featured: true
----
-
-We now prefer [Kotlin](/languages-and-frameworks/kotlin) over [Java](https://www.oracle.com/java/).
diff --git a/radar/2020-09-01/javascript.md b/radar/2020-09-01/javascript.md
deleted file mode 100644
index c75679f..0000000
--- a/radar/2020-09-01/javascript.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: "Adopt"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
diff --git a/radar/2020-09-01/kotlin.md b/radar/2020-09-01/kotlin.md
index ebf1c8c..83d7f3f 100644
--- 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
deleted file mode 100644
index 9bf4a4b..0000000
--- a/radar/2020-09-01/microservices.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Microservices"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-A microservices architecture is preferred over traditional monolithic architectures because it
-typically increases agility and time-to-market. Our preferred cloud vendors offer excellent support
-for microservices container architectures using vendor-specific services and/or Kubernetes
-solutions. For more background
-see: [Why you should use Microservices Architecture for your applications](https://info.nl/en/conversation/lessons-learned-why-you-should-use-microservices-architecture-for-your-applications/)
-and [The importance of loose coupling in microservice architecture](https://info.nl/en/conversation/the-importance-of-loose-coupling-in-microservice-architecture/).
\ No newline at end of file
diff --git a/radar/2020-09-01/nodejs.md b/radar/2020-09-01/nodejs.md
index 53e9dcd..92a1530 100644
--- 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
deleted file mode 100644
index 80592cf..0000000
--- a/radar/2020-09-01/react.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "React"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
-In the context of developing user interfaces for the web, facing a plethora of libraries and frameworks to create these user interfaces, we decided for [React](https://react.dev/) and neglected other libraries/frameworks like Angular, Vue.js, Svelte, jQuery and others, to achieve a preferred open source front-end library based on web technologies, accepting limiting our ability to work effectively on existing user interfaces for the web built using other libraries/frameworks, because React provides us with a uniform way of working with a proven mature technology, tool chain and extensive (community) resources that is portable to mobile development.
diff --git a/radar/2020-09-01/serverless.md b/radar/2020-09-01/serverless.md
deleted file mode 100644
index 0b09d93..0000000
--- a/radar/2020-09-01/serverless.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "Serverless"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-We prefer a serverless architecture (over other architectures like [microservices](/methods-and-patterns/microservices)) for most
-new client solutions, depending on requirements, potential constraints as well available expertise,
-because of increased agility and time-to-market. A combination of a serverless and
-microservice architecture is also a viable option in many cases.
-
-Serverless is often combined with an [event-driven architecture](/methods-and-patterns/event-driven-architecture).
-
-We use the [AWS definition of serverless](https://aws.amazon.com/serverless/):
-
-> "Serverless is the native architecture of the cloud that enables you to shift more of your
-> operational responsibilities to AWS (..or a different cloud vendor..), increasing your agility and innovation.
-> Serverless allows you to build and run applications and services without thinking about servers."
diff --git a/radar/2021-09-18/ai-as-a-service.md b/radar/2021-09-18/ai-as-a-service.md
deleted file mode 100644
index 403e9b1..0000000
--- a/radar/2021-09-18/ai-as-a-service.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "AI as a Service"
-ring: trial
-quadrant: methods-and-patterns
-featured: true
----
-
-
-When we want to incorporate AI into our solutions we prefer to use existing AI as a Service (AIaaS)
-services, when possible. We focus on the AIaaS services offered by <a href="aws.html">AWS</a> and 
-<a href="azure.html">Azure</a> but other AIaaS services, when they are a better fit, can also be used.
diff --git a/radar/2021-09-18/aws-ci-cd-tools.md b/radar/2021-09-18/aws-ci-cd-tools.md
deleted file mode 100644
index 49ab6b7..0000000
--- a/radar/2021-09-18/aws-ci-cd-tools.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "AWS CI CD Tools"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-The [AWS](/platforms-and-operations/aws) stack for CI CD solutions like CodeCommit, CodeBuild and CodeDeploy offer a well integrated solution for projects which are using Cloud Native components on AWS.
diff --git a/radar/2021-09-18/bitbucket-cloud-and-pipelines.md b/radar/2021-09-18/bitbucket-cloud-and-pipelines.md
deleted file mode 100644
index b6d4b24..0000000
--- a/radar/2021-09-18/bitbucket-cloud-and-pipelines.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Bitbucket Cloud & Pipelines"
-ring: assess
-quadrant: tools
-featured: true
----
-
-The [Atlassian Bitbucket Cloud stack](https://bitbucket.org/) is a mature and widely used CI/CD solution offering good integration with various target platforms including AWS and Azure.
-Atlassian at this point does not offer an artifact repository so this solution requires additional tooling: AWS ECR or Azure Artifacts.
diff --git a/radar/2021-09-18/content-as-a-service.md b/radar/2021-09-18/content-as-a-service.md
deleted file mode 100644
index 5fc533f..0000000
--- a/radar/2021-09-18/content-as-a-service.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Content as a Service"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-Content as a Service is a method of storing content in its raw form so that systems such as
-websites, apps, and devices can call and serve each piece as needed using an application programming
-interface (API). Any CMS we use at INFO should have this headless capability available.
\ No newline at end of file
diff --git a/radar/2021-09-18/contentful.md b/radar/2021-09-18/contentful.md
deleted file mode 100644
index c868231..0000000
--- a/radar/2021-09-18/contentful.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Contentful"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-A leading (commercial) headless Content as a Service CMS / content platform.
\ No newline at end of file
diff --git a/radar/2021-09-18/cypress.md b/radar/2021-09-18/cypress.md
deleted file mode 100644
index 5cb92e3..0000000
--- a/radar/2021-09-18/cypress.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Cypress"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-At INFO we strive for continuous automated functional testing and we prefer to use [Cypress](https://www.cypress.io/) as functional test tool.
diff --git a/radar/2021-09-18/dependency-drift-fitness-function.md b/radar/2021-09-18/dependency-drift-fitness-function.md
deleted file mode 100644
index ed2313e..0000000
--- a/radar/2021-09-18/dependency-drift-fitness-function.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "Dependency drift fitness function"
-ring: trial
-quadrant: methods-and-patterns
-featured: true
----
-
-Dependency drift means that libraries that are used for a project are out-of-date. A fitness
-function is trying to put a value to a check that is run, so that would be in this case the drift
-that is determined for the used libraries. A simple approach would be to count the number of
-out-dated libraries.
-
-The way to minimize dependency drift is to ensure that there is a (automated) process in place for
-updating dependencies. An automated approach can be setup using Renovate so that dependencies are
-checked and updated regularly.
\ No newline at end of file
diff --git a/radar/2021-09-18/docker-developer-environments.md b/radar/2021-09-18/docker-developer-environments.md
deleted file mode 100644
index fde7bc0..0000000
--- a/radar/2021-09-18/docker-developer-environments.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Docker Developer Environments"
-ring: assess
-quadrant: tools
-featured: true
----
-
-[Docker Development Environments](https://docs.docker.com/desktop/features/dev-environments) is still in preview, but the idea is that the whole code base,
-including development setup for coding in [Visual Studio Code](/tools/visual-studio-code). It can be a single container, or a
-compose based set of containers that make up a whole project. Any changes made in the code can be
-pushed as a new snapshot image to a docker repository, from where an other developer can continue in
-the same state.
diff --git a/radar/2021-09-18/event-sourcing.md b/radar/2021-09-18/event-sourcing.md
deleted file mode 100644
index 5d5fb7f..0000000
--- a/radar/2021-09-18/event-sourcing.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Event Sourcing"
-ring: assess
-quadrant: methods-and-patterns
-featured: true
----
-
-When using <a href="event-driven-architecture.html">Even-Driven Architectures</a> we urge you to consider using Event Sourcing.
-
-Event sourcing is an approach to thinking about persistent data where the primary record is a log of
-all events that make updates. A traditional representation of the database state can be entirely
-recreated by reprocessing this event log. Event sourcing’s benefits include strong auditing,
-creation of a historic state, and replaying of events for debugging and analysis. Event sourcing has
-been around for a while, but we think it is used much less than it should be.
-
-Event Sourcing ensures that all changes to the application state are stored as a sequence of events.
-Not only can we query these events, but we can also use the event log to reconstruct past states,
-and as a foundation to automatically adjust the state to cope with retroactive changes.
-Complementary to the capture of business meaningful events, the technique has positive implications
-for analytics in driving greater customer insight.
\ No newline at end of file
diff --git a/radar/2021-09-18/express.md b/radar/2021-09-18/express.md
deleted file mode 100644
index 66743f4..0000000
--- a/radar/2021-09-18/express.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Express"
-ring: hold
-quadrant: languages-and-frameworks
-featured: false
----
-
-We prefer [Fastify](https://fastify.dev/) over [Express](https://expressjs.com/) as [Node.js](/languages-and-frameworks/nodejs) web framework.
diff --git a/radar/2021-09-18/jamstack.md b/radar/2021-09-18/jamstack.md
deleted file mode 100644
index 19da351..0000000
--- a/radar/2021-09-18/jamstack.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Jamstack"
-ring: trial
-quadrant: methods-and-patterns
-featured: true
----
-
-Jamstack is an architecture designed to make the web faster, more secure, and easier to scale. It
-builds on many of the tools and workflows which developers love, and which bring maximum
-productivity. The core principles of pre-rendering, and decoupling, enable sites and applications to
-be delivered with greater confidence and resilience than ever before. 
\ No newline at end of file
diff --git a/radar/2021-09-18/javascript.md b/radar/2021-09-18/javascript.md
deleted file mode 100644
index 158cc8f..0000000
--- a/radar/2021-09-18/javascript.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "JavaScript"
-ring: hold
-quadrant: languages-and-frameworks
-featured: true
----
-
-We now prefer [Typescript](/languages-and-frameworks/typescript) over [JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript).
diff --git a/radar/2021-09-18/k6.md b/radar/2021-09-18/k6.md
deleted file mode 100644
index 0e5afd0..0000000
--- a/radar/2021-09-18/k6.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "k6"
-ring: trial
-quadrant: tools
-featured: true
----
-
-[k6](https://k6.io/) is a modern and strong candidate for load & performance (and stress) test tooling. Being [JavaScript](/languages-and-frameworks/javascript)-based it is often easier to use with our available team skills than other load & performance test tooling. We already use it in some of our client teams with good results. Also see: https://www.thoughtworks.com/radar/tools/k6
diff --git a/radar/2021-09-18/low-code-no-code-development.md b/radar/2021-09-18/low-code-no-code-development.md
deleted file mode 100644
index cbbaaca..0000000
--- a/radar/2021-09-18/low-code-no-code-development.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Low-code / no-code development"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-Low-code platforms use graphical user interfaces and configuration in order to create applications.
-
-We want to assess the general use case of such platforms in our context and also gain more
-experience and knowledge on the market leading platforms in this area.
\ No newline at end of file
diff --git a/radar/2021-09-18/magnolia.md b/radar/2021-09-18/magnolia.md
deleted file mode 100644
index a15448a..0000000
--- a/radar/2021-09-18/magnolia.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Magnolia"
-ring: hold
-quadrant: platforms-and-operations
-featured: true
----
-
-We have other preferred headless CMSes in our radar that replace Magnolia as our preferred CMS.
-
diff --git a/radar/2021-09-18/micro-frontends.md b/radar/2021-09-18/micro-frontends.md
deleted file mode 100644
index 3aaa9c8..0000000
--- a/radar/2021-09-18/micro-frontends.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Micro Frontends"
-ring: assess
-quadrant: methods-and-patterns
-featured: true
----
-
-An architectural style where independently deliverable frontend applications are composed into a
-greater whole. Some key benefits that we've seen from micro-frontends are, smaller, more
-cohesive and maintainable code bases, more scalable organisations with decoupled, autonomous teams and
-the ability to upgrade, update, or even rewrite parts of the frontend in a more incremental fashion
-than was previously possible.
\ No newline at end of file
diff --git a/radar/2021-09-18/progressive-web-applications.md b/radar/2021-09-18/progressive-web-applications.md
deleted file mode 100644
index 8aafca0..0000000
--- a/radar/2021-09-18/progressive-web-applications.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Progressive Web Applications"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-PWAs are web applications that take advantage of the latest technologies to combine the best of web
-and native mobile applications. All current desktop browsers and common mobile browsers support the
-Service Worker API and most “meta-frameworks” make implementation trivial.
-
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
deleted file mode 100644
index 298d59d..0000000
--- a/radar/2021-09-18/run-cost-as-architecture-fitness-function.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Run cost as architecture fitness function"
-ring: assess
-quadrant: methods-and-patterns
-featured: true
----
-
-Architecture run cost is the actual cost for running a particular (cloud) configuration, including
-maintenance, etc. With the push for more cloud based solutions, it is important to have a good view
-on the cost of the choices that have to be, and have been made. A fitness function for run-cost
-should be used as a guide for choosing solutions, as these are directly impacting the customer.
\ No newline at end of file
diff --git a/radar/2021-09-18/strapi.md b/radar/2021-09-18/strapi.md
deleted file mode 100644
index f31a5a9..0000000
--- a/radar/2021-09-18/strapi.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Strapi"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[Strapi](https://strapi.io/) is our preferred CMS. It is widely used, open-source and headless with
-a good API. Usually the free community edition serves our needs but Strapi also offers enterprise editions with
-additional features.
\ No newline at end of file
diff --git a/radar/2021-09-18/support-for-ie11.md b/radar/2021-09-18/support-for-ie11.md
deleted file mode 100644
index dd6fe05..0000000
--- a/radar/2021-09-18/support-for-ie11.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Support for Internet Explorer 11"
-ring: hold
-quadrant: platforms-and-operations
-featured: true
----
-
-No relevant browser anymore for the target audience of our clients.
diff --git a/radar/2021-09-18/typescript.md b/radar/2021-09-18/typescript.md
index 55bae2e..b0a409e 100644
--- 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.
diff --git a/radar/2022-05-17/aws-ci-cd-tools.md b/radar/2022-05-17/aws-ci-cd-tools.md
deleted file mode 100644
index 634f273..0000000
--- a/radar/2022-05-17/aws-ci-cd-tools.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "AWS CI CD Tools"
-ring: hold
-quadrant: tools
-featured: true
----
-
-The [AWS](/platforms-and-operations/aws) stack for CI CD solutions like CodeCommit, CodeBuild and CodeDeploy offers a well integrated
-solution for projects which are using Cloud Native components on AWS. However we find that <a href="github.html">GitHub</a>
-surpasses the AWS CI CD stack.
diff --git a/radar/2022-05-17/azure-devops.md b/radar/2022-05-17/azure-devops.md
deleted file mode 100644
index 1217c2e..0000000
--- a/radar/2022-05-17/azure-devops.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Azure DevOps"
-ring: hold
-quadrant: tools
-featured: true
----
-
-Having used [Azure DevOps](https://azure.microsoft.com/en-us/products/devops/) for some client projects we have come to the conclusion that it is not the
-best fit for our needs as we feel <a href="github.html">GitHub</a> surpasses it in all areas. Both are owned by Microsoft but
-Microsoft seems to put all their cards on GitHub. We see no reason to choose Azure DevOps over
-GitHub even for cloud-native Azure projects.
diff --git a/radar/2022-05-17/bitbucket-cloud-and-pipelines.md b/radar/2022-05-17/bitbucket-cloud-and-pipelines.md
deleted file mode 100644
index 9d990c6..0000000
--- a/radar/2022-05-17/bitbucket-cloud-and-pipelines.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Bitbucket Cloud & Pipelines"
-ring: hold
-quadrant: tools
-featured: true
----
-
-Having used [Atlassian Bitbucket Cloud stack](https://bitbucket.org/) for a number of years both for internal and for client
-projects we have come to the conclusion that it is no longer the best fit for our needs as we feel
-<a href="github.html">GitHub</a> surpasses it in all areas.
diff --git a/radar/2022-05-17/contentful.md b/radar/2022-05-17/contentful.md
deleted file mode 100644
index 1b8e287..0000000
--- a/radar/2022-05-17/contentful.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Contentful"
-ring: hold
-quadrant: platforms-and-operations
-featured: false
----
-
-For our current offerings we think [Strapi CMS](/tools/strapi) is a better choice.
-
-[Contentful](https://www.contentful.com/) is certainly a very powerful content platform, however we feel that for the client projects
-that we implement it is overkill and Strapi is more suitable.
diff --git a/radar/2022-05-17/data-science-and-machine-learning.md b/radar/2022-05-17/data-science-and-machine-learning.md
deleted file mode 100644
index 3ebd1ce..0000000
--- a/radar/2022-05-17/data-science-and-machine-learning.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Data Science and Machine Learning"
-ring: trial
-quadrant: methods-and-patterns
-featured: true
----
-
-We prefer to use <a href="ai-as-a-service.html">AI as a Service</a> services whenever feasible over 
-(typically more custom) data science and machine learning solutions. 
-
-If custom data science and machine learning solutions are really needed for our clients we 
-prefer to use the data science and ML services offered by <a href="aws.html">AWS</a> and <a href="azure.html">Azure</a>.
\ No newline at end of file
diff --git a/radar/2022-05-17/docker-developer-environments.md b/radar/2022-05-17/docker-developer-environments.md
deleted file mode 100644
index 8f30640..0000000
--- a/radar/2022-05-17/docker-developer-environments.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Docker Developer Environments"
-ring: hold
-quadrant: tools
-featured: false
----
-
-We now prefer <a href="github-code-spaces.html">GitHub Code Spaces</a> over [Docker Development Environments](https://docs.docker.com/desktop/features/dev-environments).
diff --git a/radar/2022-05-17/evolutionary-architecture.md b/radar/2022-05-17/evolutionary-architecture.md
deleted file mode 100644
index c6ce4ab..0000000
--- a/radar/2022-05-17/evolutionary-architecture.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Evolutionary Architecture"
-ring: assess
-quadrant: methods-and-patterns
-featured: true
----
-
-[Evolutionary architecture](https://www.thoughtworks.com/decoder/evolutionary-architecture) is an
-approach to building software that’s designed to evolve over time as
-business priorities change, customer demands shift, and new technologies emerge.
-
-We want to assess using some of the techniques in this area, like for example using 'Fitness Function
-Development'.
-
diff --git a/radar/2022-05-17/github-code-spaces.md b/radar/2022-05-17/github-code-spaces.md
deleted file mode 100644
index c04c39f..0000000
--- a/radar/2022-05-17/github-code-spaces.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "GitHub Code Spaces"
-ring: assess
-quadrant: tools
-featured: true
----
-
-[GitHub Code Spaces](https://github.com/features/codespaces) is a very easy way to set up browser-based development environments and may be
-especially suited for projects in (low) maintenance and such. Previously we had Docker Development
-Environments in Assess as potential candidate in this space but we now think GitHub Code Spaces is a
-much better and easier solution for us.
\ No newline at end of file
diff --git a/radar/2022-05-17/magnolia.md b/radar/2022-05-17/magnolia.md
deleted file mode 100644
index d1e1850..0000000
--- a/radar/2022-05-17/magnolia.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Magnolia"
-ring: hold
-quadrant: platforms-and-operations
-featured: false
----
-
-We have other preferred headless CMSes in our radar that replace Magnolia as our preferred CMS.
-
diff --git a/radar/2022-05-17/microservices.md b/radar/2022-05-17/microservices.md
deleted file mode 100644
index f364699..0000000
--- a/radar/2022-05-17/microservices.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "Microservices"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-A microservices architecture is preferred over traditional monolithic architectures because it
-typically increases agility and time-to-market. Our preferred cloud vendors offer excellent support
-for microservices container architectures using vendor-specific services and/or Kubernetes
-solutions. For more background
-see: [Why you should use Microservices Architecture for your applications](https://info.nl/en/conversation/lessons-learned-why-you-should-use-microservices-architecture-for-your-applications/)
-and [The importance of loose coupling in microservice architecture](https://info.nl/en/conversation/the-importance-of-loose-coupling-in-microservice-architecture/).
-
-We also encourage you to consider <a href="serverless.html">serverless</a>, potentially as part of 
-an <a href="event-driven-architecture.html">event-driven architecture</a>.
\ No newline at end of file
diff --git a/radar/2022-05-17/platform-as-a-service.md b/radar/2022-05-17/platform-as-a-service.md
deleted file mode 100644
index 45a84df..0000000
--- a/radar/2022-05-17/platform-as-a-service.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Platform as a Service (PaaS)"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-Using a PaaS platform for specific projects (instead of using more low-level cloud-native services from [AWS](/platforms-and-operations/aws) or [Azure](/platforms-and-operations/azure))
-can have benefits in efficiency, time-to-market and costs. We want to investigate the use case of
-such platforms in our context and if we agree on it define one or more preferred PaaS platforms
-as well as define guidelines on when to use them.
diff --git a/radar/2022-05-17/progressive-web-applications.md b/radar/2022-05-17/progressive-web-applications.md
deleted file mode 100644
index 81b2a41..0000000
--- a/radar/2022-05-17/progressive-web-applications.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Progressive Web Applications"
-ring: assess
-quadrant: methods-and-patterns
-featured: true
----
-
-PWAs are web applications that take advantage of the latest technologies to combine the best of web
-and native mobile applications. All current desktop browsers and common mobile browsers support the
-Service Worker API and most “meta-frameworks” make implementation trivial.
-
diff --git a/radar/2022-05-17/support-for-ie11.md b/radar/2022-05-17/support-for-ie11.md
deleted file mode 100644
index 02e395c..0000000
--- a/radar/2022-05-17/support-for-ie11.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Support for Internet Explorer 11"
-ring: hold
-quadrant: platforms-and-operations
-featured: false
----
-
-No relevant browser anymore for the target audience of our clients.
diff --git a/radar/2022-05-17/trpc.md b/radar/2022-05-17/trpc.md
deleted file mode 100644
index cf59d3f..0000000
--- a/radar/2022-05-17/trpc.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "tRPC"
-ring: assess
-quadrant: languages-and-frameworks
-featured: true
----
-
-[tRPC](https://trpc.io/) is a tool that provides type-safety between your front and back-ends,
-hence it makes it really easy to build scalable and robust backends quickly for [Node.js](/languages-and-frameworks/nodejs) based apps.
-Currently, the dominant way of making typesafe APIs is using [GraphQL](/languages-and-frameworks/graphql) (it's awesome).
-Since GraphQL is a query language for APIs, it doesn't take full advantage of [TypeScript](/languages-and-frameworks/typescript), it comes with excess boilerplate code and requires a lot of initial setup.
-If you're already using TypeScript everywhere, you can share types directly between the client and the server without the need of any code generation.
diff --git a/radar/2022-09-22/ai-as-a-service.md b/radar/2022-09-22/ai-as-a-service.md
deleted file mode 100644
index 231cdbe..0000000
--- a/radar/2022-09-22/ai-as-a-service.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "AI as a Service"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-This blip is currently no longer in trial because we are focussing on other topics.
diff --git a/radar/2022-09-22/aws-ci-cd-tools.md b/radar/2022-09-22/aws-ci-cd-tools.md
deleted file mode 100644
index b5f49ec..0000000
--- a/radar/2022-09-22/aws-ci-cd-tools.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "AWS CI CD Tools"
-ring: hold
-quadrant: tools
-featured: false
----
-
-The [AWS](/platforms-and-operations/aws) stack for CI CD solutions like CodeCommit, CodeBuild and CodeDeploy offers a well integrated
-solution for projects which are using Cloud Native components on AWS. However we find that <a href="github.html">GitHub</a>
-surpasses the AWS CI CD stack.
diff --git a/radar/2022-09-22/azure-devops.md b/radar/2022-09-22/azure-devops.md
deleted file mode 100644
index c5ba216..0000000
--- a/radar/2022-09-22/azure-devops.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Azure DevOps"
-ring: hold
-quadrant: tools
-featured: false
----
-
-Having used [Azure DevOps](https://azure.microsoft.com/en-us/products/devops/) for some client projects we have come to the conclusion that it is not the
-best fit for our needs as we feel <a href="github.html">GitHub</a> surpasses it in all areas. Both are owned by Microsoft but
-Microsoft seems to put all their cards on GitHub. We see no reason to choose Azure DevOps over
-GitHub even for cloud-native Azure projects.
diff --git a/radar/2022-09-22/bitbucket-cloud-and-pipelines.md b/radar/2022-09-22/bitbucket-cloud-and-pipelines.md
deleted file mode 100644
index 49d27b2..0000000
--- a/radar/2022-09-22/bitbucket-cloud-and-pipelines.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Bitbucket Cloud & Pipelines"
-ring: hold
-quadrant: tools
-featured: false
----
-
-Having used [Atlassian Bitbucket Cloud stack](https://bitbucket.org/) for a number of years both for internal and for client
-projects we have come to the conclusion that it is no longer the best fit for our needs as we feel
-<a href="github.html">GitHub</a> surpasses it in all areas.
diff --git a/radar/2022-09-22/data-science-and-machine-learning.md b/radar/2022-09-22/data-science-and-machine-learning.md
deleted file mode 100644
index 8d7e57d..0000000
--- a/radar/2022-09-22/data-science-and-machine-learning.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Data Science and Machine Learning"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-This blip is currently no longer in trial because we are focussing on other topics.
diff --git a/radar/2022-09-22/database-as-a-service.md b/radar/2022-09-22/database-as-a-service.md
deleted file mode 100644
index a7718d3..0000000
--- a/radar/2022-09-22/database-as-a-service.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Database as a Service (DBaaS)"
-ring: assess
-quadrant: methods-and-patterns
-featured: true
----
-
-Database as a Service (or Serverless Database) is a modern cloud-based database solution where you no longer need to 
-manage and maintain the underlying database technologies. 
-Many cloud vendors are starting to offer solutions in this space.
-
-We want to assess if DBaaS solutions can help our client teams and what impact it would have when 
-we start using them.
diff --git a/radar/2022-09-22/dependency-drift-fitness-function.md b/radar/2022-09-22/dependency-drift-fitness-function.md
deleted file mode 100644
index a39dbc1..0000000
--- a/radar/2022-09-22/dependency-drift-fitness-function.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Dependency drift fitness function"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-Our vision remains as it was however this blip is no longer in trial because we think this blip is  
-too low-level to still be part of our radar.
-
-Also since we have automated dependency updates in place for most teams this has become somewhat less relevant. 
diff --git a/radar/2022-09-22/event-sourcing.md b/radar/2022-09-22/event-sourcing.md
deleted file mode 100644
index 635cd09..0000000
--- a/radar/2022-09-22/event-sourcing.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Event Sourcing"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-This blip is currently no longer in assess because we are focussing on other topics.
diff --git a/radar/2022-09-22/evolutionary-architecture.md b/radar/2022-09-22/evolutionary-architecture.md
deleted file mode 100644
index dd90c8b..0000000
--- a/radar/2022-09-22/evolutionary-architecture.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Evolutionary Architecture"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-This blip is currently no longer in assess because we are focussing on other topics.
-
diff --git a/radar/2022-09-22/github-code-spaces.md b/radar/2022-09-22/github-code-spaces.md
deleted file mode 100644
index 9bbf4c5..0000000
--- a/radar/2022-09-22/github-code-spaces.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "GitHub Code Spaces"
-ring: trial
-quadrant: tools
-featured: true
----
-
-[GitHub Code Spaces](https://github.com/features/codespaces) is a very easy way to set up browser-based development environments and may be
-especially suited for projects in (low) maintenance and such. 
-
-We are currently trialing GitHub Code Spaces in our teams.
\ No newline at end of file
diff --git a/radar/2022-09-22/jamstack.md b/radar/2022-09-22/jamstack.md
deleted file mode 100644
index 0496a83..0000000
--- a/radar/2022-09-22/jamstack.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Jamstack"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-Jamstack is an architecture designed to make the web faster, more secure, and easier to scale. It
-builds on many of the tools and workflows which developers love, and which bring maximum
-productivity. The core principles of pre-rendering, and decoupling, enable sites and applications to
-be delivered with greater confidence and resilience than ever before. 
\ No newline at end of file
diff --git a/radar/2022-09-22/java.md b/radar/2022-09-22/java.md
deleted file mode 100644
index fb91897..0000000
--- a/radar/2022-09-22/java.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Java"
-ring: hold
-quadrant: languages-and-frameworks
-featured: false
----
-
-We now prefer [Kotlin](/languages-and-frameworks/kotlin) over [Java](https://www.oracle.com/java/).
diff --git a/radar/2022-09-22/javascript.md b/radar/2022-09-22/javascript.md
deleted file mode 100644
index a5460f4..0000000
--- a/radar/2022-09-22/javascript.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "JavaScript"
-ring: hold
-quadrant: languages-and-frameworks
-featured: false
----
-
-We now prefer [Typescript](/languages-and-frameworks/typescript) over [JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript).
diff --git a/radar/2022-09-22/k6.md b/radar/2022-09-22/k6.md
deleted file mode 100644
index a422cc8..0000000
--- a/radar/2022-09-22/k6.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "k6"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[k6](https://k6.io/) is a modern and strong load & performance (and stress) test tool.
-Being [JavaScript](/languages-and-frameworks/javascript)-based it is typically easier to use in our teams compared to other
-load & performance test tooling.
-
-We have been using it for some time in our client teams with good results.
-Also see: https://www.thoughtworks.com/radar/tools/k6
diff --git a/radar/2022-09-22/micro-frontends.md b/radar/2022-09-22/micro-frontends.md
deleted file mode 100644
index b7db65a..0000000
--- a/radar/2022-09-22/micro-frontends.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Micro Frontends"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-This blip is currently no longer in trial because we are focussing on other topics.
diff --git a/radar/2022-09-22/monorepo.md b/radar/2022-09-22/monorepo.md
deleted file mode 100644
index 6e5b637..0000000
--- a/radar/2022-09-22/monorepo.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Monorepo"
-ring: trial
-quadrant: methods-and-patterns
-featured: false
----
-
-A <a href="https://monorepo.tools/">monorepo</a> is a single source code repository containing multiple distinct projects, 
-with well-defined relationships.
-
-It brings certain benefits but, as with any technique, also comes with certain trade-offs.
-
-We are trialing the monorepo technique using various monorepo tools in our client teams. 
diff --git a/radar/2022-09-22/platform-as-a-service.md b/radar/2022-09-22/platform-as-a-service.md
deleted file mode 100644
index 84c2ae5..0000000
--- a/radar/2022-09-22/platform-as-a-service.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Platform as a Service (PaaS)"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-Using a PaaS platform for specific projects (instead of using more low-level cloud-native services from [AWS](/platforms-and-operations/aws) or [Azure](/platforms-and-operations/azure))
-can have benefits in efficiency, time-to-market and costs. We want to investigate the use case of
-such platforms in our context and if we agree on it define one or more preferred PaaS platforms
-as well as define guidelines on when to use them.
-
-We are currently trialing the [Vercel](/platforms-and-operations/vercel) PaaS platform in this context.
diff --git a/radar/2022-09-22/progressive-web-applications.md b/radar/2022-09-22/progressive-web-applications.md
deleted file mode 100644
index ffc60ae..0000000
--- a/radar/2022-09-22/progressive-web-applications.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Progressive Web Applications"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-This blip is currently no longer in trial because we are focussing on other topics.
-
-
diff --git a/radar/2022-09-22/run-cost-as-architecture-fitness-function.md b/radar/2022-09-22/run-cost-as-architecture-fitness-function.md
deleted file mode 100644
index 0dbab53..0000000
--- a/radar/2022-09-22/run-cost-as-architecture-fitness-function.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Run cost as architecture fitness function"
-ring: hold
-quadrant: methods-and-patterns
-featured: false
----
-
-This blip is currently no longer in assess because we are focussing on other topics.
diff --git a/radar/2022-09-22/terraform.md b/radar/2022-09-22/terraform.md
deleted file mode 100644
index cff43e9..0000000
--- a/radar/2022-09-22/terraform.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "Terraform"
-ring: assess
-quadrant: tools
-featured: true
----
-
-<a href="https://www.terraform.io/">Terraform</a> is an open-source Infrastructure as Code (IaC) tool which can be used to provision 
-infrastructures on various cloud vendors and SaaS providers.
-
-We continue to believe in <a href="infrastructure-as-code.html">Infrastructure as Code</a> but having 
-come across the limitations and challenges of using cloud vendor-specific solutions in this space we 
-now want to assess the use of Terraform.
diff --git a/radar/2022-09-22/vercel.md b/radar/2022-09-22/vercel.md
deleted file mode 100644
index 4579c14..0000000
--- a/radar/2022-09-22/vercel.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Vercel"
-ring: trial
-quadrant: platforms-and-operations
-featured: true
----
-
-<a href="https://vercel.com/">Vercel</a> is a leading [PaaS](/platforms-and-operations/platform-as-a-service) provider for front-end apps with a strong developer focus.
-Vercel is also one of the companies behind [Next.js](/languages-and-frameworks/nextjs), a front-end framework heavily used in our teams.
-
-We want to trial using Vercel as a PaaS platform in our projects.
diff --git a/radar/2022-12-05/algolia.md b/radar/2022-12-05/algolia.md
deleted file mode 100644
index 5f1df54..0000000
--- a/radar/2022-12-05/algolia.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Algolia"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-In the space of search platforms we are trialling [Algolia](https://www.algolia.com). Algolia is an API-based SaaS search service which we think is very easy to implement in our projects. It also integrates nicely with [Strapi](/tools/strapi).
-
-For our AWS-based projects you may consider using [Amazon CloudSearch](https://aws.amazon.com/cloudsearch) instead, depending on your specific needs.
diff --git a/radar/2022-12-05/amazon-cognito.md b/radar/2022-12-05/amazon-cognito.md
deleted file mode 100644
index 8849255..0000000
--- a/radar/2022-12-05/amazon-cognito.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Amazon Cognito"
-ring: adopt
-quadrant: platforms-and-operations
-featured: true
----
-
-In the space of Identity and Access Management (IAM) we prefer to use <a href="https://aws.amazon.com/cognito/">Amazon Cognito</a> for Customer Identity and Access Management. Cognito may be combined with [AWS IAM](/platforms-and-operations/aws-iam) depending on your needs. Cognito provides amongst others user sign-up, sign-in and access control features while AWS IAM is more low-level focussing on AWS account and permission management.
-
-When using Cognito strongly consider to also use the <a href="https://www.npmjs.com/package/@aws-amplify/ui-react">Amplify UI React</a> UI library which provides out-of-the-box UI components for Cognito authentication workflows.
-
-We are also trialling the SaaS IAM service [Clerk](/platforms-and-operations/clerk) as an potential alternative solution for projects which are not using AWS as the main platform (but typically use a [PaaS](/platforms-and-operations/platform-as-a-service) provider instead).
diff --git a/radar/2022-12-05/amazon-s3.md b/radar/2022-12-05/amazon-s3.md
deleted file mode 100644
index 70c5b1e..0000000
--- a/radar/2022-12-05/amazon-s3.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Amazon S3"
-ring: adopt
-quadrant: platforms-and-operations
-featured: true
----
-
-We prefer to use <a href="https://aws.amazon.com/s3/">Amazon S3</a> as cloud object storage solution.
-S3 is de de-facto industry standard in this space and is used as object store not just for solutions that are fully hosted on <a href="aws.html">AWS</a> but also for other, for example [PaaS](/platforms-and-operations/platform-as-a-service), solutions.
diff --git a/radar/2022-12-05/aws-iam.md b/radar/2022-12-05/aws-iam.md
deleted file mode 100644
index 34cab1b..0000000
--- a/radar/2022-12-05/aws-iam.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "AWS IAM"
-ring: adopt
-quadrant: platforms-and-operations
-featured: true
----
-
-In the space of Identity and Access Management we prefer to use <a href="https://aws.amazon.com/iam/">AWS IAM</a> and/or [Amazon Cognito](/platforms-and-operations/amazon-cognito) depending on the specific needs of a project.
-
-We are also trialling the SaaS IAM service [Clerk](/platforms-and-operations/clerk) as an alternative solution for projects which are not using AWS as the main platform (but typically use a [PaaS](/platforms-and-operations/platform-as-a-service) provider instead).
diff --git a/radar/2022-12-05/aws.md b/radar/2022-12-05/aws.md
index e6de54a..f86df7f 100644
--- a/radar/2022-12-05/aws.md
+++ b/radar/2022-12-05/aws.md
@@ -6,5 +6,3 @@ featured: true
 ---
 
 We prefer [AWS](https://aws.amazon.com) as our general all purpose cloud-native platform because AWS is the (local as well as global) market leader in the space of cloud-native computing, and we think it offers the best set of services for our needs when compared to other cloud providers.
-
-However we are also trialling and assessing various [PaaS](/platforms-and-operations/platform-as-a-service) providers such as [Vercel](/platforms-and-operations/vercel) to see if these providers can become our preferred hosting platform(s) for solutions where the functionality and related complexity that AWS offers is not required. We believe in such cases a PaaS provider offers a cheaper and more flexible alternative over a traditional cloud provider such as AWS.
diff --git a/radar/2022-12-05/axiom.md b/radar/2022-12-05/axiom.md
deleted file mode 100644
index a5badce..0000000
--- a/radar/2022-12-05/axiom.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Axiom"
-ring: trial
-quadrant: tools
-featured: true
----
-
-In the space of centralized all-purpose logging and monitoring we are trialling [Axiom](https://www.axiom.co).
-
-In this same space we do also use [Sentry](/tools/sentry). However Sentry is focused on frontend error logging, while tools such as Axiom fit the need for all-purpose (application and system) logging.
-
-There are many other players in this field, some of which we have used or trialled inclusing Logtail and Datadog but for us Axiom holds the best cards for our needs. We have also found that the <a href="https://aws.amazon.com/solutions/implementations/centralized-logging/">centralized logging solution offered by AWS</a> is too cumbersome to use and does not offer the same range of features that tools like Axiom do.
diff --git a/radar/2022-12-05/chai.md b/radar/2022-12-05/chai.md
deleted file mode 100644
index a975c46..0000000
--- a/radar/2022-12-05/chai.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Chai"
-ring: hold
-quadrant: languages-and-frameworks
-featured: true
----
-
-We have have been using [Chai](https://www.chaijs.com/) as our [Typescript](/languages-and-frameworks/typescript/) assertion library in our projects but now that we prefer [Vitest](/tools/vitest) as our unit testing framework we feel that the use of Chai has become obsolete.
diff --git a/radar/2022-12-05/chakra-ui.md b/radar/2022-12-05/chakra-ui.md
deleted file mode 100644
index 19530d8..0000000
--- a/radar/2022-12-05/chakra-ui.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Chakra UI"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: false
----
-
-We prefer to use <a href="https://chakra-ui.com/">Chakra UI</a> to build [React](/languages-and-frameworks/react)-based component libraries in our projects, depening on the requirements of the project. For most project we do prefer [Tailwind CSS](/languages-and-frameworks/tailwind-css) in this space.
-
-We strongly believe in using [Atomic Design](https://atomicdesign.bradfrost.com/) as a design methodology in our projects and we believe Chakra UI is an excellent fit for this.
-
-We considered the <a href="https://styled-components.com/">Styled Components</a> framework but we believe Chakra UI to be a better fit.
diff --git a/radar/2022-12-05/clerk.md b/radar/2022-12-05/clerk.md
deleted file mode 100644
index 63b62f2..0000000
--- a/radar/2022-12-05/clerk.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Clerk"
-ring: trial
-quadrant: platforms-and-operations
-featured: true
----
-
-In the space of Identity and Access Management (IAM) we are trialling <a href="https://clerk.dev/">Clerk</a> as a potential IAM solution for projects which are not using AWS as the main platform (but typically use PaaS provider instead).
-
-For AWS-based solutions we generally prefer to use [AWS IAM](/platforms-and-operations/aws-iam) and/or [Amazon Cognito](/platforms-and-operations/amazon-cognito).
-
-We have also considered alternatives such as <a href="https://www.ory.sh/">Ory</a> and <a href="https://auth0.com/">Auth0</a> but, while very similar, we believe Clerk will be the best fit for our needs.
diff --git a/radar/2022-12-05/cockroachdb.md b/radar/2022-12-05/cockroachdb.md
deleted file mode 100644
index f99745a..0000000
--- a/radar/2022-12-05/cockroachdb.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "CockroachDB"
-ring: trial
-quadrant: platforms-and-operations
-featured: false
----
-
-In the space of <a href="dbaas.html">DBaaS</a> services, we are trialling <a href="https://www.cockroachlabs.com/">CockroachDB</a> to see if it could be our preferred DBaaS solution, and if so, under what circumstances it would be our preferred choice.
-
-CockroachDB is one of the leaders in the DBaaS space and <a href="https://www.thoughtworks.com/radar/platforms-and-operations/cockroachdb">has featured on the Thoughtworks Technology Radar</a> in the past as a recommended service to assess.
diff --git a/radar/2022-12-05/content-as-a-service.md b/radar/2022-12-05/content-as-a-service.md
deleted file mode 100644
index a739124..0000000
--- a/radar/2022-12-05/content-as-a-service.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Content as a Service"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-In the Content as a Service space we prefer to use [Strapi CMS](/tools/strapi) but are also trialling [Sanity](/tools/sanity).
diff --git a/radar/2022-12-05/database-as-a-service.md b/radar/2022-12-05/database-as-a-service.md
deleted file mode 100644
index 242c7e7..0000000
--- a/radar/2022-12-05/database-as-a-service.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Database as a Service (DBaaS)"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-Database as a Service (or Serverless Database) is a modern cloud-based database solution where you no longer need to 
-manage and maintain the underlying database technologies. 
-
-We think DBaaS solutions are the best solution for many of our datastore/database needs and we are trialing <a href="cockroachdb.html">CockroachDB</a> in this space.
diff --git a/radar/2022-12-05/digitalocean.md b/radar/2022-12-05/digitalocean.md
deleted file mode 100644
index fa27827..0000000
--- a/radar/2022-12-05/digitalocean.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Digital Ocean"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-We are assessing <a href="https://www.digitalocean.com/">DigitalOcean</a> as general [PaaS](/platforms-and-operations/platform-as-a-service) provider. It is the PaaS market leader and provides a wide range of generic PaaS functionalities.
-
-We believe for solutions where the complexity of <a href="aws.html">AWS</a> is not warranted a PaaS provider can offer a cheaper and more flexible alternative over a traditional cloud provider such as AWS.
-
-In the same space we are also trialing <a href="vercel.html">Vercel</a> and assessing <a href="render.html">Render</a>.
diff --git a/radar/2022-12-05/git-rebase-and-merge-merge-strategy.md b/radar/2022-12-05/git-rebase-and-merge-merge-strategy.md
deleted file mode 100644
index 3247103..0000000
--- a/radar/2022-12-05/git-rebase-and-merge-merge-strategy.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Rebase and merge as Git merge strategy"
-ring: adopt
-quadrant: methods-and-patterns
-featured: true
----
-
-In the context of maintaining repositories using Git we prefer a rebase and merge Git merge strategy (<code>rebase + merge --no-ff</code>) so that the Git history in our codebases is linear.
-
-Git’s default strategy is to merge commits in chronological order, however having an overview of the sequence in which changes to the codebase were made is often more useful in understanding how the codebase evolved over time. This is the reason why we prefer a rebase + merge strategy.
-
-Generally all our Git repo's in [GitHub](/tools/github) should be configured to support this merge strategy.
-
-We also strongly encourage to squash commits when merging a feature branch onto the main branch in order to keep the Git log clean. There is typically no need to keep the history of individual commits in a feature branch in our view.
diff --git a/radar/2022-12-05/google-analytics.md b/radar/2022-12-05/google-analytics.md
deleted file mode 100644
index 1a258a7..0000000
--- a/radar/2022-12-05/google-analytics.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Google Analytics"
-ring: adopt
-quadrant: platforms-and-operations
-featured: true
----
-
-<a href="https://analytics.google.com/">Google Analytics</a> has been for many years and will continue to be our preferred web analytics platform. To make this preferenence more explicit we have now added it to our tech radar.
-
diff --git a/radar/2022-12-05/idea-intellij.md b/radar/2022-12-05/idea-intellij.md
index 1e06fe2..130307d 100644
--- a/radar/2022-12-05/idea-intellij.md
+++ b/radar/2022-12-05/idea-intellij.md
@@ -7,4 +7,4 @@ featured: true
 
 We now generally prefer [Visual Studio Code (VS Code)](/tools/visual-studio-code) as code editor and IDE for developing software in our teams.
 
-However when working on our [Kotlin](/languages-and-frameworks/kotlin) and [Java](/languages-and-frameworks/java) code bases we still prefer to use <a href="https://www.jetbrains.com/idea/">IntelliJ IDEA</a> as IDE.
+However when working on our [Kotlin](/languages-and-frameworks/kotlin) and Java code bases we still prefer to use <a href="https://www.jetbrains.com/idea/">IntelliJ IDEA</a> as IDE.
diff --git a/radar/2022-12-05/jest.md b/radar/2022-12-05/jest.md
deleted file mode 100644
index 62c47a7..0000000
--- a/radar/2022-12-05/jest.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Jest"
-ring: hold
-quadrant: languages-and-frameworks
-featured: true
----
-
-We have have been using <a href="https://jestjs.io/">Jest</a> as [TypeScript](/languages-and-frameworks/typescript) unit test framework in our projects but we now prefer [Vitest](/tools/vitest), mainly due to the faster performance.
diff --git a/radar/2022-12-05/keycloak.md b/radar/2022-12-05/keycloak.md
index 0c3a795..af9e695 100644
--- a/radar/2022-12-05/keycloak.md
+++ b/radar/2022-12-05/keycloak.md
@@ -7,4 +7,4 @@ featured: true
 
 In the past we have been using [Keycloak](https://www.keycloak.org/) as our preferred Identity and Access Management (IAM) solution. We found this to be a very good fit with our on-premise hosting services.
 
-But now that we prefer to host our solutions on cloud-native platforms and use (SaaS) cloud services where it makes sense, we find that Keycloak is no longer the best fit for our needs and therefore we now prefer the IAM services that AWS offers ([AWS IAM](/platforms-and-operations/aws-iam) and [Amazon Cognito](/platforms-and-operations/amazon-cognito)) while also trialling the SaaS IAM service [Clerk](/platforms-and-operations/clerk).
+But now that we prefer to host our solutions on cloud-native platforms and use (SaaS) cloud services where it makes sense, we find that Keycloak is no longer the best fit for our needs and therefore we now prefer the IAM services that AWS offers (AWS IAM and Amazon Cognito) while also trialling the SaaS IAM service Clerk.
diff --git a/radar/2022-12-05/kotlin.md b/radar/2022-12-05/kotlin.md
index f9b3fd1..92692fc 100644
--- a/radar/2022-12-05/kotlin.md
+++ b/radar/2022-12-05/kotlin.md
@@ -5,7 +5,7 @@ quadrant: languages-and-frameworks
 featured: true
 ---
 
-We now prefer [Node.js](/languages-and-frameworks/nodejs) as backend technology over [Kotlin](https://kotlinlang.org/) (and [Java](/languages-and-frameworks/java)).
+We now prefer [Node.js](/languages-and-frameworks/nodejs) as backend technology over [Kotlin](https://kotlinlang.org/) (and Java).
 
 In the context of choosing the backend technology for new projects, facing challenges in staffing our projects with backend developers and in sharing technical backend skills, we decided to prefer Node.js (and the related [Typescript](/languages-and-frameworks/typescript) stack/ecosystem) over Kotlin (the Kotlin/Java/JVM stack/ecosystem) as our main backend technology, to achieve more consolidation on backend technology within our company, accepting that we will to a large degree stop using the Kotlin (and Java) skills and experiences we have gathered and that we will need to put effort into helping developers switch from Kotlin to Node.js.
 
diff --git a/radar/2022-12-05/mocha.md b/radar/2022-12-05/mocha.md
deleted file mode 100644
index 0242abe..0000000
--- a/radar/2022-12-05/mocha.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Mocha"
-ring: hold
-quadrant: languages-and-frameworks
-featured: true
----
-
-We have have been using [Mocha](https://mochajs.org/) as [TypeScript](/languages-and-frameworks/typescript) unit test framework in our projects but we now prefer [Vitest](/tools/vitest), mainly due to the faster performance.
diff --git a/radar/2022-12-05/nestjs.md b/radar/2022-12-05/nestjs.md
deleted file mode 100644
index 788456c..0000000
--- a/radar/2022-12-05/nestjs.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "NestJS"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
-We prefer to use <a href="https://nestjs.com/">NestJS</a> for [Node.js](/languages-and-frameworks/nodejs) projects when there is a relative high degree of complexity. We feel it is especially well suited for containerised microservices.
-
-NestJS is an opinionated OO-inspired backend MVC framework which allows us build more complex Node.js backends more efficiently. For more simple backends the use of NestJS may be overkill and may add more overhead than is warranted.
diff --git a/radar/2022-12-05/nextjs.md b/radar/2022-12-05/nextjs.md
deleted file mode 100644
index d454b95..0000000
--- a/radar/2022-12-05/nextjs.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Next.js"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
-<a href="https://nextjs.org/">Next.js</a> is our preferred full-stack web framework for our [React](/languages-and-frameworks/react) and [Node.js](/languages-and-frameworks/nodejs)-based web applications.
-
-Next.js allows us to build React-based web applications efficiently and offers solutions for both server-side rendering as well as statically generated pages.
-
-We also considered <a href="https://redwoodjs.com/">RedwoodJS</a> but we believe Next.js is a better match for our needs.
diff --git a/radar/2022-12-05/postgresql.md b/radar/2022-12-05/postgresql.md
index 3aa4a8b..dfa2947 100644
--- a/radar/2022-12-05/postgresql.md
+++ b/radar/2022-12-05/postgresql.md
@@ -7,4 +7,4 @@ featured: true
 
 Our preferred relational database is (and has been for many years) <a href="https://www.postgresql.org/">PostgreSQL</a>. We prefer it over cloud-vendor specific relational databases. In our projects we experienced several shortcomings in such cloud-vendor specific relational databases and we see no advantages in using them over PostgreSQL.
 
-[AWS](/platforms-and-operations/aws) as well as [DBaaS](/methods-and-patterns/database-as-s-service) providers support PostgreSQL (or are compatible with it). When on AWS it may be that Amazon Aurora PostgreSQL may be a preferred choice over Amazon RDS for PostgreSQL depending on your (business) requirements. Please see <a href="https://aws.amazon.com/blogs/database/is-amazon-rds-for-postgresql-or-amazon-aurora-postgresql-a-better-choice-for-me/">Is Amazon RDS for PostgreSQL or Amazon Aurora PostgreSQL a better choice for me?</a> for more details.
+[AWS](/platforms-and-operations/aws) as well as database-as-a-service providers support PostgreSQL (or are compatible with it). When on AWS it may be that Amazon Aurora PostgreSQL may be a preferred choice over Amazon RDS for PostgreSQL depending on your (business) requirements. Please see <a href="https://aws.amazon.com/blogs/database/is-amazon-rds-for-postgresql-or-amazon-aurora-postgresql-a-better-choice-for-me/">Is Amazon RDS for PostgreSQL or Amazon Aurora PostgreSQL a better choice for me?</a> for more details.
diff --git a/radar/2022-12-05/prisma.md b/radar/2022-12-05/prisma.md
deleted file mode 100644
index 260b563..0000000
--- a/radar/2022-12-05/prisma.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Prisma"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
-<a href="https://www.prisma.io/">Prisma</a> is our preferred <a href="nodejs.html">Node.js</a> and <a href="typescript.html">TypeScript</a> ORM framework.
-
-We feel that Prisma is the best mature and widely-used ORM in the Node.js ecosystem at the moment and for us it provides all the features we need.
\ No newline at end of file
diff --git a/radar/2022-12-05/pulumi.md b/radar/2022-12-05/pulumi.md
deleted file mode 100644
index 9882b7a..0000000
--- a/radar/2022-12-05/pulumi.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Pulumi"
-ring: trial
-quadrant: tools
-featured: true
----
-
-We are trialling <a href="https://www.pulumi.com/">Pulumi</a> to see if it can become our preferred [Infrastructure as Code](/methods-and-patterns/infrastructure-as-code) solution.
-
-We are also considering [Terraform](/tools/terraform) as alternative.
diff --git a/radar/2022-12-05/render.md b/radar/2022-12-05/render.md
deleted file mode 100644
index 3ba5d09..0000000
--- a/radar/2022-12-05/render.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Render"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-We are assessing [Render](https://render.com/) as general [PaaS](/platforms-and-operations/platform-as-a-service) provider.
-
-We believe for solutions where the complexity of [AWS](/platforms-and-operations/aws) is not warranted a PaaS provider can offer a cheaper and more flexible alternative over a traditional cloud provider such as AWS.
-
-In the same space we are also trialing [Vercel](/platforms-and-operations/vercel) and assessing [DigitalOcean](/platforms-and-operations/digitalocean).
diff --git a/radar/2022-12-05/sanity.md b/radar/2022-12-05/sanity.md
deleted file mode 100644
index aa69505..0000000
--- a/radar/2022-12-05/sanity.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Sanity"
-ring: assess
-quadrant: tools
-featured: true
----
-
-In the space of Content Management Systems or content platforms we are trialling the SaaS headless content platform [Sanity](https://www.sanity.io).
-
-While [Strapi](/tools/strapi) is our preferred CMS, it is not a SaaS service. The new upcoming Strapi Cloud offering will also not but a full SaaS content platform but rather a [PaaS](/platforms-and-operations/platform-as-a-service) CMS solution. Depending on the needs of a project a SaaS content platform may be required or a better fit over a PaaS CMS solution. In such cases we think that a service such as Sanity can be good match.
-
-While there are many alternative SaaS content platforms on the market, some of which we have also considered including [Contentful](/platforms-and-operations/contentful), we believe Sanity holds the best cards for our needs mainly because of it's ease of use, it's strong focus on a good developer experience and because it allows for a great deal of flexibility.
diff --git a/radar/2022-12-05/serverless-framework.md b/radar/2022-12-05/serverless-framework.md
deleted file mode 100644
index e941f4d..0000000
--- a/radar/2022-12-05/serverless-framework.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Serverless Framework"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
-We prefer to use the <a href="https://www.serverless.com/framework/">Serverless Framework</a> for building [serverless](/methods-and-patterns/serverless) functions.
diff --git a/radar/2022-12-05/tailwind-css.md b/radar/2022-12-05/tailwind-css.md
deleted file mode 100644
index db719d2..0000000
--- a/radar/2022-12-05/tailwind-css.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Tailwind CSS"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
-<a href="https://tailwindcss.com/">Tailwind CSS</a> is our preferred CSS framework. It helps us to manage CSS efficiently, also on more complex projects.
-
-Most often we prefer to use Tailwind CSS over [Chakra](/languages-and-frameworks/chakra-ui), but this does depend on the specific needs of a project.
diff --git a/radar/2022-12-05/tanstack-query.md b/radar/2022-12-05/tanstack-query.md
index 3e2ffae..815f967 100644
--- a/radar/2022-12-05/tanstack-query.md
+++ b/radar/2022-12-05/tanstack-query.md
@@ -5,4 +5,4 @@ quadrant: languages-and-frameworks
 featured: true
 ---
 
-<a href="https://tanstack.com/query/">TanStack Query</a> _(formerly known as React Query)_ is our preferred [React](/languages-and-frameworks/react) framework for managing state in the frontends of our web applications.
+<a href="https://tanstack.com/query/">TanStack Query</a> _(formerly known as React Query)_ is our preferred React framework for managing state in the frontends of our web applications.
diff --git a/radar/2022-12-05/terraform.md b/radar/2022-12-05/terraform.md
deleted file mode 100644
index d524b56..0000000
--- a/radar/2022-12-05/terraform.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Terraform"
-ring: trial
-quadrant: tools
-featured: true
----
-
-We are trialling <a href="https://www.terraform.io/">Terraform</a> to see if it can become our preferred Infrastructure as Code solution. The Terraform Cloud offering (managed Terraform) will also be taken into account.
-
-We are also considering <a href="pulumi.html">Pulumi</a> as alternative.
diff --git a/radar/2022-12-05/trpc.md b/radar/2022-12-05/trpc.md
deleted file mode 100644
index c2eaa61..0000000
--- a/radar/2022-12-05/trpc.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "tRPC"
-ring: trial
-quadrant: languages-and-frameworks
-featured: true
----
-
-We want to trial [tRPC](https://trpc.io/) because we think, especially in combination with [Next.js](/languages-and-frameworks/nextjs), it can serve as a more efficient and more type-safe way to implement APIs when compared to [GraphQL](/languages-and-frameworks/graphql)
diff --git a/radar/2022-12-05/turborepo.md b/radar/2022-12-05/turborepo.md
deleted file mode 100644
index 459fc35..0000000
--- a/radar/2022-12-05/turborepo.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Turborepo"
-ring: trial
-quadrant: tools
-featured: true
----
-
-We are trialling <a href="https://turbo.build/repo">Turborepo</a> to see if it can become our preferred [monorepo](/methods-and-patterns/monorepo) solution.
-
-Turborepo is made by [Vercel](/platforms-and-operations/vercel), who are also the creators of [Next.js](/languages-and-frameworks/nextjs), and the out-of-the-box integration provided between these frameworks and services can be decisive factor, while still taking into account other considerations such as a strong dependency on Vercel.
-
-We also considered the <a href="https://nx.dev/">Nx</a> monorepo framework but after having trialed it we feel that Turborepo is a better fit for our needs.
diff --git a/radar/2022-12-05/visual-studio-code.md b/radar/2022-12-05/visual-studio-code.md
index ac6eab1..a164869 100644
--- a/radar/2022-12-05/visual-studio-code.md
+++ b/radar/2022-12-05/visual-studio-code.md
@@ -9,4 +9,4 @@ We prefer to use the free open-source source code editor [Visual Studio Code (VS
 
 It is the most widely used code editor (and IDE with the right extensions) for working with [Typescript](/languages-and-frameworks/typescript) code bases and it serves all our needs.
 
-However when working on our [Kotlin](/languages-and-frameworks/kotlin) and [Java](/languages-and-frameworks/java) code bases we still prefer to use [IntelliJ IDEA](/tools/idea-intellij) as IDE.
+However when working on our [Kotlin](/languages-and-frameworks/kotlin) and Java code bases we still prefer to use [IntelliJ IDEA](/tools/idea-intellij) as IDE.
diff --git a/radar/2022-12-05/vitest.md b/radar/2022-12-05/vitest.md
deleted file mode 100644
index 57c025f..0000000
--- a/radar/2022-12-05/vitest.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Vitest"
-ring: adopt
-quadrant: tools
-featured: false
----
-
-We prefer to use <a href="https://vitest.dev/">Vitest</a> as [Typescript](/languages-and-frameworks/typeScript) unit test framework.
-
-We have have been using other unit test frameworks like [Jest](/languages-and-frameworks/jest) and [Mocha](/languages-and-frameworks/mocha) in our projects as well but mainly due to the better performance we now prefer Vitest. Vitest is compatible with Jest and therefore this is not a huge change when switching from Jest.
diff --git a/radar/2023-03-01/azure.md b/radar/2023-03-01/azure.md
index 006e02e..21b2bc1 100644
--- a/radar/2023-03-01/azure.md
+++ b/radar/2023-03-01/azure.md
@@ -7,6 +7,6 @@ featured: false
 
 We decided to strongly prefer <a href="aws.html">AWS</a> over Azure as cloud-native platform for new client solutions from now on and therefore put Azure on hold. The main reason for this decision is that at this moment in time we wish to consolidate more on our preferred technology stack to make it easier for us to staff our projects and maintain our client solutions.
 
-We prefer AWS over Azure since AWS is the (local as well as global) market leader in the space of cloud-native computing, and we think offers the best set of services for our needs. Next to AWS we are trialing and assessing [PaaS](/platforms-and-operations/platform-as-a-service) solutions as well.
+We prefer AWS over Azure since AWS is the (local as well as global) market leader in the space of cloud-native computing, and we think offers the best set of services for our needs. Next to AWS we are trialing and assessing PaaS solutions as well.
 
 Eventhough we now favour AWS we will continue to support our existing client solutions running on Azure and we will make sure we maintain our Azure skills in order to do so.
diff --git a/radar/2023-03-01/backstage.md b/radar/2023-03-01/backstage.md
deleted file mode 100644
index 2026c18..0000000
--- a/radar/2023-03-01/backstage.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Backstage"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-[Backstage](https://backstage.io/) is an open platform for building developer portals. Developed by Spotify it provides a centralized place to look up information about the tooling, services, dependencies and architecture of a team's software solution. It can help for example in managing a [Software Bill Of Materials](https://www.thoughtworks.com/radar/methods-and-patterns/software-bill-of-materials) within a team and even our entire company.
-
-We want to assess the general use case of such platforms in our context and specifically gather experience with Backstage being a market leading solution in this space.
\ No newline at end of file
diff --git a/radar/2023-03-01/chai.md b/radar/2023-03-01/chai.md
deleted file mode 100644
index 77ff379..0000000
--- a/radar/2023-03-01/chai.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Chai"
-ring: hold
-quadrant: languages-and-frameworks
-featured: false
----
-
-We have have been using [Chai](https://www.chaijs.com/) as our [Typescript](/languages-and-frameworks/typescript/) assertion library in our projects but now that we prefer [Vitest](/tools/vitest) as our unit testing framework we feel that the use of Chai has become obsolete.
diff --git a/radar/2023-03-01/cloud-native-platforms.md b/radar/2023-03-01/cloud-native-platforms.md
deleted file mode 100644
index 8b94528..0000000
--- a/radar/2023-03-01/cloud-native-platforms.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "Cloud-native platforms-and-operations"
-ring: adopt
-quadrant: platforms-and-operations
-featured: false
----
-
-This is now such a given (also in the industry) that we no longer feature it on our tech radar.
-
-In the context of the infrastructure and architecture for new client solutions at INFO, facing
-market-conform requirements for fast time-to-market, high agility and pay-per-use costs, we prefer a
-vendor-specific cloud-native ([Amazon AWS](/platforms-and-operations/aws) or [Microsoft Azure](/platforms-and-operations/azure))
-solution over traditional on-premise or hybrid solutions (while still offering such solutions when
-there is a good reason), to achieve faster time-to-market, more agility and lower costs (depending on usage)
-because of the ability to use many out-of-the-box cloud vendor services, accepting a vendor lock-in towards the cloud
-provider, because some cloud services that will be used are specific to the cloud vendor in
-question.
diff --git a/radar/2023-03-01/cockroachdb.md b/radar/2023-03-01/cockroachdb.md
deleted file mode 100644
index 984add5..0000000
--- a/radar/2023-03-01/cockroachdb.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "CockroachDB"
-ring: hold
-quadrant: platforms-and-operations
-featured: true
----
-
-In the space of <a href="dbaas.html">DBaaS</a> services, we have trialed <a href="https://www.cockroachlabs.com/">CockroachDB</a> to see if it could be our preferred DBaaS solution, and if so, under what circumstances it would be our preferred choice.
-
-We have decided to hold off on using CockroachDB for the time being because we feel it is overkill for our current needs where we typically have no need for large-scale data distribution. For now we think for most of our needs 'plain' [PostgreSQL](/platforms-and-operations/postgresql) (as a [PaaS](/platforms-and-operations/platform-as-a-service)) is a better fit when it comes to relational databases.
diff --git a/radar/2023-03-01/content-as-a-service.md b/radar/2023-03-01/content-as-a-service.md
deleted file mode 100644
index 04e3cbd..0000000
--- a/radar/2023-03-01/content-as-a-service.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Content as a Service"
-ring: adopt
-quadrant: methods-and-patterns
-featured: false
----
-
-This is now such a given (also in the industry) that we no longer feature it on our tech radar.
-
-Content as a Service is a method of storing content in its raw form so that systems such as
-websites, apps, and devices can call and serve each piece as needed using an application programming
-interface (API). Any CMS we use should have this headless capability available.
\ No newline at end of file
diff --git a/radar/2023-03-01/data-streaming.md b/radar/2023-03-01/data-streaming.md
deleted file mode 100644
index ecbbfa3..0000000
--- a/radar/2023-03-01/data-streaming.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Data Streaming"
-ring: adopt
-quadrant: methods-and-patterns
-featured: false
----
-
-We still consider this important but in order to reduce clutter we no longer feature it on our tech radar.
-
-Stream processing is a useful technique for processing large volumes of data, and in combination with Event Processing and Streaming SQL, this also becomes a viable way for handling intra-service communication (pub/sub style). It should be preferred over direct intra-service API communication where possible.
\ No newline at end of file
diff --git a/radar/2023-03-01/docker.md b/radar/2023-03-01/docker.md
deleted file mode 100644
index d50a826..0000000
--- a/radar/2023-03-01/docker.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Docker"
-ring: adopt
-quadrant: tools
-featured: false
----
-
-[Docker](https://www.docker.com/) is the industry standard for containerisation and we use it to build, run and test [microservices](/methods-and-patterns/microservices) and other containers.
diff --git a/radar/2023-03-01/github-packages.md b/radar/2023-03-01/github-packages.md
deleted file mode 100644
index 2c2d474..0000000
--- a/radar/2023-03-01/github-packages.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "GitHub Packages"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[GitHub Packages](https://docs.github.com/en/packages) is a package registry for storing and sharing packages (such as software artifacts) with a team. 
-
-Having used on-premise solutions such as [Nexus Repository](https://www.sonatype.com/products/nexus-repository) we now prefer the use of GitHub Packages for our projects that require an artifact repository.
\ No newline at end of file
diff --git a/radar/2023-03-01/google-analytics.md b/radar/2023-03-01/google-analytics.md
deleted file mode 100644
index 2402eb1..0000000
--- a/radar/2023-03-01/google-analytics.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: "Google Analytics"
-ring: adopt
-quadrant: platforms-and-operations
-featured: false
----
-
-[Google Analytics](https://analytics.google.com/) has been for many years and will continue to be our preferred web analytics platform. To make this preferenence more explicit we have now added it to our tech radar.
-
diff --git a/radar/2023-03-01/graphql.md b/radar/2023-03-01/graphql.md
index ec96b18..ff28692 100644
--- a/radar/2023-03-01/graphql.md
+++ b/radar/2023-03-01/graphql.md
@@ -6,9 +6,8 @@ featured: true
 ---
 
 [GraphQL](https://graphql.org/) is a powerful way to expose an API for frontend use.
-We generally prefer [tRPC](/languages-and-frameworks/trpc) over GraphQL for frontend-backend integration but still consider GraphQL a valid alternative in cases where tRPC is not a good match.
 
-When tRPC is not a good match we generally prefer GraphQL over REST because it increases flexibility and agility,
+We generally prefer GraphQL over REST because it increases flexibility and agility,
 depending on the context (e.g. external APIs may still require REST for API clients' needs).
 
 Beware
diff --git a/radar/2023-03-01/idea-intellij.md b/radar/2023-03-01/idea-intellij.md
index 8106a1d..9eb2211 100644
--- a/radar/2023-03-01/idea-intellij.md
+++ b/radar/2023-03-01/idea-intellij.md
@@ -7,4 +7,4 @@ featured: false
 
 We now generally prefer [Visual Studio Code (VS Code)](/tools/visual-studio-code) as code editor and IDE for developing software in our teams.
 
-However when working on our [Kotlin](/languages-and-frameworks/kotlin) and [Java](/languages-and-frameworks/java) code bases we still prefer to use <a href="https://www.jetbrains.com/idea/">IntelliJ IDEA</a> as IDE.
+However when working on our [Kotlin](/languages-and-frameworks/kotlin) and Java code bases we still prefer to use <a href="https://www.jetbrains.com/idea/">IntelliJ IDEA</a> as IDE.
diff --git a/radar/2023-03-01/jest.md b/radar/2023-03-01/jest.md
deleted file mode 100644
index 5ba935a..0000000
--- a/radar/2023-03-01/jest.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Jest"
-ring: hold
-quadrant: languages-and-frameworks
-featured: false
----
-
-We have have been using <a href="https://jestjs.io/">Jest</a> as [TypeScript](/languages-and-frameworks/typescript) unit test framework in our projects but we now prefer [Vitest](/tools/vitest), mainly due to the faster performance.
diff --git a/radar/2023-03-01/keycloak.md b/radar/2023-03-01/keycloak.md
index 48a3cbe..ab62467 100644
--- a/radar/2023-03-01/keycloak.md
+++ b/radar/2023-03-01/keycloak.md
@@ -7,4 +7,4 @@ featured: false
 
 In the past we have been using [Keycloak](https://www.keycloak.org/) as our preferred Identity and Access Management (IAM) solution. We found this to be a very good fit with our on-premise hosting services.
 
-But now that we prefer to host our solutions on cloud-native platforms and use (SaaS) cloud services where it makes sense, we find that Keycloak is no longer the best fit for our needs and therefore we now prefer the IAM services that AWS offers ([AWS IAM](/platforms-and-operations/aws-iam) and [Amazon Cognito](/platforms-and-operations/amazon-cognito)) while also trialling the SaaS IAM service [Clerk](/platforms-and-operations/clerk).
+But now that we prefer to host our solutions on cloud-native platforms and use (SaaS) cloud services where it makes sense, we find that Keycloak is no longer the best fit for our needs and therefore we now prefer the IAM services offered by our cloud platform.
diff --git a/radar/2023-03-01/kotlin.md b/radar/2023-03-01/kotlin.md
index d445602..9dd8637 100644
--- a/radar/2023-03-01/kotlin.md
+++ b/radar/2023-03-01/kotlin.md
@@ -5,7 +5,7 @@ quadrant: languages-and-frameworks
 featured: false
 ---
 
-We now prefer [Node.js](/languages-and-frameworks/nodejs) as backend technology over [Kotlin](https://kotlinlang.org/) (and [Java](/languages-and-frameworks/java)).
+We now prefer [Node.js](/languages-and-frameworks/nodejs) as backend technology over [Kotlin](https://kotlinlang.org/) (and Java).
 
 In the context of choosing the backend technology for new projects, facing challenges in staffing our projects with backend developers and in sharing technical backend skills, we decided to prefer Node.js (and the related [Typescript](/languages-and-frameworks/typescript) stack/ecosystem) over Kotlin (the Kotlin/Java/JVM stack/ecosystem) as our main backend technology, to achieve more consolidation on backend technology within our company, accepting that we will to a large degree stop using the Kotlin (and Java) skills and experiences we have gathered and that we will need to put effort into helping developers switch from Kotlin to Node.js.
 
diff --git a/radar/2023-03-01/microservices.md b/radar/2023-03-01/microservices.md
deleted file mode 100644
index 12d0707..0000000
--- a/radar/2023-03-01/microservices.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "Microservices"
-ring: adopt
-quadrant: methods-and-patterns
-featured: false
----
-
-This is now such a given (also in the industry) that we no longer feature it on our tech radar.
-
-A microservices architecture is preferred over traditional monolithic architectures because it
-typically increases agility and time-to-market. Our preferred cloud vendors offer excellent support
-for microservices container architectures using vendor-specific services and/or Kubernetes
-solutions. For more background
-see: [Why you should use Microservices Architecture for your applications](https://info.nl/en/conversation/lessons-learned-why-you-should-use-microservices-architecture-for-your-applications/)
-and [The importance of loose coupling in microservice architecture](https://info.nl/en/conversation/the-importance-of-loose-coupling-in-microservice-architecture/).
\ No newline at end of file
diff --git a/radar/2023-03-01/mocha.md b/radar/2023-03-01/mocha.md
deleted file mode 100644
index a08b6f8..0000000
--- a/radar/2023-03-01/mocha.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Mocha"
-ring: hold
-quadrant: languages-and-frameworks
-featured: false
----
-
-We have have been using [Mocha](https://mochajs.org/) as [TypeScript](/languages-and-frameworks/typescript) unit test framework in our projects but we now prefer [Vitest](/tools/vitest), mainly due to the faster performance.
diff --git a/radar/2023-03-01/react.md b/radar/2023-03-01/react.md
deleted file mode 100644
index df49687..0000000
--- a/radar/2023-03-01/react.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "React"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: false
----
-
-This is now such a given (also in the industry) that we no longer feature it on our tech radar.
-
-In the context of developing user interfaces for the web, facing a plethora of libraries and frameworks to create these user interfaces, we decided for [React](https://react.dev/) and neglected other libraries/frameworks like Angular, Vue.js, Svelte, jQuery and others, to achieve a preferred open source front-end library based on web technologies, accepting limiting our ability to work effectively on existing user interfaces for the web built using other libraries/frameworks, because React provides us with a uniform way of working with a proven mature technology, tool chain and extensive (community) resources that is portable to mobile development.
diff --git a/radar/2023-03-01/superblocks.md b/radar/2023-03-01/superblocks.md
deleted file mode 100644
index d26ef81..0000000
--- a/radar/2023-03-01/superblocks.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Superblocks"
-ring: assess
-quadrant: platforms-and-operations
-featured: true
----
-
-[Superblocks](https://www.superblocks.com/) is a low-code platform for quickly building and deploying applications.
-
-As part of [assessing the use of low-code platforms-and-operations](/platforms-and-operations/low-code-no-code-development) we specifically want to assess Superblocks in our context.
diff --git a/radar/2023-03-01/trpc.md b/radar/2023-03-01/trpc.md
deleted file mode 100644
index 380e35c..0000000
--- a/radar/2023-03-01/trpc.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "tRPC"
-ring: adopt
-quadrant: languages-and-frameworks
-featured: true
----
-
-For internal frontend-backend communication we prefer [tRPC](https://trpc.io) because we think, especially in combination with [Next.js](/languages-and-frameworks/nextjs), it is as a more efficient and more type-safe solution when compared to [GraphQL](/languages-and-frameworks/graphql).
-
-For externally facing ('public') APIs where we are not in control of the clients using our API GraphQL or REST are viable alternatives.
diff --git a/radar/2023-03-01/turborepo.md b/radar/2023-03-01/turborepo.md
deleted file mode 100644
index 0f98a99..0000000
--- a/radar/2023-03-01/turborepo.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Turborepo"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-When possible we prefer to use a [monorepo](/methods-and-patterns/monorepo) solution in our teams using the monorepo tool [Turborepo](https://turbo.build/repo). We believe using such a monorepo helps us to improve our development experience, productivity and software quality.
diff --git a/radar/2023-03-01/visual-studio-code.md b/radar/2023-03-01/visual-studio-code.md
index 5f5164b..bf6b5e0 100644
--- a/radar/2023-03-01/visual-studio-code.md
+++ b/radar/2023-03-01/visual-studio-code.md
@@ -9,4 +9,4 @@ We prefer to use the free open-source source code editor [Visual Studio Code (VS
 
 It is the most widely used code editor (and IDE with the right extensions) for working with [Typescript](/languages-and-frameworks/typescript) code bases and it serves all our needs.
 
-However when working on our [Kotlin](/languages-and-frameworks/kotlin) and [Java](/languages-and-frameworks/java) code bases we still prefer to use [IntelliJ IDEA](/tools/idea-intellij) as IDE.
+However when working on our [Kotlin](/languages-and-frameworks/kotlin) and Java code bases we still prefer to use [IntelliJ IDEA](/tools/idea-intellij) as IDE.
diff --git a/radar/2023-08-01/bdd.md b/radar/2023-08-01/bdd.md
index 4351abe..0e1bbbd 100644
--- a/radar/2023-08-01/bdd.md
+++ b/radar/2023-08-01/bdd.md
@@ -11,10 +11,8 @@ Behavior-Driven Development (BDD) is a collaborative approach to software develo
 
 [Cucumber](https://cucumber.io/) is a tool that supports BDD. It reads Gherkin documents and validates that the code performs as expected.
 
-[Cypress](/tools/cypress.html) is an end-to-end testing framework that can be used alongside Gherkin and Cucumber for testing web applications. It's popular for its easy setup and fast, reliable testing capabilities. Cypress can validate various aspects of your application, ranging from the UI functionality to complete workflows.
+[Playwright](/tools/playwright) is a powerful tool for end-to-end testing that complements BDD approaches. With support for multiple browsers, headless testing, and API controls, Playwright offers robust testing capabilities for both simple and complex applications.
 
-[Playwright](/tools/playwright.html) is another powerful tool for end-to-end testing that complements BDD approaches. With support for multiple browsers, headless testing, and API controls, Playwright offers robust testing capabilities for both simple and complex applications.
-
-Adopting BDD, Gherkin, Cucumber, [Cypress](/tools/cypress.html), and [Playwright](/tools/playwright.html) in our workflow allows for a clear understanding and discussion of requirements across the team, including non-technical stakeholders. This fosters collaboration and helps prevent miscommunication. Automated testing through Gherkin, Cucumber, Cypress, and Playwright also encourages the development of more robust, bug-free software.
+Adopting BDD, Gherkin, Cucumber and [Playwright](/tools/playwright) in our workflow allows for a clear understanding and discussion of requirements across the team, including non-technical stakeholders. This fosters collaboration and helps prevent miscommunication. Automated testing through Gherkin, Cucumber and Playwright also encourages the development of more robust, bug-free software.
 
 However, BDD is not a one-size-fits-all solution. It works best when the team is committed to the collaborative approach and when complex business rules need to be understood by all stakeholders.
diff --git a/radar/2023-08-01/contentful.md b/radar/2023-08-01/contentful.md
deleted file mode 100644
index d5c992a..0000000
--- a/radar/2023-08-01/contentful.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "Contentful CMS"
-ring: trial
-quadrant: tools
-featured: true
----
-
-[Contentful](https://www.contentful.com/) is a versatile headless CMS that allows teams to manage content across multiple digital platforms. Its API-first approach decouples content management from presentation, enabling parallel workflows between developers and content creators for faster digital product delivery.
-
-### Why Contentful?
-
-- **Headless Architecture:** Delivers content anywhere via robust APIs that are suitable for websites, mobile apps, and more.
-
-- **Developer-Friendly:** Strong SDKs and APIs provide easy integration with various tech stacks, making it a flexible and scalable solution.
-
-- **Content Modeling:** Offers simple and intuitive content modeling for managing complex structures.
-
-- **Scalability and Localization:** Supports enterprise-scale operations with global content management and localization features.
-
-### Considerations at INFO
-
-- Contentful is currently trialed for its ability to integrate seamlessly into our existing workflows and provide an easy-to-use platform for developers and content editors.
-
-- **Current Focus:** Evaluating scalability, customization options, and ease of content management across projects.
-
-Contentful's potential to streamline content management makes it a strong candidate as we continue to assess its fit for our long-term needs.
diff --git a/radar/2023-08-01/cypress.md b/radar/2023-08-01/cypress.md
deleted file mode 100644
index a9b6c29..0000000
--- a/radar/2023-08-01/cypress.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: "Cypress"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-At INFO, we prioritize continuous automated testing to ensure high-quality software delivery. [Cypress](https://www.cypress.io/) remains our tool of choice for functional testing due to its robustness, developer-friendly environment, and extensive feature set.
-
-
-
-### Why Cypress?
-
-- **Developer Experience:** Cypress provides a smooth setup process, real-time reloading, and direct debugging in the browser, enhancing productivity and reducing time to identify issues.
-
-- **End-to-end Testing:** It offers comprehensive support for end-to-end, integration, and unit testing within a single framework, promoting test consistency and reliability.
-
-- **Automatic Waiting:** Cypress automatically waits for elements to be ready, reducing the need for manual wait commands and making tests more stable.
-
-- **Robust Ecosystem:** With a rich plugin ecosystem, Cypress allows easy integration with CI/CD pipelines, reporting tools, and more.
-
-
-
-### Use Cases
-
-- **Web Application Testing:** Perfect for complex UIs and single-page applications (SPAs).
-
-- **API Testing:** This can validate APIs alongside UI tests, providing a holistic testing approach.
-
-- **Cross-Browser Testing:** Support multiple browsers, including Chrome, Firefox, and Edge.
-
-
-
-### Best Practices at INFO
-
-- **Test Early and Often:** Integrate Cypress tests in your development workflow to catch bugs early.
-
-- **Use Data-Driven Testing:** Leverage fixtures and custom commands for reusable and maintainable tests.
-
-- **Continuous Integration:** Run tests in CI pipelines to ensure code quality before production deployment.
-
-
-
-Cypress helps us maintain high standards in software quality, and its adoption continues to grow across our teams.
diff --git a/radar/2023-08-01/react-native.md b/radar/2023-08-01/react-native.md
index f3f1b79..47d5f5f 100644
--- a/radar/2023-08-01/react-native.md
+++ b/radar/2023-08-01/react-native.md
@@ -5,7 +5,7 @@ quadrant: languages-and-frameworks
 featured: true
 ---
 
-[React Native](https://reactnative.dev/) is a popular open-source framework that allows developers to create mobile applications for both iOS and Android using [JavaScript](/languages-and-frameworks/javascript) and [React](/languages-and-frameworks/react). Its central principle is "learn once, write anywhere," enabling a single codebase for both iOS and Android applications.
+[React Native](https://reactnative.dev/) is a popular open-source framework that allows developers to create mobile applications for both iOS and Android using JavaScript and React. Its central principle is "learn once, write anywhere," enabling a single codebase for both iOS and Android applications.
 
 [Expo](https://expo.io/) is a free and open-source toolchain built around React Native. It simplifies the process of building, deploying, and iterating on iOS, Android, and web apps.
 
diff --git a/radar/2023-08-01/vercel.md b/radar/2023-08-01/vercel.md
deleted file mode 100644
index fbbb178..0000000
--- a/radar/2023-08-01/vercel.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Vercel"
-ring: adopt
-quadrant: platforms-and-operations
-featured: true
----
-
-[Vercel](https://vercel.com/) is a leading Platform as a Service ([PaaS](/platforms-and-operations/platform-as-a-service)) provider that specializes in frontend deployment and development, providing an efficient and robust infrastructure for modern web applications.
-
-Vercel is the creator of [Next.js](/languages-and-frameworks/nextjs), a popular [React](/languages-and-frameworks/react) framework that is heavily used in our teams. It provides comprehensive support for many frontend technologies, including but not limited to React, Vue, Angular, and Ember.
-
-One of Vercel's significant strengths is its diverse range of services, which significantly streamline and optimize the development process:
-
-- **Infrastructure**: Includes Edge Network for enhanced performance and reliability, Serverless Functions for running server-side code without managing servers, Edge Functions for executing code closer to the user, Edge Middleware for server-side transformations, Image Optimization for automatic compression and resizing of images, Incremental Static Regeneration for rebuilding static pages after they've been deployed, and Edge Cache for high cache hit-rates.
-
-- **Storage**: Vercel provides comprehensive data storage solutions such as Vercel KV for key-value storage, Vercel Postgres for relational data storage, Vercel Blob for storing and retrieving binary data, and Edge Config for storing application configurations at the edge.
-
-Given its extensive capabilities, we recommend adopting Vercel as a PaaS platform in our projects. Its strong alignment with our frontend development needs, seamless GitHub integration, and robust features make it an excellent choice for our teams.
-
-As with any platform, successful adoption will depend on appropriate implementation and the specific needs of each project. Therefore, proper training and preparation should be prioritized to ensure successful adoption.
diff --git a/radar/2024-01-01/contentful.md b/radar/2024-01-01/contentful.md
deleted file mode 100644
index 2895b5e..0000000
--- a/radar/2024-01-01/contentful.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Contentful CMS"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[Contentful](https://www.contentful.com/) is our preferred headless CMS for managing content across diverse digital platforms. With its robust API-first architecture and user-friendly interface, Contentful streamlines content management and delivery, enabling teams to work efficiently and collaboratively.
-
-### Why Contentful?
-- **Headless Architecture:** Facilitates omnichannel content delivery with a robust set of APIs, ideal for websites, mobile apps, and other digital products.
-- **Developer and Editor Friendly:** Provides easy integration with SDKs for developers and an intuitive UI for content creators, supporting parallel workflows.
-- **Scalability:** Highly scalable for enterprise-level projects, with excellent localization and workflow management capabilities.
-- **Content Modeling:** Enables structured content management, allowing complex and reusable content models that fit various use cases.
-
-### Best Practices at INFO
-- **Adoption Strategy:** Contentful has proven to be a reliable solution, offering our teams the right balance of usability, flexibility, and scalability.
-- **Use Cases:** Used across marketing websites, e-commerce platforms, and complex content-driven applications to manage and deliver content seamlessly.
-
-Contentful’s adoption reinforces our commitment to efficient, scalable, and user-friendly content management solutions at INFO.
diff --git a/radar/2024-01-01/sanity.md b/radar/2024-01-01/sanity.md
deleted file mode 100644
index 1c993d0..0000000
--- a/radar/2024-01-01/sanity.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: "Sanity CMS"
-ring: assess
-quadrant: tools
-featured: true
----
-
-[Sanity](https://www.sanity.io) is a powerful, customizable, headless CMS designed for real-time collaboration and highly structured content management. It offers a unique combination of flexibility, API-driven architecture, and a fully customizable studio.
-
-
-
-### Why Sanity?
-
-- **Customizable Studio:** Fully adaptable to editorial workflows with options for custom input components, plugins, and live previews.
-
-- **Structured Content:** Provides a schema-driven approach that allows for highly structured and reusable content.
-
-- **Real-Time Collaboration:** Enables simultaneous editing and collaboration with version control and history tracking.
-
-- **Scalable API Support:** Strong APIs with [GraphQL](/languages-and-frameworks/graphql) support that are adaptable to complex workflows and integrations.
-
-
-
-### Considerations at INFO
-
-- Sanity is being assessed for projects that require deep customization and collaborative editorial environments, mainly where structured content is crucial.
-
-- **Current Focus:** Evaluating real-time collaboration features, API capabilities, and the flexibility of content modeling.
-
-
-
-Sanity's high degree of customization and collaboration features make it a strong choice as we assess its alignment with our content management needs.
diff --git a/radar/2024-01-01/storyblok.md b/radar/2024-01-01/storyblok.md
deleted file mode 100644
index 24c13c4..0000000
--- a/radar/2024-01-01/storyblok.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Storyblok CMS"
-ring: assess
-quadrant: tools
-featured: true
----
-
-[Storyblok](https://www.storyblok.com/)'s unique blend of visual editing and component-based content management offers a compelling solution for dynamic websites and content-rich applications. Its real-time visual editor and flexible architecture are designed to empower content creators and developers alike.
-
-### Why Storyblok?
-- **Real-Time Visual Editor:** Provides a unique visual editing experience, allowing immediate feedback and adjustments to content.
-- **Component-Based Content Management:** Supports reusable content structures, reducing redundancy and enhancing flexibility.
-- **Robust APIs:** Seamlessly deliver content across multiple platforms, supporting headless setups for modern web applications.
-- **Collaboration Features:** Includes workflows, version control, and multilingual support for managing global content.
-
-### Current Focus at INFO
-- Storyblok is being trialed for its potential to enhance the content creation experience, particularly in dynamic and marketing-oriented projects.
-- **Evaluation Areas:** Integration ease, user experience, and component reusability.
-
-Storyblok's innovative approach to content management positions it as a strong candidate as we trial its capabilities in our workflows.
diff --git a/radar/2024-08-01/sanity.md b/radar/2024-08-01/sanity.md
deleted file mode 100644
index 57449bc..0000000
--- a/radar/2024-08-01/sanity.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Sanity CMS"
-ring: trial
-quadrant: tools
-featured: true
----
-
-[Sanity](https://www.sanity.io) stands out for its customizable studio, real-time collaboration, and schema-driven content management. As we trial its features, Sanity's flexibility and robust API support offer promising solutions for complex editorial workflows.
-
-### Why Sanity?
-- **Highly Customizable Studio:** This studio is Tailored to fit diverse editorial needs, with custom inputs, plugins, and preview features.
-- **Real-Time Collaboration:** Supports simultaneous editing and comprehensive version control, enhancing productivity in content teams.
-- **API and [GraphQL](/languages-and-frameworks/graphql) Support:** Provides flexible content delivery solutions that adapt to varying project requirements.
-- **Structured Content:** Schema-driven approach allows for creating highly organized and reusable content.
-
-### Current Focus at INFO
-- Sanity is being trialed to explore its suitability for projects with complex content requirements, where customization and collaboration are critical.
-- **Evaluation Areas:** Real-time editing, customization capabilities, and structured content management.
-
-Sanity's adaptable and collaborative features make it a strong contender as we explore its potential within our content management ecosystem.
diff --git a/radar/2024-08-01/storyblok.md b/radar/2024-08-01/storyblok.md
deleted file mode 100644
index 5128348..0000000
--- a/radar/2024-08-01/storyblok.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "Storyblok CMS"
-ring: trial
-quadrant: tools
-featured: true
----
-
-[Storyblok](https://www.storyblok.com/)'s unique blend of visual editing and component-based content management offers a compelling solution for dynamic websites and content-rich applications. Its real-time visual editor and flexible architecture are designed to empower content creators and developers alike.
-
-### Why Storyblok?
-- **Real-Time Visual Editor:** Provides a unique visual editing experience, allowing immediate feedback and adjustments to content.
-- **Component-Based Content Management:** Supports reusable content structures, reducing redundancy and enhancing flexibility.
-- **Robust APIs:** Seamlessly deliver content across multiple platforms, supporting headless setups for modern web applications.
-- **Collaboration Features:** Includes workflows, version control, and multilingual support for managing global content.
-
-### Current Focus at INFO
-- Storyblok is being trialed for its potential to enhance the content creation experience, particularly in dynamic and marketing-oriented projects.
-- **Evaluation Areas:** Integration ease, user experience, and component reusability.
-
-Storyblok's innovative approach to content management positions it as a strong candidate as we trial its capabilities in our workflows.
diff --git a/radar/2024-08-01/strapi.md b/radar/2024-08-01/strapi.md
deleted file mode 100644
index c94c8ee..0000000
--- a/radar/2024-08-01/strapi.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: "Strapi CMS"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[Strapi](https://strapi.io/) is our preferred CMS at INFO. It offers an open-source, headless architecture that provides the flexibility and control needed for modern content management. Known for its robust API, ease of customization, and the recent addition of TypeScript support, Strapi enables teams to build and manage content-rich applications efficiently.
-
-### Why Strapi?
-
-- **Open-Source and Headless:** Strapi's open-source nature allows full access to the source code, giving developers complete control over customization and scalability.
-- **Developer-Friendly:** Strapi provides an intuitive admin panel, customizable APIs, and support for both RESTful and GraphQL, making it highly adaptable to various tech stacks.
-- **Extensible Content Models:** Allows easy creation and management of complex content structures with reusable components.
-- **Community and Enterprise Editions:** While the free community edition meets most of our needs, enterprise editions offer additional features such as role-based access control, SSO, and enhanced security for larger projects.
-- **TypeScript Support:** The latest versions of Strapi include TypeScript support, which enhances code quality and developer productivity and makes it easier to build scalable, type-safe applications by moving from JavaScript to TypeScript.
-
-### Use Cases
-
-- **API-Driven Content Delivery:** Ideal for headless setups, delivering content seamlessly to the web, mobile, and other digital platforms.
-- **Custom Content Solutions:** Highly customizable to fit unique business requirements, from simple blogs to complex data-driven applications.
-- **Flexible Integrations:** Strapi integrates well with various databases, front-end frameworks, and other services, enhancing overall development agility.
-
-### Best Practices at INFO
-
-- **Schema Customization:** Leverage Strapi's flexible schema design to create tailored content types that align with project needs.
-- **API Customization:** Utilize Strapi's robust API capabilities to create custom endpoints and extend functionality as required.
-- **Security and Performance:** Update to the latest versions regularly and consider enterprise features for projects with heightened security or performance needs.
-- **TypeScript Adoption:** Strapi's TypeScript support significantly improves maintainability, type safety, and collaboration within development teams when scaling large and complex applications.
-
-Strapi's flexibility, extensibility, recent TypeScript support, and ease of use make it a standout choice for managing and delivering content across various projects at INFO. Its continuous improvements ensure it remains at the forefront of modern content management solutions.
\ No newline at end of file
diff --git a/radar/2024-12-01/axiom.md b/radar/2024-12-01/axiom.md
deleted file mode 100644
index b826912..0000000
--- a/radar/2024-12-01/axiom.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: "Axiom"
-ring: hold
-quadrant: tools
-featured: true
----
-
-[Axiom](https://www.axiom.co) is a centralized logging and monitoring platform designed to simplify application and system-level observability. It was trialed as a solution for all-purpose logging and monitoring, complementing other tools like [Sentry](/tools/sentry), which focuses on frontend error logging.
-
-### Previous Benefits of Axiom
-
-- **All-Purpose Logging:** Provided robust capabilities for both application and system-level logging in a centralized platform.
-- **Ease of Use:** Offered a user-friendly interface and flexible querying capabilities, making it accessible for developers and operations teams.
-- **Comprehensive Monitoring:** Addressed a wide range of use cases, including real-time monitoring, long-term log retention, and advanced analytics.
-
-### Reasons for Holding
-
-- **Established Alternatives:** Tools like Sentry, Datadog, and [Grafana](/tools/grafana) provide more mature and widely adopted solutions for logging and monitoring.
-- **Standardization Goals:** We are focusing on standardizing observability tools with providers that offer comprehensive ecosystems and better integration capabilities.
-- **Feature Overlap:** While Axiom held promise, its feature set overlaps with more established tools, which already fulfill our monitoring and logging requirements.
-
-### Current Stance at INFO
-
-Axiom has been placed on hold as we prioritize Sentry for frontend error logging and Datadog or Grafana for broader monitoring and observability needs. These tools align better with our long-term goals, offer extensive community support, and provide a more unified approach to monitoring and logging across our systems. Existing setups with Axiom will be maintained, but future observability projects will utilize these established alternatives.
diff --git a/radar/2024-12-01/cypress.md b/radar/2024-12-01/cypress.md
deleted file mode 100644
index a43c907..0000000
--- a/radar/2024-12-01/cypress.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: "Cypress"
-ring: hold
-quadrant: tools
-featured: true
----
-
-[Cypress](https://www.cypress.io/) has been a valuable tool for functional testing at INFO, known for its robustness and developer-friendly environment. However, as we prioritize advanced testing capabilities and cross-browser support, Cypress is now on hold while we focus on [Playwright](/tools/playwright) as our preferred solution.
-
-
-
-### Previous Benefits of Cypress
-
-- **Developer Experience:** Provided a smooth setup process, real-time reloading, and direct debugging in the browser, enhancing productivity.
-
-- **End-to-end Testing:** Offered support for end-to-end, integration, and unit testing within a single framework.
-
-- **Automatic Waiting:** Automatically waited for elements to be ready, reducing the need for manual wait commands.
-
-- **Robust Ecosystem:** Had a rich plugin ecosystem for easy integration with CI/CD pipelines and reporting tools.
-
-
-
-### Reasons for Holding
-
-- **Limited Cross-Browser Support:** Cypress has limitations in supporting multiple browsers compared to Playwright's comprehensive coverage.
-
-- **Scaling Challenges:** As testing needs grow, Playwright offers better scalability and performance for large test suites.
-
-- **Advanced Features:** Playwright's advanced capabilities in network interception and browser context isolation provide more robust testing options.
-
-
-
-### Considerations at INFO
-
-- **Transition to Playwright:** Teams are transitioning to Playwright to take advantage of its enhanced features and flexibility.
-
-- **Support and Maintenance:** While on hold, existing Cypress tests will be maintained, but no new tests will be developed using Cypress.
-
-- **Training and Resources:** Resources are being allocated to train teams on Playwright to ensure a smooth transition.
-
-
-
-Cypress played a significant role in our testing strategy, but with Playwright's adoption, we are focusing on tools that better meet our evolving testing requirements.
diff --git a/radar/2024-12-01/digitalocean.md b/radar/2024-12-01/digitalocean.md
deleted file mode 100644
index 8fad260..0000000
--- a/radar/2024-12-01/digitalocean.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "DigitalOcean"
-ring: hold
-quadrant: platforms-and-operations
-featured: true
----
-
-DigitalOcean is a cloud computing platform that offers developers and businesses a straightforward way to deploy, manage, and scale applications of any size. Known for its simplicity and developer-friendly interfaces, DigitalOcean provides a range of services including virtual servers (Droplets), managed databases, and object storage.
-
-### Previous Benefits of DigitalOcean
-
-- **Simplicity and Ease of Use:** Offered an intuitive user experience with straightforward setup processes, making it accessible for small teams and startups.
-- **Cost-Effective Solutions:** Provided affordable pricing models suitable for projects with limited budgets.
-- **Developer Tools:** Included features like one-click apps and pre-configured environments, accelerating development and deployment workflows.
-
-### Reasons for Holding
-
-- **Standardizing Cloud Offerings:** To streamline our cloud infrastructure, we are focusing on mainstream providers like AWS, Azure, and Google Cloud that offer more comprehensive services and better integration capabilities.
-- **Competitive Alternatives:** Platforms like Vercel and Render provide similar simplicity with additional features tailored for modern application deployment.
-- **Lack of Distinct Advantages:** DigitalOcean does not offer significant benefits over competitors that would justify its continued adoption within our technology stack.
-
-### Current Stance at INFO
-
-While DigitalOcean has been valuable for simplifying cloud deployments, we are placing it on hold to concentrate on standardizing our cloud offerings with providers that align better with our long-term strategic goals. We believe this focus will help us maintain consistency, improve scalability, and leverage the extensive feature sets of major cloud platforms. Existing projects on DigitalOcean will be maintained, but future deployments will prioritize platforms that offer more concrete benefits compared to competitors.
-
----
\ No newline at end of file
diff --git a/radar/2024-12-01/event-sourcing.md b/radar/2024-12-01/event-sourcing.md
deleted file mode 100644
index 3d79642..0000000
--- a/radar/2024-12-01/event-sourcing.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: "Event Sourcing"
-ring: trial
-quadrant: methods-and-patterns
-featured: true
----
-
-Event Sourcing is an approach to persistent data management where the primary record is a log of all events that update the system. This log can be replayed to recreate the entire database state at any point in time. Event Sourcing provides significant benefits, including strong auditing, the ability to reconstruct historic states, and the ability to replay events for debugging and analysis.
-
-### Why Event Sourcing?
-
-- **Complete Audit Trail:** Every change to the application state is captured as an immutable event, providing full transparency and traceability.
-- **Historic State Reconstruction:** Enables reconstruction of past states by replaying events, facilitating retroactive adjustments and debugging.
-- **Enhanced Analytics:** Drives greater customer insight by capturing business-meaningful events for advanced analytics.
-- **Event Replay:** Simplifies troubleshooting and debugging by allowing systems to reproduce exact scenarios using event logs.
-
-### Adoption at INFO
-
-- **Trial Phase:** Event Sourcing is currently in the trial phase for projects utilizing [Event-Driven Architectures](event-driven-architecture.html). We aim to validate its practical benefits and scalability across diverse use cases.
-- **Use Cases:** Particularly useful for systems requiring strong auditing, historical state tracking, and complex business workflows.
-- **Complementary Techniques:** Works well with other patterns such as CQRS (Command Query Responsibility Segregation) to optimize query and command operations.
-
-### Considerations
-
-- **Complexity:** Implementing Event Sourcing can increase the complexity of data models and infrastructure.
-- **Storage Requirements:** Event logs require additional storage compared to traditional state-based models.
-- **Operational Overhead:** Requires a robust strategy for event versioning and log replay mechanisms.
-
-### Moving Forward
-
-As we trial Event Sourcing, we are focusing on its potential to enhance auditing, debugging, and analytical capabilities in systems where traditional approaches fall short. Its ability to provide an immutable, comprehensive event log positions it as a powerful tool for modern, data-driven applications.
\ No newline at end of file
diff --git a/radar/2024-12-01/pulumi.md b/radar/2024-12-01/pulumi.md
deleted file mode 100644
index 1aea28d..0000000
--- a/radar/2024-12-01/pulumi.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "Pulumi"
-ring: hold
-quadrant: tools
-featured: true
----
-
-[Pulumi](https://www.pulumi.com) is an open-source [Infrastructure as Code (IaC)](/methods-and-patterns/infrastructure-as-code) tool that enables developers to define and manage cloud infrastructure using familiar programming languages like [TypeScript](/languages-and-frameworks/typescript), [Python](/languages-and-frameworks/python), [Go](/languages-and-frameworks/go), and C#. It bridges the gap between development and operations by allowing code-based infrastructure definitions, promoting reusability and collaboration.
-
-### Previous Benefits of Pulumi
-
-- **Programming Language Support:** Allowed the use of general-purpose programming languages for infrastructure definitions, providing rich abstraction capabilities.
-
-- **Multi-Cloud Compatibility:** Supported all major cloud providers, facilitating a unified approach to managing diverse environments.
-
-- **Enhanced Flexibility:** Offered advanced features like conditional logic and loops, enabling more dynamic infrastructure configurations.
-
-### Reasons for Holding
-
-- **Complexity for Teams:** The use of full-fledged programming languages introduced a steeper learning curve for infrastructure teams accustomed to declarative languages.
-
-- **Ecosystem Maturity:** Compared to [Terraform](/tools/terraform), Pulumi has a smaller community and fewer pre-built modules, affecting the speed of development and issue resolution.
-
-- **Standardization Needs:** To streamline our IaC practices, standardizing on a single tool with broad industry support became a priority.
-
-### Current Stance at INFO
-
-While Pulumi brings innovative approaches to IaC, we are placing it on hold as we shift our focus to Terraform, which better aligns with our standardization and scalability goals. Existing Pulumi projects will be maintained, but future infrastructure developments will prioritize Terraform to leverage its market leadership and extensive ecosystem.
diff --git a/radar/2024-12-01/render.md b/radar/2024-12-01/render.md
deleted file mode 100644
index a61eefa..0000000
--- a/radar/2024-12-01/render.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "Render"
-ring: hold
-quadrant: platforms-and-operations
-featured: true
----
-
-[Render](https://render.com/) is a general-purpose Platform as a Service ([PaaS](/platforms-and-operations/platform-as-a-service)) provider that simplifies cloud deployment by offering an intuitive interface for hosting web applications, databases, and microservices. Initially assessed as a potential alternative for projects where the complexity of AWS is not warranted, Render aimed to provide a cheaper and more flexible solution compared to traditional cloud providers.
-
-### Previous Benefits of Render
-
-- **Ease of Deployment:** Simplified the process of deploying applications with minimal configuration, allowing developers to focus more on code and less on infrastructure.
-- **Cost-Effective Solutions:** Offered competitive pricing models suitable for startups and small to medium-sized projects.
-- **Integrated Features:** Included built-in services like automatic SSL certificates, custom domains, and DDoS protection without additional configuration.
-
-### Reasons for Holding
-
-- **Standardizing Cloud Offerings:** To streamline our cloud infrastructure, we are focusing on mainstream providers like [AWS](/platforms-and-operations/aws), [Azure](/platforms-and-operations/azure), and Google Cloud that offer more comprehensive services and better integration capabilities.
-- **Competitive Alternatives:** Platforms like [Vercel](/platforms-and-operations/vercel) and [DigitalOcean](/platforms-and-operations/digitalocean) provide similar or enhanced features with greater scalability and community support.
-- **Lack of Distinct Advantages:** Render does not offer significant benefits over competitors that would justify its continued adoption within our technology stack.
-
-### Current Stance at INFO
-
-While Render has been valuable for simplifying deployments, we are placing it on hold to concentrate on standardizing our cloud offerings with providers that align better with our long-term strategic goals. We believe this focus will help us maintain consistency, improve scalability, and leverage the extensive feature sets of major cloud platforms. Existing projects on Render will be maintained, but future deployments will prioritize platforms that offer more concrete benefits compared to competitors.
-
----
diff --git a/radar/2024-12-01/snowflake.md b/radar/2024-12-01/snowflake.md
deleted file mode 100644
index abd92b3..0000000
--- a/radar/2024-12-01/snowflake.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: "Snowflake"
-ring: assess
-quadrant: tools
-featured: true
----
-
-[Snowflake](https://www.snowflake.com/en/data-cloud/platform/) is a cloud-based data warehousing platform that offers scalable storage and compute resources for big data processing and analytics. Designed specifically for the cloud, it provides a flexible and efficient solution for data warehousing, data lakes, and data sharing.
-
-
-
-### Why Snowflake?
-
-- **Scalable Architecture:** Separates compute and storage, allowing independent scaling and cost optimization based on workloads.
-
-- **Multi-Cloud Availability:** Operates across major cloud providers like [AWS](/platforms-and-operations/aws), [Azure](/platforms-and-operations/azure), and Google Cloud, offering flexibility and avoiding vendor lock-in.
-
-- **Data Sharing and Collaboration:** Enables secure and instant data sharing within and outside the organization without the need to move or copy data.
-
-- **Performance Optimization:** Automatically manages performance tuning, indexing, and partitioning, reducing administrative overhead.
-
-
-
-### Considerations at INFO
-
-- Snowflake is being assessed for projects that require advanced data warehousing capabilities, seamless scalability, and efficient data sharing mechanisms. We are mainly evaluating it as a competitor vs. Databricks.
-
-
-- **Current Focus:** Evaluating integration with existing data ecosystems, cost-effectiveness, and its ability to support complex analytical queries and workloads.
-
-
-
-Snowflake's cloud-native data platform and robust features position it as a compelling option as we assess its potential to meet our data warehousing and analytics requirements.
diff --git a/radar/2024-12-01/superblocks.md b/radar/2024-12-01/superblocks.md
deleted file mode 100644
index 5cf2c1b..0000000
--- a/radar/2024-12-01/superblocks.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Superblocks"
-ring: assess
-quadrant: platforms-and-operations
-featured: false
----
-
-This blip is currently no longer in trial because we are focussing on other topics.
diff --git a/radar/2024-12-01/terraform.md b/radar/2024-12-01/terraform.md
deleted file mode 100644
index dd42bad..0000000
--- a/radar/2024-12-01/terraform.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: "Terraform"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[Terraform](https://www.terraform.io) is the industry-leading open-source Infrastructure as Code (IaC) tool that allows teams to define and provision infrastructure across multiple cloud providers using a declarative configuration language. At INFO, we have adopted Terraform as our preferred IaC solution due to its maturity, scalability, and extensive community support.
-
-### Why Terraform?
-
-- **Market Leadership:** Terraform is widely recognized as the standard in IaC, offering a stable and reliable platform backed by a vast user community.
-
-- **Declarative Syntax with HCL:** Utilizes HashiCorp Configuration Language (HCL), which is intuitive and easy to learn, making infrastructure definitions clear and maintainable.
-
-- **Extensive Provider Ecosystem:** Supports a broad range of cloud providers and services through official and community providers, enabling seamless multi-cloud deployments.
-
-- **Robust State Management:** Efficiently handles infrastructure state, enabling safe and predictable infrastructure changes with detailed execution plans.
-
-### Focus on OpenTofu
-
-- **Embracing Open-Source Innovation:** With the emergence of [OpenTofu](https://opentofu.org/), the open-source fork of Terraform, we are committed to supporting community-driven advancements in IaC tooling.
-
-- **Vendor Neutrality:** OpenTofu ensures that our infrastructure remains free from vendor lock-in, aligning with our principles of openness and flexibility.
-
-- **Future-Proofing Infrastructure:** By keeping an eye on OpenTofu's developments, we aim to leverage its innovations while maintaining compatibility with existing Terraform configurations.
-
-### Adoption at INFO
-
-- **Standardization Across Teams:** Adopting Terraform allows us to unify our IaC practices, improving collaboration and reducing complexity.
-
-- **Scalability and Performance:** Terraform's ability to manage complex infrastructures makes it suitable for projects of any size, ensuring reliability as we scale.
-
-- **Community and Support:** The extensive Terraform community provides a wealth of modules, best practices, and support resources, accelerating development and problem-solving.
-
-### Moving Forward
-
-Terraform's position as the market leader in IaC tools, combined with its robust features and strong community backing, makes it the ideal choice for our infrastructure needs. We will continue to invest in Terraform while actively exploring OpenTofu to stay at the forefront of IaC innovation.
diff --git a/radar/2025-01-22/react-testing-library.md b/radar/2025-01-22/react-testing-library.md
deleted file mode 100644
index 9116540..0000000
--- a/radar/2025-01-22/react-testing-library.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "React testing library"
-ring: adopt
-quadrant: tools
-featured: true
----
-
-[React Testing Library](https://testing-library.com/) is a testing utility that encourages best practices by focusing on testing components from the user's perspective. It is designed to work with React applications and provides a simple API for querying and interacting with the DOM.
-
-### Why React Testing Library?
-
-- **User-Centric Testing:** Emphasizes testing the behavior of components as users would interact with them, leading to more reliable and maintainable tests.
-
-- **Simplicity:** Offers a straightforward API that reduces the complexity of writing tests, making it easier for developers to adopt and use.
-
-- **Integration with Vitest:** Works seamlessly with [Vitest](/tools/vitest/), a popular [JavaScript](/languages-and-frameworks/javascript) testing framework, providing a robust environment for writing and running tests.
-
-### Considerations at INFO
-
-- React Testing Library has a strong community and is widely adopted in the [React](/languages-and-frameworks/react) ecosystem, providing access to a wealth of resources, plugins, and community support.
-
-- Promotes best practices in testing by discouraging reliance on implementation details and encouraging tests that reflect actual user behavior.
-
-- **Current Focus:** Leveraging its ease of use and the positive impact on test reliability and maintainability.
-
-React Testing Library's emphasis on user-centric testing and its simplicity make it a valuable tool as we adopt it to enhance our front-end testing practices.
diff --git a/radar/2026-04-23/european-sovereign-cloud.md b/radar/2026-04-23/european-sovereign-cloud.md
index 90e0c82..bd966ce 100644
--- a/radar/2026-04-23/european-sovereign-cloud.md
+++ b/radar/2026-04-23/european-sovereign-cloud.md
@@ -31,7 +31,7 @@ When evaluating a European sovereign cloud provider, the following criteria are
 
 - **Comprehensive Service Catalogue:** Beyond compute and storage, look for managed databases, object storage, load balancers, DNS, backup services, VPN/networking, and monitoring.
 
-- **Infrastructure as Code Compatibility:** First-class support for [Terraform](/tools/terraform) / [OpenTofu](https://opentofu.org/) providers is essential for automation and reproducibility.
+- **Infrastructure as Code Compatibility:** First-class support for Terraform / [OpenTofu](https://opentofu.org/) providers is essential for automation and reproducibility.
 
 - **Cost Transparency & Competitiveness:** Transparent, predictable pricing without hidden fees. Evaluate compute, storage, egress, and managed services costs against each other and hyperscaler equivalents. Pricing models vary significantly between providers and should be compared per use case.