Using FileTree component and minor fixes

Author: Oxyjun

src/content/docs/autorag/configuration/metadata-filtering.mdx

@@ -5,6 +5,8 @@ sidebar:
   order: 6
 ---
 
+import { FileTree } from "~/components"
+
 Metadata filtering narrows down search results based on metadata, so only relevant content is retrieved. The filter narrows down results prior to retrieval, so that you only query the scope of documents that matter.
 
 Here is an example of metadata filtering using [Workers Binding](/autorag/usage/workers-binding/) but it can be easily adapted to use the [REST API](/autorag/usage/rest-api/) instead.
@@ -96,12 +98,16 @@ Note the following limitations with the compound operators:
 You can use "starts with" filtering on the `folder` metadata attribute to search for all files and subfolders within a specific path.
 
 For example, consider this file structure:
-```
-customer-a/profile.md
-customer-a/contracts/property/contract-1.pdf
-```
 
-If you were to filter using an `eq` (equals) operator with `value: "customer-a/"`, it would only match files directly within that folder, like `profile.md`. It wouldn't include files in subfolders like `customer-a/contracts/`.
+<FileTree>
+- customer-a
+  - profile.md
+  - contracts
+    - property
+      - contract-1.pdf
+</FileTree>
+
+If you were to filter using an `eq` (equals) operator with `value: "customer-a/"`, it would only match files directly within that folder, like `profile.md`. It would not include files in subfolders like `customer-a/contracts/`.
 
 To recursively filter for all items starting with the path `customer-a/`, you can use the following compound filter:
 
@@ -117,7 +123,7 @@ filters: {
       {
         type: "lte",
         key: "folder",
-        value: "customer-a/z", 
+        value: "customer-a/z",
       },
     ],
   },
@@ -126,8 +132,8 @@ filters: {
 This filter identifies paths starting with `customer-a/` by using:
 
 - The `and` condition to combine the effects of the `gt` and `lte` conditions.
-- The `gt` condition to include pathes greater than the `/` ASCII character.
-- The `lte` condition to include pathes less than and including the lower case `z` ASCII character.
+- The `gt` condition to include paths greater than the `/` ASCII character.
+- The `lte` condition to include paths less than and including the lower case `z` ASCII character.
 
 Together, these conditions effectively select paths that begin with the provided path value.
 

src/content/docs/autorag/how-to/multitenancy.mdx

@@ -5,6 +5,8 @@ sidebar:
   order: 5
 ---
 
+import { FileTree } from "~/components"
+
 AutoRAG supports multitenancy by letting you segment content by tenant, so each user, customer, or workspace can only access their own data. This is typically done by organizing documents into per-tenant folders and applying [metadata filters](/autorag/configuration/metadata-filtering/) at query time.
 
 ## 1. Organize Content by Tenant
@@ -13,11 +15,13 @@ When uploading files to R2, structure your content by tenant using unique folder
 
 Example folder structure:
 
-```bash
-customer-a/logs/
-customer-a/contracts/
-customer-b/contracts/
-```
+<FileTree>
+- customer-a
+  - logs/
+  - contracts/
+- customer-b
+  - contracts/
+</FileTree>
 
 When indexing, AutoRAG will automatically store the folder path as metadata under the `folder` attribute. It is recommended to enforce folder separation during upload or indexing to prevent accidental data access across tenants.
 
@@ -44,10 +48,13 @@ To filter across multiple folders, or to add date-based filtering, you can use a
 
 While an `eq` filter targets files at the specific folder, you'll often want to retrieve all documents belonging to a tenant regardless if there are files in its subfolders. For example, all files in `customer-a/` with a structure like:
 
-```
-customer-a/profile.md
-customer-a/contracts/property/contract-1.pdf
-```
+<FileTree>
+- customer-a
+  - profile.md
+  - contracts
+    - property
+      - contract-1.pdf
+</FileTree>
 
 To achieve this [starts with](/autorag/configuration/metadata-filtering/#starts-with-filter-for-folders) behavior, use a compound filter like:
 
@@ -63,7 +70,7 @@ filters: {
       {
         type: "lte",
         key: "folder",
-        value: "customer-a/z", 
+        value: "customer-a/z",
       },
     ],
   },
@@ -72,7 +79,7 @@ filters: {
 This filter identifies paths starting with `customer-a/` by using:
 
 - The `and` condition to combine the effects of the `gt` and `lte` conditions.
-- The `gt` condition to include pathes greater than the `/` ASCII character.
-- The `lte` condition to include pathes less than and including the lower case `z` ASCII character.
+- The `gt` condition to include paths greater than the `/` ASCII character.
+- The `lte` condition to include paths less than and including the lower case `z` ASCII character.
 
-With this filter you would capture both files `profile.md` and `contract-1.pdf`.
+This filter captures both files `profile.md` and `contract-1.pdf`.