Removed "This documentation describes NeMo Retriever Library" from files

docs/docs/extraction/agentic-retrieval-concept.md

@@ -1,10 +1,5 @@
 # Agentic retrieval (concept)
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Agentic retrieval means **iterative, tool-driven** retrieval: an agent plans steps, issues searches, may refine filters, and optionally reranks until it has enough context to answer.
 
 NeMo Retriever Library focuses on document ingestion, embeddings, vector stores, hybrid search, and reranking. Orchestration frameworks call these building blocks from your application.

docs/docs/extraction/benchmarking.md

@@ -1,10 +1,5 @@
 # NeMo Retriever Library integration testing framework
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 A configurable, dataset-agnostic testing framework for end-to-end validation of NeMo Retriever Library pipelines. This framework uses structured YAML configuration for type safety, validation, and parameter management.
 
 ## Dataset Prerequisites

docs/docs/extraction/choose-your-path.md

@@ -1,10 +1,5 @@
 # Choose your path
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Use this page to pick documentation and deployment options that match your goal.
 
 ## I want to run locally or embed the library

docs/docs/extraction/chunking.md

@@ -1,10 +1,5 @@
 # Split Documents
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Splitting, also known as chunking, breaks large documents or text into smaller, manageable sections to improve retrieval efficiency. 
 After chunking, only the most relevant pieces of information are retrieved for a given query. 
 Chunking also prevents text from exceeding the context window of the embedding model.

docs/docs/extraction/cli-reference.md

@@ -1,10 +1,5 @@
 # CLI Reference
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 After you install the Python dependencies, you can use the [NeMo Retriever Library](overview.md) command line interface (CLI).
 To use the CLI, use the `nemo-retriever` command.
 

docs/docs/extraction/concepts.md

@@ -1,10 +1,5 @@
 # Concepts
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 These terms appear throughout NeMo Retriever Library documentation.
 
 ## Job
@@ -26,6 +21,7 @@ Optionally, the library can compute **embeddings** for extracted content and sto
 ## Deployment modes
 
 - **Library mode** — Run without the full container stack where appropriate ([quickstart](quickstart-library-mode.md)).
+- **Docker Compose (self-hosted)** — [Container stack quickstart](quickstart-guide.md) for running the full microservices pipeline locally.
 - **Helm / Kubernetes** — [Helm-based deployment](https://github.com/NVIDIA/NeMo-Retriever/blob/main/helm/README.md) for cluster operations.
 - **Notebooks** — [Jupyter examples](notebooks.md) for experimentation and RAG demos.
 

docs/docs/extraction/content-metadata.md

@@ -8,11 +8,6 @@ The definitions used in this documentation are the following:
 
 Metadata can be extracted from a source or content, or generated by using models, heuristics, or other methods.
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 
 ## Source File Metadata
 

docs/docs/extraction/contributing.md

@@ -1,9 +1,148 @@
 # Contributing to NeMo Retriever Library
 
-!!! note
+External contributions will be welcome soon, and they are greatly appreciated. For repository policy, coding standards, and the contribution process, refer to **[Contributing to NeMo Retriever](https://github.com/NVIDIA/NeMo-Retriever/blob/main/CONTRIBUTING.md)** on GitHub.
 
-    This documentation describes NeMo Retriever Library.
+The sections below describe how to configure your machine and Git remotes so you can work on documentation (or code) against **[NVIDIA/NeMo-Retriever](https://github.com/NVIDIA/NeMo-Retriever)** using a fork and a separate publishing clone.
 
+---
 
-External contributions will be welcome soon, and they are greatly appreciated! 
-For more information, refer to [Contributing to NeMo Retriever](https://github.com/NVIDIA/NeMo-Retriever/blob/main/CONTRIBUTING.md).
+## Set up your writing and development environment
+
+### SSH authentication (one time for each computer)
+
+1. **Create an SSH key** on your computer. Follow steps 1–3 in [Generating a new SSH key and adding it to the ssh-agent](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). (You only need the key-generation steps; you can skip configuring ssh-agent if your organization prefers not to use it.)
+
+2. **Add the public key to GitHub** using [Adding a new SSH key to your GitHub account](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account).
+
+### Commit signing for GitHub (one time for each computer)
+
+1. **Create a GPG key** following [Generating a new GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key).
+
+2. **Tell Git which key to use:**
+
+    ```bash
+    git config --global user.signingkey YOUR_KEY_ID
+    ```
+
+3. **Sign every commit by default (recommended if your org requires signed commits):**
+
+    ```bash
+    git config --global commit.gpgsign true
+    ```
+
+4. **Optional — sign a single commit:**
+
+    ```bash
+    git commit -S -m "your message"
+    ```
+
+    or
+
+    ```bash
+    git commit --gpg-sign -m "your message"
+    ```
+
+5. **Optional — skip signing for one commit:**
+
+    ```bash
+    git commit --no-gpg-sign -m "Unsigned commit"
+    ```
+
+---
+
+## Set up your writing and development clone (fork)
+
+You do day-to-day work in a clone of **your fork**, with `upstream` pointing at NVIDIA’s repo.
+
+1. **Get access** to **[https://github.com/NVIDIA/NeMo-Retriever](https://github.com/NVIDIA/NeMo-Retriever)** (and permission to fork it, per your organization).
+
+2. **Create a fork**
+
+    - Open the **Fork** menu, then choose **Create a new fork**.
+    - Accept the default repository name (`NeMo-Retriever`) unless your org requires another name.
+    - **Deselect** “Copy the main branch only” if you need other branches locally; you can recover later with `git fetch upstream --tags` (see below).
+    - Click **Create fork**.
+
+3. **Clone the fork** onto your machine:
+
+    - Pick a parent folder, for example `C:\_work\NeMo-Retriever-fork` or `C:\_repositories\NeMo-Retriever-fork`.
+    - Open a terminal in that folder, then clone:
+
+        ```bash
+        git clone git@github.com:<your-github-username>/NeMo-Retriever.git
+        ```
+
+    - Enter the repository directory (default folder name is usually `NeMo-Retriever`):
+
+        ```bash
+        cd NeMo-Retriever
+        ```
+
+    - **Add NVIDIA’s repo as `upstream`:**
+
+        ```bash
+        git remote add upstream https://github.com/NVIDIA/NeMo-Retriever.git
+        ```
+
+    - If the fork was created with **only** the default branch, fetch the rest from upstream when needed:
+
+        ```bash
+        git fetch upstream --tags
+        ```
+
+Confirm remotes:
+
+```bash
+git remote -v
+```
+
+You should see `origin` pointing at your fork and `upstream` at `NVIDIA/NeMo-Retriever`.
+
+---
+
+## Set up your publishing clone (canonical repo)
+
+Some workflows use a **second clone** of the **official** repository (not your fork) for publishing or internal automation.
+
+1. Choose a **different** directory from your fork clone. On Windows, your team may require this clone inside **WSL**; follow internal guidance.
+
+2. Clone NVIDIA’s repository:
+
+    ```bash
+    git clone git@github.com:NVIDIA/NeMo-Retriever.git
+    ```
+
+After setup you typically have **two** working copies: one from your fork (with `upstream` configured) and one straight from `NVIDIA/NeMo-Retriever`.
+
+---
+
+## Make a documentation change
+
+### Target branches
+
+Decide where the change lands:
+
+- **`main` only**
+- A **release** branch only (for example `release/25.9.0`)
+- **Both** `main` and a release branch — commit to `main` first, then [cherry-pick](https://git-scm.com/docs/git-cherry-pick) the commits onto the release branch.
+
+### Keep your fork and local clone in sync with NVIDIA
+
+From your **fork** clone, on each branch you care about (example uses `main`; substitute `develop` or a release branch as needed):
+
+```bash
+git checkout main
+git fetch upstream
+git merge upstream/main
+git push origin main
+```
+
+Use a **space** between the remote name and the branch: `git push origin main`. (`git push origin/main` is invalid and Git will report an error.)
+
+Repeat `checkout` / `fetch` / `merge` / `push` for every branch you maintain (`main`, `develop`, release branches, and so on).
+
+---
+
+## Related
+
+- [Contributing to NeMo Retriever](https://github.com/NVIDIA/NeMo-Retriever/blob/main/CONTRIBUTING.md) — authoritative contribution guidelines in the repository

docs/docs/extraction/custom-metadata.md

@@ -1,10 +1,5 @@
 # Use Custom Metadata to Filter Search Results
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 You can upload custom metadata for documents during ingestion. 
 By uploading custom metadata you can attach additional information to documents, 
 and use it for filtering results during retrieval operations. 

docs/docs/extraction/data-store.md

@@ -2,10 +2,6 @@
 
 Use this documentation to learn how [NeMo Retriever Library](overview.md) handles and uploads data.
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
 
 ## Overview
 

docs/docs/extraction/embedding-nims-models.md

@@ -1,10 +1,5 @@
 # Embedding NIMs and models
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Embeddings turn extracted text and multimodal content into vectors for semantic search. NeMo Retriever Library integrates with NVIDIA NIM microservices for embedding. Model names and compatibility vary by release; refer to the [Support matrix](support-matrix.md) and the [NVIDIA NIM catalog](https://build.nvidia.com/).
 
 For multimodal or VLM embeddings, refer to [Multimodal embeddings (VLM)](vlm-embed.md).

docs/docs/extraction/environment-config.md

@@ -3,10 +3,6 @@
 The following are the environment variables that you can use to configure [NeMo Retriever Library](overview.md).
 You can specify these in your .env file or directly in your environment.
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
 
 ## General Environment Variables
 

docs/docs/extraction/evaluate-on-your-data.md

@@ -1,10 +1,5 @@
 # Evaluate on your data
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Retrieval and ingestion performance **depend on your documents**, hardware, and pipeline settings. Use the following when measuring quality and throughput on **your** datasets.
 
 ## Benchmarking and baselines

docs/docs/extraction/extraction-charts-infographics.md

@@ -1,10 +1,5 @@
 # Charts and infographics
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Charts and infographic regions are classified as graphic elements and processed with the corresponding NVIDIA NIM workflows (for example, **yolox-graphic-elements** in current releases). Outputs use the same metadata schema as other extracted objects.
 
 **Related**

docs/docs/extraction/extraction-ocr-scanned.md

@@ -1,10 +1,5 @@
 # OCR and scanned documents
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Scanned PDFs and image-only pages rely on OCR and hybrid paths that combine native text extraction with OCR when needed. For extract methods such as `ocr` and `pdfium_hybrid`, refer to the [Python API reference](python-api-reference.md).
 
 **Related**

docs/docs/extraction/extraction-tables.md

@@ -1,10 +1,5 @@
 # Tables
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 NeMo Retriever Library detects tables as structured page elements, processes them through the appropriate NIMs, and exports formats suitable for downstream RAG (including Markdown-oriented representations where configured). Availability depends on pipeline and model configuration; refer to the [Support matrix](support-matrix.md).
 
 **Related**

docs/docs/extraction/faq.md

@@ -2,11 +2,6 @@
 
 This documentation contains the Frequently Asked Questions (FAQ) for [NeMo Retriever Library](overview.md).
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 
 ## What if I already have a retrieval pipeline? Can I just use NeMo Retriever Library? 
 

docs/docs/extraction/getting-started-about.md

@@ -1,10 +1,5 @@
 # About getting started
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 This section walks you from **access and prerequisites** through **first deployment** and **hands-on notebooks**.
 
 Typical order:
@@ -13,6 +8,7 @@ Typical order:
 2. Confirm [Prerequisites](prerequisites.md) and the [Support matrix](support-matrix.md) for your OS, GPU, and software stack.
 3. Deploy using one of:
     - [Library mode](quickstart-library-mode.md) (without full stack containers where appropriate)
+    - [Docker Compose (self-hosted)](quickstart-guide.md) for the reference microservices stack in containers
     - [Helm chart](https://github.com/NVIDIA/NeMo-Retriever/blob/main/helm/README.md) for Kubernetes environments
 4. Explore [Jupyter Notebooks](notebooks.md) for end-to-end examples.
 

docs/docs/extraction/hosted-nims-when-to-use.md

@@ -1,10 +1,5 @@
 # When to use NVIDIA-hosted NIMs
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 [NVIDIA-hosted NIMs](https://build.nvidia.com/) run inference on NVIDIA-managed infrastructure. You call models with API keys (refer to [Get your API key](ngc-api-key.md)) without operating GPU nodes yourself.
 
 Consider hosted NIMs when:

docs/docs/extraction/how-to-use-this-documentation.md

@@ -1,10 +1,5 @@
 # How to use this documentation
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Use the sections below as a reading order that matches how you run NeMo Retriever Library.
 
 ## NeMo Retriever Library (local or embedded)

docs/docs/extraction/image-captioning.md

@@ -1,10 +1,5 @@
 # Image captioning
 
-!!! note
-
-    This documentation describes NeMo Retriever Library.
-
-
 Image captioning generates natural-language descriptions for unstructured image content. Retrieval can then use text embeddings over captions and visual embeddings where you configure them.
 
 **Related**