docs: admonitions right usage (#11063)

* docs: update caution to latest admonition syntax

* docs: update note to latest admonition syntax

* docs: update warning to latest admonition syntax

* docs: update tip to latest admonition syntax

* docs: update info to latest admonition syntax

* docs: update contribution docs to latest admonition syntax

Author: srini047

docs-website/CONTRIBUTING.md

@@ -163,24 +163,19 @@ Link to it: `[Install](./page.mdx#install-guide)` or `[Install](/docs/overview/q
 Use Docusaurus admonitions sparingly for supporting information:
 
 ```mdx
-:::note
-General notes or important information to highlight.
+:::note[General notes or important information to highlight.]
 :::
 
-:::tip
-Short tip that helps the reader succeed.
+:::tip[Short tip that helps the reader succeed.]
 :::
 
-:::info
-Useful but non-blocking background information.
+:::info[Useful but non-blocking background information.]
 :::
 
-:::warning
-Risky settings or potential pitfalls.
+:::warning[Risky settings or potential pitfalls.]
 :::
 
-:::danger
-Data loss or security-impacting issues.
+:::danger[Data loss or security-impacting issues.]
 :::
 ```
 

docs-website/docs/concepts/components/custom-components.mdx

@@ -19,7 +19,7 @@ Here are the requirements for all custom components:
 - `run()`: This is a required method in every component. It accepts input arguments and returns a `dict`. The inputs can either come from the pipeline when it’s executed, or from the output of another component when connected using `connect()`. The `run()` method should be compatible with the input/output definitions declared for the component. See an [Extended Example](#extended-example) below to check how it works.
 
 
-:::note Avoid in-place input mutation
+:::note[Avoid in-place input mutation]
 
 When building custom components, do not change the component's inputs directly. Instead, work on a copy or a new version of the input, modify that, and return it. The reason for this is that the original input values might be reused by other components or by later pipeline steps. Mutating the input directly can lead to unintended side effects and bugs in the pipeline, as other components might rely on the original input values.
 

docs-website/docs/concepts/device-management.mdx

@@ -24,7 +24,7 @@ Haystack’s device management is built on the following abstractions:
 
 With the above abstractions, Haystack can fully address any supported device that’s part of your local machine and can support the usage of multiple devices at the same time. Every component that supports local inference will internally handle the conversion of these generic representations to their backend-specific representations.
 
-:::info Source Code
+:::info[Source Code]
 
 Find the full code for the abstractions above in the Haystack GitHub [repo](https://github.com/deepset-ai/haystack/blob/6a776e672fb69cc4ee42df9039066200f1baf24e/haystack/utils/device.py).
 :::

docs-website/docs/concepts/document-store.mdx

@@ -11,12 +11,12 @@ You can think of the Document Store as a database that stores your data and prov
 
 Document Store is an object that stores your documents. In Haystack, a Document Store is different from a component, as it doesn't have the `run()` method. You can think of it as an interface to your database – you put the information there, or you can look through it. This means that a Document Store is not a piece of a pipeline but rather a tool that the components of a pipeline have access to and can interact with.
 
-:::tip Work with Retrievers
+:::tip[Work with Retrievers]
 
 The most common way to use a Document Store in Haystack is to fetch documents using a Retriever. A Document Store will often have a corresponding Retriever to get the most out of specific technologies. See more information in our [Retriever](../pipeline-components/retrievers.mdx) documentation.
 :::
 
-:::note How to choose a Document Store?
+:::note[How to choose a Document Store?]
 
 To learn about different types of Document Stores and their strengths and disadvantages, head to the [Choosing a Document Store](document-store/choosing-a-document-store.mdx) page.
 :::
@@ -65,7 +65,7 @@ document_store.write_documents(
 )
 ```
 
-:::note `DocumentWriter`
+:::note[`DocumentWriter`]
 
 See `DocumentWriter` component [docs](../pipeline-components/writers/documentwriter.mdx) to write your documents into a Document Store in a pipeline.
 :::

docs-website/docs/concepts/document-store/choosing-a-document-store.mdx

@@ -60,7 +60,7 @@ Continue further down the article for a more complex explanation of the strength
 
 Vector libraries are often included in the “vector database” category improperly, as they are limited to handling only vectors, are designed to work in-memory, and normally don’t have a clean way to store data on disk. Still, they are the way to go every time performance and speed are the top requirements for your AI application, as these libraries can use hardware resources very effectively.
 
-:::warning In progress
+:::warning[In progress]
 
 We are currently developing the support for vector libraries in Haystack.
 :::

docs-website/docs/concepts/pipelines.mdx

@@ -115,7 +115,7 @@ Thanks to serialization, you can save and then load your pipelines. Serializatio
 
 Haystack pipelines delegate the serialization to its components, so serializing a pipeline simply means serializing each component in the pipeline one after the other, along with their connections. The pipeline is serialized into a dictionary format, which acts as an intermediate format that you can then convert into the final format you want.
 
-:::info Serialization formats
+:::info[Serialization formats]
 
 Haystack only supports YAML format at this time. We'll be rolling out more formats gradually.
 :::

docs-website/docs/concepts/pipelines/serialization.mdx

@@ -130,7 +130,7 @@ restored = component_from_dict(Greeter, data, "my_greeter")
 assert restored.message == greeter.message
 ```
 
-:::caution Init parameters must be stored as instance attributes
+:::caution[Init parameters must be stored as instance attributes]
 
 Default serialization only works when there is a **1:1 mapping** between init parameter names and instance attributes. For every argument in `__init__`, the component must assign it to an attribute with the same name. For example, if you have `def __init__(self, prompt: str)`, you must have `self.prompt = prompt` in the class. Otherwise the serialization logic can't find the value to serialize and raises an error or uses the default value if the parameter has one.
 :::

docs-website/docs/concepts/pipelines/visualizing-pipelines.mdx

@@ -13,7 +13,7 @@ You can visualize your pipelines as graphs to better understand how the componen
 
 Haystack pipelines have  `draw()` and `show()` methods that enable you to visualize the pipeline as a graph using Mermaid graphs.
 
-:::note Data Privacy Notice
+:::note[Data Privacy Notice]
 
 Exercise caution with sensitive data when using pipeline visualization.
 

docs-website/docs/development/deployment.mdx

@@ -25,7 +25,7 @@ Here are the currently available guides on Haystack pipeline deployment:
 
 Haystack can be easily integrated into any HTTP application, but if you don’t have one, you can use Hayhooks, a ready-made application that serves Haystack pipelines as REST endpoints. We’ll be using Hayhooks throughout this guide to streamline the code examples. Refer to the Hayhooks [overview](hayhooks.mdx) for a quick start, or the [official Hayhooks documentation](https://deepset-ai.github.io/hayhooks/) for comprehensive guides and reference.
 
-:::note Looking to scale with confidence?
+:::note[Looking to scale with confidence?]
 
 If your team needs **enterprise-grade support, best practices, and deployment guidance** to run Haystack in production, check out **Haystack Enterprise Starter**.
 

docs-website/docs/development/hayhooks.mdx

@@ -9,7 +9,7 @@ description: "Hayhooks is a web application you can use to serve Haystack pipeli
 
 Hayhooks is a web application you can use to serve Haystack pipelines through HTTP endpoints. This page provides an overview of the main features of Hayhooks.
 
-:::info Hayhooks Documentation
+:::info[Hayhooks Documentation]
 
 For comprehensive documentation, including detailed configuration reference, advanced features,
 and examples, see the [official Hayhooks documentation](https://deepset-ai.github.io/hayhooks/).