code · pull · Apr 20, 2026 · Apr 20, 2026 · Apr 20, 2026
diff --git a/docs-mintlify/admin/ai/agent-rules.mdx b/docs-mintlify/admin/ai/agent-rules.mdx
@@ -18,15 +18,15 @@ Agent Rules in Cube provide a powerful way to customize and control how AI agent
 - Domain-specific terminology
 
 **Example Always Rules:**
-```
+```text
 Sales efficiency is deal size divided by sales cycle length
 ```
 
-```
+```text
 When analyzing customer data, always consider seasonality patterns from our retail business
 ```
 
-```
+```text
 Revenue should be calculated using our standard GAAP accounting principles
 ```
 
@@ -41,15 +41,15 @@ Revenue should be calculated using our standard GAAP accounting principles
 - Scenario-specific instructions
 
 **Example Agent Requested Rules:**
-```
+```text
 If you asked to analyze sales efficiency start with correlation to WSE
 ```
 
-```
+```text
 For customer segmentation analysis, use RFM methodology (Recency, Frequency, Monetary)
 ```
 
-```
+```text
 When analyzing marketing performance, compare against industry benchmarks where available
 ```
 
@@ -77,13 +77,13 @@ When analyzing marketing performance, compare against industry benchmarks where
 ### Domain-Specific Rules
 
 **E-commerce Example:**
-```
+```text
 Always Rule: "Customer lifetime value equals average order value × purchase frequency × customer lifespan"
 Agent Requested: "For cart abandonment analysis, segment by device type and traffic source"
 ```
 
 **SaaS Example:**
-```
+```text
 Always Rule: "MRR growth rate should exclude one-time charges and setup fees"
 Agent Requested: "When analyzing churn, differentiate between voluntary and involuntary churn"
 ```
@@ -92,7 +92,7 @@ Agent Requested: "When analyzing churn, differentiate between voluntary and invo
 
 Rules should provide context that agents might not inherently understand about your business:
 
-```
+```text
 Always Rule: "Our peak season is Q4, with 40% of annual revenue typically occurring in December"
 Agent Requested: "For inventory analysis, consider our 6-week lead time for international suppliers"
 ```
@@ -111,23 +111,23 @@ Based on the rule configuration system, when multiple rules could apply to the s
 ### Example Conflict Scenarios
 
 **Scenario 1: Direct Contradiction**
-```
+```text
 Rule A (Always): "Revenue recognition follows monthly billing cycles"
 Rule B (Always): "Revenue should be recognized quarterly"
 
 Resolution: The agent will flag this conflict and may ask for clarification
 ```
 
 **Scenario 2: Complementary Rules**
-```
+```text
 Rule A (Always): "Sales efficiency is deal size divided by sales cycle length"
 Rule B (Agent Requested): "When analyzing sales efficiency, include pipeline velocity metrics"
 
 Resolution: Both rules work together - B provides additional context to A
 ```
 
 **Scenario 3: Specificity Override**
-```
+```text
 Rule A (Always): "Use standard deviation for all variance calculations"
 Rule B (Agent Requested): "For customer behavior analysis, use median absolute deviation instead of standard deviation"
 

diff --git a/docs-mintlify/admin/ai/spaces-agents-models.mdx b/docs-mintlify/admin/ai/spaces-agents-models.mdx
@@ -73,7 +73,7 @@ Cube is an agentic analytics platform that combines AI agents with semantic data
 
 ### Example Interaction:
 
-```
+```text
 User: "Show me sales performance by region for Q4"
 
 Agent:
@@ -86,7 +86,7 @@ Agent:
 
 ### Space-Agent-Model Relationship:
 
-```
+```text
 Space (Sales Analytics)
 ├── Rules: "Revenue = quantity × price"
 ├── Memories: Past Q4 analyses

diff --git a/docs-mintlify/admin/ai/yaml-config.mdx b/docs-mintlify/admin/ai/yaml-config.mdx
@@ -64,7 +64,7 @@ When YAML agent configuration is enabled, an `auto` space and `auto` agent are a
 
 ### File Structure
 
-```
+```text
 your-cube-project/
 ├── model/
 │   └── cubes/

diff --git a/docs-mintlify/admin/connect-to-data/data-sources/ms-fabric.mdx b/docs-mintlify/admin/connect-to-data/data-sources/ms-fabric.mdx
@@ -27,7 +27,7 @@ Then, provide the **JDBC URL** connection string in the following
 format. See below for tips on filling in `<SERVER_NAME>`, `<DATABASE_NAME>`,
 `<AUTH_TYPE>`, `<USER_NAME>`, and `<PASSWORD>`.
 
-```
+```text
 jdbc:sqlserver://;serverName=<SERVER_NAME>.datawarehouse.pbidedicated.windows.net;database=<DATABASE_NAME>;encrypt=true;Authentication=<AUTH_TYPE>;UserName=<USER_NAME>;Password=<PASSWORD>
 ```
 

diff --git a/docs-mintlify/admin/connect-to-data/data-sources/snowflake.mdx b/docs-mintlify/admin/connect-to-data/data-sources/snowflake.mdx
@@ -12,7 +12,7 @@ description: "Snowflake is a popular cloud-based data platform."
 In order to connect Cube to Snowflake, you need to grant certain permissions to the Snowflake role
 used by Cube. Cube requires the role to have `USAGE` on databases and schemas
 and `SELECT` on tables. An example configuration:
-```
+```sql
 GRANT USAGE ON DATABASE ABC TO ROLE XYZ;
 GRANT USAGE ON ALL SCHEMAS IN DATABASE ABC TO ROLE XYZ;
 GRANT USAGE ON FUTURE SCHEMAS IN DATABASE ABC TO ROLE XYZ;

diff --git a/docs-mintlify/admin/connect-to-data/multitenancy.mdx b/docs-mintlify/admin/connect-to-data/multitenancy.mdx
@@ -40,7 +40,7 @@ See the following recipes:
 
 </Note>
 
-### Multitenancy vs Multiple Data Sources
+## Multitenancy vs Multiple Data Sources
 
 In cases where your Cube data model is spread across multiple different data
 sources, consider using the [`data_source` cube property][ref-cube-datasource]

diff --git a/docs-mintlify/admin/connect-to-data/visualization-tools/index.mdx b/docs-mintlify/admin/connect-to-data/visualization-tools/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Connecting to Visualization Tools
 description: Find connection guides for BI and visualization tools that integrate with Cube.
 ---
 

diff --git a/docs-mintlify/admin/deployment/byoc/index.mdx b/docs-mintlify/admin/deployment/byoc/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Bring Your Own Cloud (BYOC)
 description: Deploy Cube Cloud data-plane components on your own AWS, Azure, or GCP infrastructure for full data residency control.
 ---
 

diff --git a/docs-mintlify/admin/deployment/providers/index.mdx b/docs-mintlify/admin/deployment/providers/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Cloud Providers
 description: Learn about AWS, GCP, and Azure support in Cube Cloud, including available regions and dedicated infrastructure.
 ---
 

diff --git a/docs-mintlify/admin/deployment/vpc/aws/index.mdx b/docs-mintlify/admin/deployment/vpc/aws/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: AWS VPC Connectivity
 description: Establish a private network connection between Cube Cloud and your AWS VPC using PrivateLink or VPC peering.
 ---
 

diff --git a/docs-mintlify/admin/deployment/vpc/azure/index.mdx b/docs-mintlify/admin/deployment/vpc/azure/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Azure VNet Connectivity
 description: Establish a private network connection between Cube Cloud and your Azure VNet using Private Link or VNet peering.
 ---
 

diff --git a/docs-mintlify/admin/monitoring/monitoring-integrations/s3.mdx b/docs-mintlify/admin/monitoring/monitoring-integrations/s3.mdx
@@ -54,7 +54,7 @@ navigate to your S3 bucket and watch the logs coming.
 
 You might see the following error message in Vector logs:
 
-```
+```text
 The bucket you are attempting to access must be addressed using the specified
 endpoint. Please send all future requests to this endpoint.
 ```

diff --git a/docs-mintlify/admin/sso/microsoft-entra-id/index.mdx b/docs-mintlify/admin/sso/microsoft-entra-id/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Microsoft Entra ID SSO
 description: Set up single sign-on for Cube Cloud using Microsoft Entra ID with SAML authentication and SCIM provisioning.
 ---
 

diff --git a/docs-mintlify/cube-core/getting-started/index.mdx b/docs-mintlify/cube-core/getting-started/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Getting Started with Cube Core
 description: Create a project, connect a database, query data, and add a pre-aggregation in self-hosted Cube Core.
 ---
 

diff --git a/docs-mintlify/cube-core/migrate-from-core/index.mdx b/docs-mintlify/cube-core/migrate-from-core/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Migrate from Cube Core to Cube Cloud
 description: Import your self-hosted Cube Core project into Cube Cloud using Git, SSH, or the CLI.
 ---
 
diff --git a/docs-mintlify/cube-core/running-in-production.mdx b/docs-mintlify/cube-core/running-in-production.mdx
@@ -328,7 +328,7 @@ system to report the creation time of a file.
 If the file system does not support getting the creation time, you will see the
 following error message in Cube Store logs:
 
-```
+```text
 ERROR [cubestore::remotefs::cleanup] <pid:1>
 error while getting created time for file "<name>.chunk.parquet":
 creation time is not available for the filesystem
@@ -377,7 +377,7 @@ for Cube Store via the **Encryption Keys** page in Cube Cloud.
 
 When building some pre-aggregations, you might encounter the following error:
 
-```
+```text
 Error: Error during create table: CREATE TABLE <REDACTED>
 Error: Query execution timeout after 10 min of waiting
 ```
@@ -402,7 +402,7 @@ However, it is recommended that you optimize your pre-aggregations instead:
 
 When using MinIO for persistent storage, you might encounter the following error:
 
-```
+```text
 Error: Error during upload of <REDACTED>
 File <REDACTED> can't be listed after upload.
 Either there's Cube Store cluster misconfiguration,

diff --git a/docs-mintlify/docs.json b/docs-mintlify/docs.json
@@ -53,11 +53,46 @@
                 "pages": [
                   "docs/explore-analyze/workbooks/querying-data",
                   "docs/explore-analyze/workbooks/calculated-fields",
-                  "docs/explore-analyze/workbooks/source-sql-tabs",
-                  "docs/explore-analyze/workbooks/charts"
+                  "docs/explore-analyze/workbooks/source-sql-tabs"
                 ]
               },
               "docs/explore-analyze/explore",
+              {
+                "group": "Charts",
+                "root": "docs/explore-analyze/charts/index",
+                "pages": [
+                  {
+                    "group": "Chart types",
+                    "root": "docs/explore-analyze/charts/chart-types/index",
+                    "pages": [
+                      "docs/explore-analyze/charts/chart-types/bar",
+                      "docs/explore-analyze/charts/chart-types/line",
+                      "docs/explore-analyze/charts/chart-types/area",
+                      "docs/explore-analyze/charts/chart-types/scatter",
+                      "docs/explore-analyze/charts/chart-types/pie",
+                      "docs/explore-analyze/charts/chart-types/heatmap",
+                      "docs/explore-analyze/charts/chart-types/boxplot",
+                      "docs/explore-analyze/charts/chart-types/table",
+                      "docs/explore-analyze/charts/chart-types/kpi",
+                      "docs/explore-analyze/charts/chart-types/map",
+                      "docs/explore-analyze/charts/chart-types/html"
+                    ]
+                  },
+                  "docs/explore-analyze/charts/custom",
+              {
+                    "group": "Configure charts",
+                    "root": "docs/explore-analyze/charts/configuration/index",
+                    "pages": [
+                      "docs/explore-analyze/charts/configuration/series-mapping",
+                      "docs/explore-analyze/charts/configuration/series-configuration",
+                      "docs/explore-analyze/charts/configuration/color-and-stacking",
+                      "docs/explore-analyze/charts/configuration/axes",
+                      "docs/explore-analyze/charts/configuration/tooltips",
+                      "docs/explore-analyze/charts/configuration/data-labels"
+                    ]
+                  }
+                ]
+              },
               "docs/explore-analyze/analytics-chat"
             ]
           },
@@ -623,6 +658,13 @@
       "href": "https://cubecloud.dev/auth/signup"
     }
   },
+  "seo": {
+    "indexing": "all",
+    "metatags": {
+      "og:type": "website",
+      "og:site_name": "Cube Documentation"
+    }
+  },
   "footer": {
     "socials": {
       "x": "https://x.com/the_cube_dev",

diff --git a/docs-mintlify/docs/data-modeling/access-control/index.mdx b/docs-mintlify/docs/data-modeling/access-control/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Access Control
 sidebarTitle: Overview
 description: Learn how Cube separates authentication and authorization to control who can access your data and platform features.
 ---

diff --git a/docs-mintlify/docs/data-modeling/dynamic/index.mdx b/docs-mintlify/docs/data-modeling/dynamic/index.mdx
@@ -1,4 +1,5 @@
 ---
+title: Dynamic Data Models
 description: Generate data models programmatically using Jinja with Python or JavaScript for dynamic schema creation.
 ---
 

diff --git a/docs-mintlify/docs/explore-analyze/charts/chart-types/area.mdx b/docs-mintlify/docs/explore-analyze/charts/chart-types/area.mdx
@@ -0,0 +1,38 @@
+---
+title: Area
+description: Show volume or part-to-whole trends over time with a filled region beneath the line.
+---
+
+Area charts add a filled region beneath the line. The fill communicates magnitude and cumulative volume, making area charts especially effective for stacked part-to-whole breakdowns over time.
+
+## Variants
+
+### Stacked
+
+Each series is stacked on top of the previous one. The top edge shows the cumulative total; each filled band shows the individual contribution. Use this for part-to-whole breakdowns over time (e.g. revenue by product category over months).
+
+{/* Screenshot: stacked area chart — total sale price by month, split by product category (4–5 stacked bands). Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
+
+### Percentage stacked (Stack %)
+
+Each series is normalized to 100% at every X-axis value, showing proportional contribution over time. Use when relative share matters more than absolute volume.
+
+{/* Screenshot: percentage stacked area chart — same data normalized to 100%. Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
+
+### Overlaid
+
+All series share the same baseline. Use only when series are clearly separated in value and you want to compare trajectories rather than totals — with many series, fills will occlude each other.
+
+{/* Screenshot: overlaid area chart — two series, clearly separated in value. Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
+
+## Stacking
+
+Set stacking behavior in the **Color & stacking** section of the Style tab. The **Stack**, **Stack %**, and **Overlay** options are the relevant modes for area charts.
+
+{/* Screenshot: stacking dropdown in the Style tab. Place inline, 50% width, right-aligned. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
+
+See [Color & stacking](/docs/explore-analyze/charts/configuration/color-and-stacking) for palette options and stacked segment sorting.
+
+## Axis behavior
+
+Area charts use a temporal X axis for time dimensions — continuous and time-aware. For non-time fields, the axis is ordinal.
-Original file line number
+Diff line change
@@ Expand Up @@
     format. See below for tips on filling in `<SERVER_NAME>`, `<DATABASE_NAME>`,
     `<AUTH_TYPE>`, `<USER_NAME>`, and `<PASSWORD>`.
-    ```
+    ```text
     jdbc:sqlserver://;serverName=<SERVER_NAME>.datawarehouse.pbidedicated.windows.net;database=<DATABASE_NAME>;encrypt=true;Authentication=<AUTH_TYPE>;UserName=<USER_NAME>;Password=<PASSWORD>
     ```
@@ Expand Down @@