docs: refresh JUICE module docs

Author: Vonng

content/docs/juice/_index.md

@@ -1,65 +1,77 @@
 ---
 title: "Module: JUICE"
 weight: 4500
-description: JuiceFS distributed filesystem using PostgreSQL as metadata engine, with PITR-capable shared storage.
+description: Use JuiceFS distributed filesystem with PostgreSQL metadata to provide shared POSIX storage.
 icon: fas fa-folder-tree
 module: [JUICE]
 categories: [Reference]
 ---
 
-[JuiceFS](https://juicefs.com/) is a high-performance POSIX-compatible distributed filesystem that can use PostgreSQL as its metadata engine.
+[JuiceFS](https://juicefs.com/) is a high-performance POSIX-compatible distributed filesystem that can mount object storage or databases as a local filesystem.
 
-Pigsty's JUICE module provides complete JuiceFS deployment and management, with multi-instance support, automated installation, monitoring integration, and filesystem PITR via PostgreSQL backup recovery.
+The `JUICE` module depends on [`NODE`](/docs/node) for infrastructure and package repo, and typically uses [`PGSQL`](/docs/pgsql) as the metadata engine.
+Data storage can be PostgreSQL or [`MINIO`](/docs/minio) / S3 object storage. Monitoring relies on [`INFRA`](/docs/infra) VictoriaMetrics.
 
+```mermaid
+flowchart LR
+    subgraph Client["App/User"]
+        app["POSIX Access"]
+    end
 
---------
-
-## Features
+    subgraph JUICE["JUICE"]
+        jfs["JuiceFS Mount"]
+    end
 
-- **PostgreSQL Metadata Engine**: Uses PostgreSQL for filesystem metadata storage, with HA and PITR capability
-- **Flexible Data Storage**: Supports PostgreSQL Large Object, MinIO, S3 and other storage backends
-- **Multi-Instance Support**: Single node can mount multiple independent JuiceFS filesystems
-- **PITR Capability**: Leverage PostgreSQL backup recovery for filesystem point-in-time recovery
-- **Monitoring Integration**: Auto-integrated with VictoriaMetrics monitoring system
+    subgraph PGSQL["PGSQL"]
+        meta["Metadata DB"]
+    end
 
+    subgraph Object["Object Storage (optional)"]
+        s3["S3 / MinIO"]
+    end
 
---------
-
-## Config Example
+    subgraph INFRA["INFRA (optional)"]
+        vm["VictoriaMetrics"]
+    end
 
-Typical JuiceFS configuration using PostgreSQL as metadata and data storage:
+    app --> jfs
+    jfs --> meta
+    jfs -.-> s3
+    jfs -->|/metrics| vm
 
-```yaml
-juice_instances:
-  jfs:
-    path  : /fs
-    meta  : postgres://dbuser_meta:DBUser.Meta@10.10.10.10:5432/meta
-    data  : --storage postgres --bucket 10.10.10.10:5432/meta --access-key dbuser_meta --secret-key DBUser.Meta
-    port  : 9567
+    style JUICE fill:#5B9CD5,stroke:#4178a8,color:#fff
+    style PGSQL fill:#3E668F,stroke:#2d4a66,color:#fff
+    style Object fill:#FCDB72,stroke:#d4b85e,color:#333
+    style INFRA fill:#999,stroke:#666,color:#fff
 ```
 
-
 --------
 
-## Use Cases
-
-JUICE module is suitable for:
-
-- **AI Coding Sandbox**: Persistent storage for Code-Server, JupyterLab
-- **Shared Storage**: Multi-node mount same filesystem for file sharing
-- **Data Lake Storage**: Large capacity storage for data analysis, ML tasks
-- **Backup Archive**: Low-cost data archiving using object storage backends
+## Features
 
+- **PostgreSQL metadata**: Metadata stored in PostgreSQL for easy management and backup
+- **Multi-instance**: One node can mount multiple independent filesystem instances
+- **Multiple data backends**: PostgreSQL, MinIO, S3, and more
+- **Monitoring integration**: Each instance exposes Prometheus / Victoria metrics port
+- **Simple config**: Describe instances with the [**`juice_instances`**](/docs/juice/param#juice_instances) dict
 
 --------
 
-## Documentation
+## Quick Start
 
-- [**Configuration**](config): Configure JuiceFS instances, storage backends and mount options
-- [**Parameters**](param): JUICE module parameter reference
-- [**Playbook**](playbook): Deployment and management playbook guide
-- [**Administration**](admin): JuiceFS management SOPs, including scaling, PITR recovery
-- [**Monitoring**](monitor): JuiceFS metrics and Grafana dashboards
-- [**FAQ**](faq): Common questions about JUICE module
+Minimal config example (single instance):
 
+```yaml
+juice_instances:
+  jfs:
+    path: /fs
+    meta: postgres://dbuser_meta:DBUser.Meta@10.10.10.10:5432/meta
+    data: --storage postgres --bucket 10.10.10.10:5432/meta --access-key dbuser_meta --secret-key DBUser.Meta
+    port: 9567
+```
 
+Deploy:
+
+```bash
+./juice.yml -l <host>
+```