fix: deprecating catalog

docs/architecture/building-dapps.md

@@ -9,17 +9,7 @@ Nevermined provides a list of features that allow to build rich use cases around
 
 Nevermined ships different [technical components](building-blocks.md) to make that happen, but in most of the cases the builders of applications are interested in delivering nice use cases without knowing all the low level details of the architecture.
 
-To facilitate the utilization of Nevermined and the orchestration of all the different components, we provide the following components:
-
-* The [Nevermined SDK](../nevermined-sdk/intro)
-* The [Nevermined React Components](../react-components/intro)
-
-
-:::info Which one to use
-
-If you are building a **React application** our recommendation is to use the [Nevermined React Components](../react-components/intro), but if not to use the [Nevermined SDK](../nevermined-sdk/intro).
-
-:::
+To facilitate the utilization of Nevermined and the orchestration of all the different components, we provide the [Nevermined SDK](../nevermined-sdk/intro).
 
 From a developer point of view, the integration of Nevermined is quite straight forward. The usage of the Catalog or the SDK with the usage of any of the existing [Nevermined public environments](../environments/) facilitate the easy development of Decentralized Applications leveraging the Nevermined features.
 
@@ -40,10 +30,6 @@ Nevermined provides the following core features that can be used to build differ
 
 The existence of these features allow application developers to build use cases touching one or many of the above. The best way to do that is using any of the existing libraries provided.
 
-### Nevermined React Components
-
-The [Nevermined React Components](../react-components/intro) is also a **NPM** library of packaged Nevermined functionalities making easier to add web3 capabilities to any existing **React application**. The Catalog uses the SDK under the hood.
-
 ### Nevermined SDK
 
 The [Nevermined SDK](../nevermined-sdk/intro) is a **NPM** library of packaged Nevermined functionalities allowing to use all the existing functionalities in any kind of **web or stand-alone** application.

docs/getting-started/users.md

@@ -13,9 +13,6 @@ The desire to share data across silos and geographic boundaries is not new for d
 
 So any team, organization or individual that sees Data and AI as economic assets, with incentives, IP rights,... can benefit from using Nevermined. 
 
-Currently, Nevermined is geared towards developers and is available in two ways, for different development approaches. 
-
-- If you want to use a low-level library, you can use our [SDK](../nevermined-sdk/intro)
-- For apps made in React, we have functionalities available as [React Components](../react-components/intro).
+Currently, Nevermined is geared towards developers and is available via our [SDK](../nevermined-sdk/intro).
 
 We’re also working on packaging our components in SaaS-solutions.

docs/nevermined-sdk/example.md

@@ -4,10 +4,6 @@ sidebar_position: 3
 
 # How to use the SDK?
 
-## Before to start
-
-If you project is using `React` we recommend to use [Catalog](../react-components/intro.md) to make everything much easier, SDK is the low level of it.
-
 ## Requirements
 
 Before you start with this demo you require:

docs/nevermined-sdk/intro.md

@@ -6,10 +6,6 @@ sidebar_position: 1
 
 The Nevermined SDK is a low level library which functions as an intermediate between the client and the different backend services like [Marketplace API](../architecture/marketplace-api/index.md), [Node](../architecture/node/index.md), [Smart Contracts](../architecture/contracts/index.md), etc...
 
-# When should I use the Nevermined SDK?
-
-You should use Nevermined SDK if your project isn't developed using [React](https://reactjs.org/). If you do use React, we recommend to use [Nevermined React Components](../react-components/intro.md). As we mentioned before, the **SDK** is a low level library and **Catalog** makes developing dApps in React easier.  
-
 import DocCardList from '@site/src/components/docCard/docCardList';
 
 <DocCardList />