docs: update docs from notion (#2684)

Co-authored-by: lucaseduoli <lucaseduoli@users.noreply.github.com>

docs/docs/Components/components-custom-components.md

@@ -6,16 +6,16 @@ slug: /components-custom-components
 
 
 
-Langflow components can be created from within the platform, allowing users to extend the platform's functionality using Python code. They encapsulate are designed to be independent units, reusable across different workflows.
+Langflow components can be created from within the platform, allowing users to extend the platform's functionality using Python code. They encapsulate are designed to be independent units, reusable across different workflows. 
 
 
-These components can be easily connected within a language model pipeline, adding freedom and flexibility to what can be included in between user and AI messages.
+These components can be easily connected within a language model pipeline, adding freedom and flexibility to what can be included in between user and AI messages. 
 
 
 ![](./238089171.png)
 
 
-Since Langflow operates with Python behind the scenes, you can implement any Python function within a Custom Component. This means you can leverage the power of libraries such as Pandas, Scikit-learn, Numpy, and thousands of packages to create components that handle data processing in unlimited ways.
+Since Langflow operates with Python behind the scenes, you can implement any Python function within a Custom Component. This means you can leverage the power of libraries such as Pandas, Scikit-learn, Numpy, and thousands of packages to create components that handle data processing in unlimited ways. 
 
 
 Custom Components are not just about extending functionality; they also streamline the development process. By creating reusable and configurable components, you can enhance the capabilities of Langflow, making it a powerful tool for developing complex workflows.

docs/docs/Components/components-data.md

@@ -6,6 +6,15 @@ slug: /components-data
 
 
 
+:::info
+
+This page may contain outdated information. It will be updated as soon as possible.
+
+:::
+
+
+
+
 ## API Request {#23da589293f74016a1f70d6d7c0fdc55}
 
 

docs/docs/Components/components-embedding-models.md

@@ -6,6 +6,15 @@ slug: /components-embedding-models
 
 
 
+:::info
+
+This page may contain outdated information. It will be updated as soon as possible.
+
+:::
+
+
+
+
 ## Amazon Bedrock Embeddings {#4ddcfde8c1664e358d3f16d718e944d8}
 
 

docs/docs/Components/components-helpers.md

@@ -6,6 +6,15 @@ slug: /components-helpers
 
 
 
+:::info
+
+This page may contain outdated information. It will be updated as soon as possible.
+
+:::
+
+
+
+
 ## Chat memory {#304dc4a3bea74efb9068093ff18a56ad}
 
 

docs/docs/Components/components-io.md

@@ -30,9 +30,6 @@ You can find out more about Chat Input and other Inputs [here](/components-io).
 ### Chat Input {#2a5f02262f364f8fb75bcfa246e7bb26}
 
 
----
-
-
 This component collects user input from the chat.
 
 
@@ -43,11 +40,14 @@ This component collects user input from the chat.
 - **Message:** Specifies the message text. It is a multiline text input.
 - **Session ID:** Specifies the session ID of the chat history. If provided, the message will be saved in the Message History.
 
-NOTE
-
+:::note
 
 If `As Data` is `true` and the `Message` is a `Data`, the data of the `Data` will be updated with the `Sender`, `Sender Name`, and `Session ID`.
 
+:::
+
+
+
 
 One significant capability of the Chat Input component is its ability to transform the Playground into a chat window. This feature is particularly valuable for scenarios requiring user input to initiate or influence the flow.
 
@@ -55,9 +55,6 @@ One significant capability of the Chat Input component is its ability to transfo
 ### Text Input {#260aef3726834896b496b56cdefb6d4a}
 
 
----
-
-
 The **Text Input** component adds an **Input** field on the Playground. This enables you to define parameters while running and testing your flow.
 
 
@@ -99,9 +96,6 @@ You can find out more about it and the other Outputs [here](/components-io).
 ### Chat Output {#1edd49b72781432ea29d70acbda4e7e7}
 
 
----
-
-
 This component sends a message to the chat.
 
 
@@ -112,18 +106,18 @@ This component sends a message to the chat.
 - **Session ID:** Specifies the session ID of the chat history. If provided, messages are saved in the Message History.
 - **Message:** Specifies the text of the message.
 
-NOTE
-
+:::note
 
 If `As Data` is `true` and the `Message` is a `Data`, the data in the `Data` is updated with the `Sender`, `Sender Name`, and `Session ID`.
 
+:::
+
+
+
 
 ### Text Output {#b607000bc0c5402db0433c1a7d734d01}
 
 
----
-
-
 This component displays text data to the user. It is useful when you want to show text without sending it to the chat.
 
 

docs/docs/Components/components-models.md

@@ -6,6 +6,15 @@ slug: /components-models
 
 
 
+:::info
+
+This page may contain outdated information. It will be updated as soon as possible.
+
+:::
+
+
+
+
 ## Amazon Bedrock {#3b8ceacef3424234814f95895a25bf43}
 
 

docs/docs/Components/components-prompts.md

@@ -6,6 +6,15 @@ slug: /components-prompts
 
 
 
+:::info
+
+This page may contain outdated information. It will be updated as soon as possible.
+
+:::
+
+
+
+
 A prompt is the input provided to a language model, consisting of multiple components and can be parameterized using prompt templates. A prompt template offers a reproducible method for generating prompts, enabling easy customization through input variables.
 
 
@@ -25,6 +34,6 @@ This component creates a prompt template with dynamic variables. This is useful
 The `PromptTemplate` component enables users to create prompts and define variables that control how the model is instructed. Users can input a set of variables which the template uses to generate the prompt when a conversation starts.
 
 
-After defining a variable in the prompt template, it acts as its own component input.
+After defining a variable in the prompt template, it acts as its own component input. 
 
 - **template:** The template used to format an individual request.

docs/docs/Components/components-vector-stores.md

@@ -6,6 +6,15 @@ slug: /components-vector-stores
 
 
 
+:::info
+
+This page may contain outdated information. It will be updated as soon as possible.
+
+:::
+
+
+
+
 ### Astra DB {#453bcf5664154e37a920f1b602bd39da}
 
 
@@ -298,11 +307,14 @@ Ensure the PostgreSQL server is accessible and configured correctly.
 - **Search Kwargs:** Additional search parameters.
 - **Pool Threads:** Number of threads.
 
-NOTE
-
+:::info
 
 Ensure the Pinecone API key and environment are correctly configured.
 
+:::
+
+
+
 
 ---
 
@@ -381,11 +393,14 @@ Ensure the Pinecone API key and environment are correctly configured.
 For detailed documentation, refer to the [Redis Documentation](https://python.langchain.com/docs/integrations/vectorstores/redis).
 
 
-NOTE
-
+:::info
 
 Ensure the Redis server URL and index name are configured correctly. Provide a schema if no documents are available.
 
+:::
+
+
+
 
 ---
 
@@ -425,11 +440,14 @@ Ensure the Redis server URL and index name are configured correctly. Provide a s
 - **Supabase URL:** Instance URL.
 - **Table Name:** Optional table name.
 
-NOTE
-
+:::info
 
 Ensure the Supabase service key, URL, and table name are properly configured.
 
+:::
+
+
+
 
 ---
 
@@ -471,11 +489,14 @@ Ensure the Supabase service key, URL, and table name are properly configured.
 For more information, consult the [Vectara Component Documentation](https://python.langchain.com/docs/integrations/vectorstores/vectara).
 
 
-NOTE
-
+:::info
 
 If inputs or files_url are provided, they will be processed accordingly.
 
+:::
+
+
+
 
 ---
 

docs/docs/Components/components.md

@@ -9,6 +9,9 @@ slug: /components
 ## Component {#0323a728d8314767adb907b998036bb4}
 
 
+---
+
+
 A component is a single building block within a flow. It consists of inputs, outputs, and parameters that define their functionality. These elements provide a convenient and  straightforward way to compose LLM-based applications. Learn more about components and how they work below.