diff --git a/docs/app/[lang]/docs/[[...slug]]/page.tsx b/docs/app/[lang]/docs/[[...slug]]/page.tsx
index d269af72cb..62cf86f97a 100644
--- a/docs/app/[lang]/docs/[[...slug]]/page.tsx
+++ b/docs/app/[lang]/docs/[[...slug]]/page.tsx
@@ -7,9 +7,29 @@ import {
   DocsDescription,
 } from 'fumadocs-ui/page';
 import defaultMdxComponents from 'fumadocs-ui/mdx';
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
+import { Step, Steps } from 'fumadocs-ui/components/steps';
+import { Callout } from 'fumadocs-ui/components/callout';
+import { Card, Cards } from 'fumadocs-ui/components/card';
+import { ImageZoom } from 'fumadocs-ui/components/image-zoom';
+import { Accordion, Accordions } from 'fumadocs-ui/components/accordion';
 import type { MDXContent } from 'mdx/types';
 import type { TOCItemType } from 'fumadocs-core/toc';
 
+const mdxComponents = {
+  ...defaultMdxComponents,
+  Tab,
+  Tabs,
+  Step,
+  Steps,
+  Callout,
+  Card,
+  Cards,
+  ImageZoom,
+  Accordion,
+  Accordions,
+};
+
 export default async function Page({
   params,
 }: {
@@ -29,7 +49,7 @@ export default async function Page({
       <DocsTitle>{page.data.title}</DocsTitle>
       <DocsDescription>{page.data.description}</DocsDescription>
       <DocsBody>
-        <MDX components={{ ...defaultMdxComponents }} />
+        <MDX components={mdxComponents} />
       </DocsBody>
     </DocsPage>
   );
diff --git a/docs/app/[lang]/page.tsx b/docs/app/[lang]/page.tsx
index 7e6abcdf6d..4056bfff97 100644
--- a/docs/app/[lang]/page.tsx
+++ b/docs/app/[lang]/page.tsx
@@ -1,10 +1,372 @@
-import { redirect } from 'next/navigation';
+import Link from 'next/link';
+import {
+  Database,
+  Zap,
+  Shield,
+  Bot,
+  ArrowRight,
+  GitCompare,
+  Table,
+  Search,
+  FileCode,
+  Import,
+  Network,
+  Terminal,
+} from 'lucide-react';
 
-export default async function LangPage({
+const stats = {
+  en: [
+    { value: '15 MB', label: 'Install Size' },
+    { value: '25+', label: 'Databases' },
+    { value: 'Desktop + Docker', label: 'Deployment' },
+    { value: 'Built-in AI', label: 'Assistant' },
+  ],
+  cn: [
+    { value: '15 MB', label: '安装体积' },
+    { value: '25+', label: '支持数据库' },
+    { value: '桌面 + Docker', label: '部署方式' },
+    { value: '内置 AI', label: '智能助手' },
+  ],
+};
+
+const features = {
+  en: [
+    {
+      icon: Terminal,
+      title: 'Query Editor',
+      desc: 'CodeMirror 6-powered SQL editor with syntax highlighting, smart autocomplete, and query history.',
+      href: '/en/docs/query-editor',
+    },
+    {
+      icon: Table,
+      title: 'Data Grid',
+      desc: 'Browse and edit data with virtual scrolling. Inline editing with SQL preview before saving.',
+      href: '/en/docs/data-grid',
+    },
+    {
+      icon: Search,
+      title: 'Schema Browser',
+      desc: 'Tree view with search, pin, context menus, and column comments. Color-coded connections.',
+      href: '/en/docs/schema-browser',
+    },
+    {
+      icon: GitCompare,
+      title: 'Schema Diff & Sync',
+      desc: 'Compare schemas across databases and generate sync SQL. Dev vs Production in one click.',
+      href: '/en/docs/schema-diff',
+    },
+    {
+      icon: Bot,
+      title: 'AI Assistant + MCP',
+      desc: 'Natural language to SQL, query optimization, error fixing. Let Claude/Cursor query your databases via MCP.',
+      href: '/en/docs/ai-assistant',
+    },
+    {
+      icon: Import,
+      title: 'Data Transfer',
+      desc: 'Move data across database engines — MySQL to PostgreSQL, SQLite to SQL Server, and more.',
+      href: '/en/docs/data-transfer',
+    },
+    {
+      icon: Network,
+      title: 'Field Lineage',
+      desc: 'Trace column relationships across foreign keys, views, and query history with confidence levels.',
+      href: '/en/docs/field-lineage',
+    },
+    {
+      icon: FileCode,
+      title: 'Import & Export',
+      desc: 'Import CSV/JSON/Excel, export SQL dumps, run .sql files with smart statement splitting.',
+      href: '/en/docs/table-import',
+    },
+  ],
+  cn: [
+    {
+      icon: Terminal,
+      title: '查询编辑器',
+      desc: '基于 CodeMirror 6 的 SQL 编辑器，支持语法高亮、智能补全、JOIN 建议和查询历史。',
+      href: '/cn/docs/query-editor',
+    },
+    {
+      icon: Table,
+      title: '数据表格',
+      desc: '虚拟滚动浏览大数据量。行内编辑，保存前可预览将要执行的 SQL 语句。',
+      href: '/cn/docs/data-grid',
+    },
+    {
+      icon: Search,
+      title: '结构浏览',
+      desc: '树形视图，支持搜索、置顶、右键菜单、字段注释显示和连接颜色标记。',
+      href: '/cn/docs/schema-browser',
+    },
+    {
+      icon: GitCompare,
+      title: 'Schema 对比与同步',
+      desc: '跨数据库结构对比，自动生成同步 SQL。开发环境 vs 生产环境，一键搞定。',
+      href: '/cn/docs/schema-diff',
+    },
+    {
+      icon: Bot,
+      title: 'AI 助手 + MCP',
+      desc: '自然语言转 SQL、查询优化、错误修复。通过 MCP 让 Claude/Cursor 直接查询你的数据库。',
+      href: '/cn/docs/ai-assistant',
+    },
+    {
+      icon: Import,
+      title: '数据传输',
+      desc: '跨引擎数据迁移 — MySQL 到 PostgreSQL、SQLite 到 SQL Server，自动处理类型映射。',
+      href: '/cn/docs/data-transfer',
+    },
+    {
+      icon: Network,
+      title: '字段血缘',
+      desc: '追踪外键、视图、查询历史中的字段关联关系，标注置信度，数据治理必备。',
+      href: '/cn/docs/field-lineage',
+    },
+    {
+      icon: FileCode,
+      title: '导入与导出',
+      desc: '导入 CSV/JSON/Excel，导出 SQL 文件，执行 .sql 脚本，智能语句分割。',
+      href: '/cn/docs/table-import',
+    },
+  ],
+};
+
+const databases = [
+  'MySQL', 'PostgreSQL', 'SQLite', 'Redis', 'MongoDB',
+  'DuckDB', 'ClickHouse', 'SQL Server', 'Oracle', 'Elasticsearch',
+  'MariaDB', 'TiDB', 'OceanBase', 'CockroachDB', 'StarRocks',
+  'Doris', 'DM', 'GaussDB', 'Redshift', 'TDengine',
+];
+
+const comparison = {
+  en: {
+    title: 'Why DBX?',
+    headers: ['', 'DBX', 'DBeaver', 'Navicat', 'TablePlus'],
+    rows: [
+      ['Install Size', '~15 MB', '~300 MB', '~200 MB', '~80 MB'],
+      ['Price', 'Free (AGPL)', 'Free / $230', '$180+', '$99+'],
+      ['Database Support', '25+', '80+', '15+', '20+'],
+      ['Built-in AI', 'Yes', 'No', 'Yes', 'No'],
+      ['MCP Integration', 'Yes', 'No', 'No', 'No'],
+      ['Docker Self-Host', 'Yes', 'No', 'No', 'No'],
+      ['Field Lineage', 'Yes', 'No', 'No', 'No'],
+    ],
+  },
+  cn: {
+    title: '为什么选择 DBX？',
+    headers: ['', 'DBX', 'DBeaver', 'Navicat', 'TablePlus'],
+    rows: [
+      ['安装体积', '~15 MB', '~300 MB', '~200 MB', '~80 MB'],
+      ['价格', '免费 (AGPL)', '免费 / $230', '$180+', '$99+'],
+      ['数据库支持', '25+', '80+', '15+', '20+'],
+      ['内置 AI', '有', '无', '有', '无'],
+      ['MCP 集成', '有', '无', '无', '无'],
+      ['Docker 自托管', '有', '无', '无', '无'],
+      ['字段血缘', '有', '无', '无', '无'],
+    ],
+  },
+};
+
+const i18nText = {
+  en: {
+    heroTitle: '25+ Databases.',
+    heroTitle2: 'One 15 MB App.',
+    heroSubtitle: 'Open-source database management tool with built-in AI assistant. Desktop & Docker self-hosting, powered by Tauri 2 and Rust.',
+    ctaDownload: 'Download',
+    ctaDocs: 'Read the Docs',
+    featuresTitle: 'Everything You Need',
+    featuresSubtitle: 'A complete toolkit for database management, from daily queries to cross-engine migration.',
+    dbTitle: 'Supported Databases',
+    dbSubtitle: 'Native Rust drivers, no JDBC. MySQL/PostgreSQL compatible databases work out of the box.',
+    andMore: 'and more...',
+    footerCta: 'Ready to try?',
+    footerCtaSub: 'Download DBX or deploy with Docker in seconds.',
+  },
+  cn: {
+    heroTitle: '25+ 数据库',
+    heroTitle2: '一个 15 MB 的应用',
+    heroSubtitle: '开源数据库管理工具，内置 AI 助手。桌面应用 + Docker 自托管，基于 Tauri 2 和 Rust 构建。',
+    ctaDownload: '下载',
+    ctaDocs: '查看文档',
+    featuresTitle: '功能一览',
+    featuresSubtitle: '从日常查询到跨引擎迁移，一站式数据库管理工具。',
+    dbTitle: '支持的数据库',
+    dbSubtitle: 'Rust 原生驱动，无 JDBC。MySQL / PostgreSQL 兼容数据库开箱即用。',
+    andMore: '更多...',
+    footerCta: '准备好了吗？',
+    footerCtaSub: '下载 DBX 或用 Docker 秒级部署。',
+  },
+};
+
+export default async function LandingPage({
   params,
 }: {
   params: Promise<{ lang: string }>;
 }) {
   const { lang } = await params;
-  redirect(`/${lang}/docs/what-is-dbx`);
+  const l = lang === 'cn' ? 'cn' : 'en';
+  const t = i18nText[l];
+  const feat = features[l];
+  const stat = stats[l];
+  const comp = comparison[l];
+
+  return (
+    <main className="landing">
+      {/* Navbar */}
+      <nav className="landing-nav">
+        <div className="landing-nav-inner">
+          <Link href={`/${l}`} className="landing-logo">
+            <img src="/logo.png" alt="DBX" width={28} height={28} />
+            <span>DBX</span>
+          </Link>
+          <div className="landing-nav-links">
+            <Link href={`/${l}/docs/what-is-dbx`}>{l === 'cn' ? '文档' : 'Docs'}</Link>
+            <Link href="https://github.com/t8y2/dbx" target="_blank">GitHub</Link>
+            <Link href="https://discord.gg/W7NyVDRt6a" target="_blank">Discord</Link>
+            <Link href={l === 'cn' ? '/en' : '/cn'} className="landing-lang-switch">
+              {l === 'cn' ? 'EN' : '中文'}
+            </Link>
+          </div>
+        </div>
+      </nav>
+
+      {/* Hero */}
+      <section className="landing-hero">
+        <div className="landing-hero-content">
+          <h1 className="landing-hero-title">
+            <span className="landing-gradient">{t.heroTitle}</span>
+            <br />
+            {t.heroTitle2}
+          </h1>
+          <p className="landing-hero-sub">{t.heroSubtitle}</p>
+          <div className="landing-hero-cta">
+            <Link href="https://github.com/t8y2/dbx/releases" className="landing-btn-primary">
+              {t.ctaDownload} <ArrowRight size={16} />
+            </Link>
+            <Link href={`/${l}/docs/what-is-dbx`} className="landing-btn-secondary">
+              {t.ctaDocs}
+            </Link>
+          </div>
+        </div>
+        <div className="landing-hero-image">
+          <img src="/screenshot-dark.png" alt="DBX Screenshot" />
+        </div>
+      </section>
+
+      {/* Stats */}
+      <section className="landing-stats">
+        {stat.map((s) => (
+          <div key={s.label} className="landing-stat">
+            <div className="landing-stat-value">{s.value}</div>
+            <div className="landing-stat-label">{s.label}</div>
+          </div>
+        ))}
+      </section>
+
+      {/* Features */}
+      <section className="landing-section">
+        <h2 className="landing-section-title">{t.featuresTitle}</h2>
+        <p className="landing-section-sub">{t.featuresSubtitle}</p>
+        <div className="landing-features-grid">
+          {feat.map((f) => (
+            <Link key={f.title} href={f.href} className="landing-feature-card">
+              <div className="landing-feature-icon">
+                <f.icon size={24} />
+              </div>
+              <h3>{f.title}</h3>
+              <p>{f.desc}</p>
+            </Link>
+          ))}
+        </div>
+      </section>
+
+      {/* Database Logos */}
+      <section className="landing-section">
+        <h2 className="landing-section-title">{t.dbTitle}</h2>
+        <p className="landing-section-sub">{t.dbSubtitle}</p>
+        <div className="landing-db-grid">
+          {databases.map((db) => (
+            <div key={db} className="landing-db-badge">
+              <Database size={16} />
+              <span>{db}</span>
+            </div>
+          ))}
+          <div className="landing-db-badge landing-db-more">
+            <span>{t.andMore}</span>
+          </div>
+        </div>
+      </section>
+
+      {/* Comparison */}
+      <section className="landing-section">
+        <h2 className="landing-section-title">{comp.title}</h2>
+        <div className="landing-comparison">
+          <table>
+            <thead>
+              <tr>
+                {comp.headers.map((h, i) => (
+                  <th key={i} className={i === 1 ? 'landing-highlight-col' : ''}>
+                    {h}
+                  </th>
+                ))}
+              </tr>
+            </thead>
+            <tbody>
+              {comp.rows.map((row, ri) => (
+                <tr key={ri}>
+                  {row.map((cell, ci) => (
+                    <td key={ci} className={ci === 1 ? 'landing-highlight-col' : ''}>
+                      {cell}
+                    </td>
+                  ))}
+                </tr>
+              ))}
+            </tbody>
+          </table>
+        </div>
+      </section>
+
+      {/* Screenshots */}
+      <section className="landing-section">
+        <div className="landing-screenshots">
+          <div className="landing-screenshot-item">
+            <img src="/screenshot-light.png" alt="DBX Light Mode" />
+          </div>
+          <div className="landing-screenshot-item">
+            <img src="/screenshot-er.png" alt="DBX ER Diagram" />
+          </div>
+        </div>
+      </section>
+
+      {/* Footer CTA */}
+      <section className="landing-footer-cta">
+        <h2>{t.footerCta}</h2>
+        <p>{t.footerCtaSub}</p>
+        <div className="landing-hero-cta">
+          <Link href="https://github.com/t8y2/dbx/releases" className="landing-btn-primary">
+            {t.ctaDownload} <ArrowRight size={16} />
+          </Link>
+          <Link href={`/${l}/docs/getting-started`} className="landing-btn-secondary">
+            {t.ctaDocs}
+          </Link>
+        </div>
+      </section>
+
+      {/* Footer */}
+      <footer className="landing-footer">
+        <div className="landing-footer-inner">
+          <div className="landing-footer-brand">
+            <img src="/logo.png" alt="DBX" width={20} height={20} />
+            <span>DBX</span>
+          </div>
+          <div className="landing-footer-links">
+            <Link href="https://github.com/t8y2/dbx" target="_blank">GitHub</Link>
+            <Link href="https://discord.gg/W7NyVDRt6a" target="_blank">Discord</Link>
+            <Link href="https://github.com/t8y2/dbx/blob/main/LICENSE" target="_blank">AGPL-3.0</Link>
+          </div>
+        </div>
+      </footer>
+    </main>
+  );
 }
diff --git a/docs/app/global.css b/docs/app/global.css
index 6ff46f2e4c..b692b1d211 100644
--- a/docs/app/global.css
+++ b/docs/app/global.css
@@ -1,3 +1,433 @@
 @import 'tailwindcss';
 @import 'fumadocs-ui/css/ocean.css';
 @import 'fumadocs-ui/css/preset.css';
+
+/* ===== Landing Page Styles ===== */
+
+.landing {
+  --landing-max: 1200px;
+  --landing-accent: #3b82f6;
+  --landing-accent-dark: #2563eb;
+  color: var(--color-fd-foreground);
+  background: var(--color-fd-background);
+}
+
+/* Navbar */
+.landing-nav {
+  position: sticky;
+  top: 0;
+  z-index: 50;
+  backdrop-filter: blur(12px);
+  background: color-mix(in srgb, var(--color-fd-background) 80%, transparent);
+  border-bottom: 1px solid var(--color-fd-border);
+}
+
+.landing-nav-inner {
+  max-width: var(--landing-max);
+  margin: 0 auto;
+  padding: 0.875rem 1.5rem;
+  display: flex;
+  align-items: center;
+  justify-content: space-between;
+}
+
+.landing-logo {
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+  font-weight: 700;
+  font-size: 1.125rem;
+  color: var(--color-fd-foreground);
+  text-decoration: none;
+}
+
+.landing-nav-links {
+  display: flex;
+  align-items: center;
+  gap: 1.5rem;
+}
+
+.landing-nav-links a {
+  color: var(--color-fd-muted-foreground);
+  text-decoration: none;
+  font-size: 0.875rem;
+  font-weight: 500;
+  transition: color 0.15s;
+}
+
+.landing-nav-links a:hover {
+  color: var(--color-fd-foreground);
+}
+
+.landing-lang-switch {
+  padding: 0.25rem 0.75rem;
+  border: 1px solid var(--color-fd-border);
+  border-radius: 6px;
+  font-size: 0.75rem !important;
+}
+
+/* Hero */
+.landing-hero {
+  max-width: var(--landing-max);
+  margin: 0 auto;
+  padding: 5rem 1.5rem 3rem;
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  text-align: center;
+  gap: 3rem;
+}
+
+.landing-hero-title {
+  font-size: 3.5rem;
+  font-weight: 800;
+  line-height: 1.1;
+  letter-spacing: -0.03em;
+}
+
+.landing-gradient {
+  background: linear-gradient(135deg, #3b82f6 0%, #8b5cf6 50%, #ec4899 100%);
+  -webkit-background-clip: text;
+  -webkit-text-fill-color: transparent;
+  background-clip: text;
+}
+
+.landing-hero-sub {
+  max-width: 600px;
+  margin: 1.25rem auto 0;
+  font-size: 1.125rem;
+  line-height: 1.6;
+  color: var(--color-fd-muted-foreground);
+}
+
+.landing-hero-cta {
+  display: flex;
+  gap: 0.75rem;
+  margin-top: 2rem;
+  flex-wrap: wrap;
+  justify-content: center;
+}
+
+.landing-btn-primary {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.5rem;
+  padding: 0.75rem 1.75rem;
+  background: var(--landing-accent);
+  color: #fff;
+  border-radius: 8px;
+  font-weight: 600;
+  font-size: 0.9375rem;
+  text-decoration: none;
+  transition: background 0.15s, transform 0.1s;
+}
+
+.landing-btn-primary:hover {
+  background: var(--landing-accent-dark);
+  transform: translateY(-1px);
+}
+
+.landing-btn-secondary {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.5rem;
+  padding: 0.75rem 1.75rem;
+  border: 1px solid var(--color-fd-border);
+  color: var(--color-fd-foreground);
+  border-radius: 8px;
+  font-weight: 600;
+  font-size: 0.9375rem;
+  text-decoration: none;
+  transition: border-color 0.15s, background 0.15s;
+}
+
+.landing-btn-secondary:hover {
+  background: var(--color-fd-accent);
+  border-color: var(--color-fd-muted-foreground);
+}
+
+.landing-hero-image {
+  width: 100%;
+  max-width: 1000px;
+}
+
+.landing-hero-image img {
+  width: 100%;
+  border-radius: 12px;
+  border: 1px solid var(--color-fd-border);
+  box-shadow: 0 20px 60px -15px rgba(0, 0, 0, 0.3);
+}
+
+/* Stats */
+.landing-stats {
+  max-width: var(--landing-max);
+  margin: 0 auto;
+  padding: 3rem 1.5rem;
+  display: grid;
+  grid-template-columns: repeat(4, 1fr);
+  gap: 1.5rem;
+}
+
+.landing-stat {
+  text-align: center;
+  padding: 1.5rem;
+  border-radius: 12px;
+  background: var(--color-fd-card);
+  border: 1px solid var(--color-fd-border);
+}
+
+.landing-stat-value {
+  font-size: 1.75rem;
+  font-weight: 800;
+  color: var(--landing-accent);
+}
+
+.landing-stat-label {
+  margin-top: 0.25rem;
+  font-size: 0.875rem;
+  color: var(--color-fd-muted-foreground);
+}
+
+/* Sections */
+.landing-section {
+  max-width: var(--landing-max);
+  margin: 0 auto;
+  padding: 4rem 1.5rem;
+}
+
+.landing-section-title {
+  font-size: 2rem;
+  font-weight: 700;
+  text-align: center;
+  letter-spacing: -0.02em;
+}
+
+.landing-section-sub {
+  text-align: center;
+  color: var(--color-fd-muted-foreground);
+  margin-top: 0.5rem;
+  font-size: 1rem;
+}
+
+/* Feature Cards */
+.landing-features-grid {
+  display: grid;
+  grid-template-columns: repeat(4, 1fr);
+  gap: 1rem;
+  margin-top: 2.5rem;
+}
+
+.landing-feature-card {
+  padding: 1.5rem;
+  border-radius: 12px;
+  border: 1px solid var(--color-fd-border);
+  background: var(--color-fd-card);
+  text-decoration: none;
+  color: var(--color-fd-foreground);
+  transition: border-color 0.2s, box-shadow 0.2s, transform 0.15s;
+}
+
+.landing-feature-card:hover {
+  border-color: var(--landing-accent);
+  box-shadow: 0 4px 20px rgba(59, 130, 246, 0.1);
+  transform: translateY(-2px);
+}
+
+.landing-feature-icon {
+  display: inline-flex;
+  padding: 0.5rem;
+  border-radius: 8px;
+  background: color-mix(in srgb, var(--landing-accent) 12%, transparent);
+  color: var(--landing-accent);
+  margin-bottom: 0.75rem;
+}
+
+.landing-feature-card h3 {
+  font-size: 1rem;
+  font-weight: 600;
+  margin-bottom: 0.375rem;
+}
+
+.landing-feature-card p {
+  font-size: 0.8125rem;
+  line-height: 1.5;
+  color: var(--color-fd-muted-foreground);
+}
+
+/* Database Badges */
+.landing-db-grid {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 0.625rem;
+  justify-content: center;
+  margin-top: 2rem;
+  max-width: 800px;
+  margin-left: auto;
+  margin-right: auto;
+}
+
+.landing-db-badge {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.375rem;
+  padding: 0.5rem 0.875rem;
+  border-radius: 999px;
+  border: 1px solid var(--color-fd-border);
+  font-size: 0.8125rem;
+  font-weight: 500;
+  color: var(--color-fd-muted-foreground);
+  background: var(--color-fd-card);
+  transition: border-color 0.15s;
+}
+
+.landing-db-badge:hover {
+  border-color: var(--landing-accent);
+  color: var(--color-fd-foreground);
+}
+
+.landing-db-more {
+  border-style: dashed;
+}
+
+/* Comparison Table */
+.landing-comparison {
+  margin-top: 2rem;
+  overflow-x: auto;
+}
+
+.landing-comparison table {
+  width: 100%;
+  border-collapse: collapse;
+  font-size: 0.875rem;
+}
+
+.landing-comparison th,
+.landing-comparison td {
+  padding: 0.75rem 1rem;
+  text-align: left;
+  border-bottom: 1px solid var(--color-fd-border);
+}
+
+.landing-comparison th {
+  font-weight: 600;
+  color: var(--color-fd-muted-foreground);
+  font-size: 0.8125rem;
+  text-transform: uppercase;
+  letter-spacing: 0.05em;
+}
+
+.landing-comparison td:first-child {
+  font-weight: 500;
+}
+
+.landing-highlight-col {
+  background: color-mix(in srgb, var(--landing-accent) 6%, transparent);
+  color: var(--landing-accent) !important;
+  font-weight: 600 !important;
+}
+
+/* Screenshots */
+.landing-screenshots {
+  display: grid;
+  grid-template-columns: repeat(2, 1fr);
+  gap: 1.5rem;
+}
+
+.landing-screenshot-item img {
+  width: 100%;
+  border-radius: 10px;
+  border: 1px solid var(--color-fd-border);
+  transition: transform 0.2s;
+}
+
+.landing-screenshot-item img:hover {
+  transform: scale(1.02);
+}
+
+/* Footer CTA */
+.landing-footer-cta {
+  text-align: center;
+  padding: 5rem 1.5rem;
+  margin: 2rem auto;
+  max-width: var(--landing-max);
+  border-radius: 16px;
+  background: linear-gradient(135deg, color-mix(in srgb, var(--landing-accent) 8%, transparent), color-mix(in srgb, #8b5cf6 8%, transparent));
+  border: 1px solid var(--color-fd-border);
+}
+
+.landing-footer-cta h2 {
+  font-size: 2rem;
+  font-weight: 700;
+}
+
+.landing-footer-cta p {
+  color: var(--color-fd-muted-foreground);
+  margin-top: 0.5rem;
+}
+
+/* Footer */
+.landing-footer {
+  border-top: 1px solid var(--color-fd-border);
+  padding: 1.5rem;
+}
+
+.landing-footer-inner {
+  max-width: var(--landing-max);
+  margin: 0 auto;
+  display: flex;
+  align-items: center;
+  justify-content: space-between;
+}
+
+.landing-footer-brand {
+  display: flex;
+  align-items: center;
+  gap: 0.5rem;
+  font-weight: 600;
+  font-size: 0.875rem;
+}
+
+.landing-footer-links {
+  display: flex;
+  gap: 1.5rem;
+}
+
+.landing-footer-links a {
+  color: var(--color-fd-muted-foreground);
+  text-decoration: none;
+  font-size: 0.8125rem;
+  transition: color 0.15s;
+}
+
+.landing-footer-links a:hover {
+  color: var(--color-fd-foreground);
+}
+
+/* Responsive */
+@media (max-width: 768px) {
+  .landing-hero-title {
+    font-size: 2.25rem;
+  }
+
+  .landing-stats {
+    grid-template-columns: repeat(2, 1fr);
+  }
+
+  .landing-features-grid {
+    grid-template-columns: 1fr;
+  }
+
+  .landing-screenshots {
+    grid-template-columns: 1fr;
+  }
+
+  .landing-comparison {
+    font-size: 0.8125rem;
+  }
+}
+
+@media (min-width: 769px) and (max-width: 1024px) {
+  .landing-features-grid {
+    grid-template-columns: repeat(2, 1fr);
+  }
+}
diff --git a/docs/content/docs/ai-assistant.cn.mdx b/docs/content/docs/ai-assistant.cn.mdx
index 62ff54b498..923014e79f 100644
--- a/docs/content/docs/ai-assistant.cn.mdx
+++ b/docs/content/docs/ai-assistant.cn.mdx
@@ -1,50 +1,122 @@
 ---
 title: AI 助手
-description: 内置 AI 助手，帮你编写、解释、优化和修复 SQL 查询。
+description: 内置 AI 助手，自然语言转 SQL、查询优化、错误修复，支持 Claude/OpenAI/自定义端点。
 ---
 
-DBX 内置 AI 助手，帮你编写、解释、优化和修复 SQL 查询。
+<Callout type="info">
+内置 AI 助手，无需额外安装插件。自然语言描述需求，AI 帮你生成 SQL、优化查询、修复错误。
+</Callout>
+
+DBX 内置 AI 助手，深度集成数据库元数据，能根据你的表结构和字段生成精准的 SQL。
+
+![DBX AI 助手](/screenshot-ai.jpg)
 
 ## 设置
 
-1. 点击工具栏的 **设置** 图标
-2. 进入 **AI 设置**
-3. 选择供应商（Claude、OpenAI 或自定义端点）
-4. 输入 API Key
-5. 选择模型
+<Steps>
+  <Step>
+    ### 打开设置
+    点击工具栏的 **设置** 图标。
+  </Step>
+  <Step>
+    ### 选择 AI 供应商
+    进入 **AI 设置**，选择供应商。
+  </Step>
+  <Step>
+    ### 输入 API Key
+    填入你的 API Key（如使用自定义端点，还需填入端点 URL）。
+  </Step>
+  <Step>
+    ### 选择模型并开始使用
+    选择一个模型，完成设置。回到编辑器即可使用 AI 功能。
+  </Step>
+</Steps>
 
-## 功能
+## 核心功能
 
 ### 自然语言转 SQL
 
-用自然语言描述你想查询的内容：
+用自然语言描述你的查询需求，AI 助手根据数据库结构生成对应的 SQL：
 
-> "查看最近 10 个订单金额最高的客户"
+> **你说：** "查看最近 10 个订单金额最高的客户"
+>
+> **AI 生成：**
+> ```sql
+> SELECT c.name, SUM(o.amount) AS total_amount
+> FROM customers c
+> JOIN orders o ON c.id = o.customer_id
+> WHERE o.created_at >= NOW() - INTERVAL 30 DAY
+> GROUP BY c.id, c.name
+> ORDER BY total_amount DESC
+> LIMIT 10;
+> ```
 
-AI 助手会根据你的数据库结构生成 SQL。
+AI 会自动识别你当前连接的数据库中的表名和字段名，不会生成不存在的表或字段。
 
 ### 解释 SQL
 
-选中一段 SQL 查询，让 AI 解释它的作用。
+选中一段复杂的 SQL 查询，AI 会逐步解释它的逻辑：
+
+- 每个子查询的作用
+- JOIN 条件的含义
+- WHERE 过滤条件的业务意义
+- 聚合函数和分组逻辑
 
 ### 优化 SQL
 
-获取查询性能优化建议。
+AI 会分析查询的潜在性能问题，给出优化建议：
+
+- 是否缺少索引
+- 是否可以减少全表扫描
+- 子查询是否可以改写为 JOIN
+- 是否存在不必要的排序或去重
 
 ### 修复错误
 
-查询执行失败时，点击 **AI 修复** 获取修正后的版本。
+查询执行失败时，点击 **AI 修复**，AI 会根据错误信息和 SQL 内容自动生成修正版本。常见场景包括：
+
+- 语法错误修正
+- 字段名或表名拼写错误
+- 缺少 GROUP BY 字段
+- 类型不匹配
 
 ## 支持的供应商
 
-| 供应商 | 模型 |
-|---|---|
-| Anthropic (Claude) | Claude 4 Opus、Claude 4 Sonnet、Claude 3.5 Haiku |
-| OpenAI | GPT-4o、GPT-4o-mini、o3-mini |
-| 自定义端点 | 任何 OpenAI 兼容的 API 端点 |
+<Tabs groupId="ai-provider" items={['Anthropic (Claude)', 'OpenAI', '自定义端点']}>
+  <Tab value="Anthropic (Claude)">
+    | 模型 | 说明 |
+    |---|---|
+    | Claude 4 Opus | 最强模型，复杂查询推荐 |
+    | Claude 4 Sonnet | 速度与质量平衡 |
+    | Claude 3.5 Haiku | 最快响应 |
 
-你可以配置自定义的 OpenAI 兼容端点（自定义端点），连接第三方或自托管的 AI 服务。只需在 AI 设置中选择"自定义端点"，填入 API 地址和 Key 即可。
+    在 AI 设置中选择 **Anthropic**，填入 API Key 即可。
+  </Tab>
+  <Tab value="OpenAI">
+    | 模型 | 说明 |
+    |---|---|
+    | GPT-4o | 最新旗舰模型 |
+    | GPT-4o-mini | 轻量快速 |
+    | o3-mini | 推理增强 |
+
+    在 AI 设置中选择 **OpenAI**，填入 API Key 即可。
+  </Tab>
+  <Tab value="自定义端点">
+    任何兼容 OpenAI Chat Completions API 的端点都可以使用，例如：
+
+    - **Ollama** — 本地运行开源模型
+    - **LM Studio** — 本地模型管理
+    - **Azure OpenAI** — 企业级部署
+    - **DeepSeek / Qwen** — 国产大模型
+
+    在 AI 设置中选择 **自定义端点**，填入端点 URL 和 API Key。
+  </Tab>
+</Tabs>
 
 ## 更强大的 AI 体验
 
-除了内置 AI 助手，还可以试试 [MCP 集成](/cn/docs/mcp)。它让 Claude Code、Cursor 等 AI 编程助手直接查询你的数据库，并在 DBX 中打开结果。
+<Callout type="info">
+想让 AI 助手不只是生成 SQL，还能直接执行查询、浏览数据？试试 [MCP 集成](/cn/docs/mcp)。
+</Callout>
+
+MCP 集成让 Claude Code、Cursor 等 AI 编程助手直接通过 DBX 查询你的数据库，并在 DBX 中打开结果。这意味着你可以在 IDE 中用自然语言和 AI 对话，AI 自动调用 DBX 执行查询并返回结果。
diff --git a/docs/content/docs/ai-assistant.mdx b/docs/content/docs/ai-assistant.mdx
index 96edd10f7e..cd7dea6712 100644
--- a/docs/content/docs/ai-assistant.mdx
+++ b/docs/content/docs/ai-assistant.mdx
@@ -1,50 +1,122 @@
 ---
 title: AI Assistant
-description: Built-in AI assistant for writing, explaining, optimizing, and fixing SQL queries.
+description: Built-in AI assistant for natural language to SQL, query optimization, error fixing. Supports Claude, OpenAI, and custom endpoints.
 ---
 
-# AI Assistant
+<Callout type="info">
+Built-in AI assistant — no plugins needed. Describe what you want in plain language, and AI generates SQL, optimizes queries, and fixes errors.
+</Callout>
 
-DBX has a built-in AI assistant that helps you write, explain, optimize, and fix SQL queries.
+DBX's AI assistant is deeply integrated with your database metadata. It knows your tables, columns, and relationships, so the SQL it generates actually works with your schema.
+
+![DBX AI Assistant](/screenshot-ai.jpg)
 
 ## Setup
 
-1. Click the **Settings** icon in the toolbar
-2. Go to **AI Settings**
-3. Choose your provider (Claude, OpenAI, or a custom OpenAI-compatible endpoint)
-4. Enter your API key (and endpoint URL for custom providers)
-5. Select a model
+<Steps>
+  <Step>
+    ### Open Settings
+    Click the **Settings** icon in the toolbar.
+  </Step>
+  <Step>
+    ### Choose AI Provider
+    Go to **AI Settings** and select your provider.
+  </Step>
+  <Step>
+    ### Enter API Key
+    Enter your API key (and endpoint URL for custom providers).
+  </Step>
+  <Step>
+    ### Select a Model
+    Pick a model and you're ready to go.
+  </Step>
+</Steps>
 
-## Features
+## Core Features
 
 ### Natural Language to SQL
 
-Describe what you want to query in plain language:
+Describe what you want to query in plain language. The AI generates SQL based on your actual database schema:
 
-> "Show me the top 10 customers by total order amount"
+> **You say:** "Show me the top 10 customers by total order amount in the last month"
+>
+> **AI generates:**
+> ```sql
+> SELECT c.name, SUM(o.amount) AS total_amount
+> FROM customers c
+> JOIN orders o ON c.id = o.customer_id
+> WHERE o.created_at >= NOW() - INTERVAL 30 DAY
+> GROUP BY c.id, c.name
+> ORDER BY total_amount DESC
+> LIMIT 10;
+> ```
 
-The AI assistant will generate the SQL based on your database schema.
+The AI auto-detects tables and columns in your connected database — it won't generate references to tables or columns that don't exist.
 
 ### Explain SQL
 
-Select a SQL query and ask the AI to explain what it does.
+Select a complex SQL query and ask the AI to explain it. It breaks down:
+
+- What each subquery does
+- The purpose of JOIN conditions
+- What the WHERE clause filters
+- How aggregation and grouping work
 
 ### Optimize SQL
 
-Get suggestions for improving query performance.
+The AI analyzes your query for potential performance issues and suggests improvements:
+
+- Missing indexes
+- Full table scans that could be avoided
+- Subqueries that could be rewritten as JOINs
+- Unnecessary sorting or deduplication
 
 ### Fix Errors
 
-When a query fails, click **Fix with AI** to get a corrected version.
+When a query fails, click **Fix with AI**. The AI reads the error message and your SQL, then generates a corrected version. Common fixes include:
+
+- Syntax error corrections
+- Misspelled table or column names
+- Missing GROUP BY columns
+- Type mismatches
 
 ## Supported Providers
 
-| Provider | Models |
-|---|---|
-| Anthropic (Claude) | Claude 4 Opus, Claude 4 Sonnet, Claude 3.5 Haiku |
-| OpenAI | GPT-4o, GPT-4o-mini, o3-mini |
-| Custom / OpenAI-compatible | Any endpoint that implements the OpenAI chat completions API (e.g., Ollama, LM Studio, Azure OpenAI, self-hosted models) |
+<Tabs groupId="ai-provider" items={['Anthropic (Claude)', 'OpenAI', 'Custom Endpoint']}>
+  <Tab value="Anthropic (Claude)">
+    | Model | Best For |
+    |---|---|
+    | Claude 4 Opus | Complex queries, highest quality |
+    | Claude 4 Sonnet | Balance of speed and quality |
+    | Claude 3.5 Haiku | Fastest responses |
+
+    Select **Anthropic** in AI Settings and enter your API key.
+  </Tab>
+  <Tab value="OpenAI">
+    | Model | Best For |
+    |---|---|
+    | GPT-4o | Latest flagship model |
+    | GPT-4o-mini | Lightweight and fast |
+    | o3-mini | Enhanced reasoning |
+
+    Select **OpenAI** in AI Settings and enter your API key.
+  </Tab>
+  <Tab value="Custom Endpoint">
+    Any endpoint that implements the OpenAI Chat Completions API works, including:
+
+    - **Ollama** — Run open-source models locally
+    - **LM Studio** — Local model management
+    - **Azure OpenAI** — Enterprise deployment
+    - **DeepSeek / Qwen** — Additional model providers
+
+    Select **Custom Endpoint** in AI Settings and enter the endpoint URL and API key.
+  </Tab>
+</Tabs>
 
 ## Beyond Built-in AI
 
-For a more powerful AI-driven database experience, try the [MCP integration](/docs/mcp). It lets AI coding agents like Claude Code and Cursor directly query your databases and open results in DBX.
+<Callout type="info">
+Want AI to not just generate SQL, but actually execute queries and browse results? Try the [MCP integration](/en/docs/mcp).
+</Callout>
+
+MCP integration lets AI coding agents like Claude Code and Cursor query your databases directly through DBX and open results in the DBX UI. You can have a natural language conversation with AI in your IDE, and it automatically calls DBX to run queries and return results.
diff --git a/docs/content/docs/config-export.cn.mdx b/docs/content/docs/config-export.cn.mdx
index ec4e8aced2..a5ef9075ca 100644
--- a/docs/content/docs/config-export.cn.mdx
+++ b/docs/content/docs/config-export.cn.mdx
@@ -1,34 +1,52 @@
 ---
 title: 配置导出/导入
-description: 导出数据库连接配置（含加密密码），方便在不同电脑之间迁移。
+description: 导出数据库连接配置（AES-256-GCM 加密），安全地在不同电脑之间迁移。
 ---
 
-导出数据库连接配置（含加密密码），方便在不同电脑之间迁移。
+<Callout type="info">
+导出你的数据库连接配置（含加密密码），用 AES-256-GCM 加密保护，安全地在不同电脑之间迁移。
+</Callout>
 
 ## 导出
 
-1. 点击侧边栏顶部的 **导出** 按钮
-2. 输入密码短语来加密连接密码
-3. 选择保存位置
-4. 导出文件包含所有连接及密码，已加密
+<Steps>
+  <Step>
+    ### 发起导出
+    点击侧边栏顶部的 **导出** 按钮。
+  </Step>
+  <Step>
+    ### 设置加密密码
+    输入密码短语来加密连接密码。
+  </Step>
+  <Step>
+    ### 保存文件
+    选择保存位置。导出文件包含所有连接及密码，已加密。
+  </Step>
+</Steps>
 
 ## 导入
 
-1. 点击侧边栏顶部的 **导入** 按钮
-2. 选择导出的文件
-3. 如果文件已加密，输入密码短语
-4. 连接导入完成，密码自动恢复
+<Steps>
+  <Step>
+    ### 发起导入
+    点击侧边栏顶部的 **导入** 按钮。
+  </Step>
+  <Step>
+    ### 选择文件并解密
+    选择导出的文件，输入密码短语解密。
+  </Step>
+  <Step>
+    ### 完成
+    连接导入完成，密码自动恢复。按 名称 + 主机 + 端口 自动去重。
+  </Step>
+</Steps>
 
 ## 安全性
 
-- 密码使用 AES-256-GCM 加密，密钥通过 PBKDF2 派生
+- 密码使用 **AES-256-GCM** 加密，密钥通过 **PBKDF2** 派生
 - 没有密码短语无法解密文件
 - 导出文件是标准 JSON 格式，可以通过 U 盘、网盘等方式传输
 
 ## 向后兼容
 
-导入同样支持：
-- 旧版本导出的明文 JSON 文件（不含密码）
-- 原始的连接配置数组
-
-导入时按 名称 + 主机 + 端口 去重。
+导入同样支持旧版本导出的明文 JSON 文件（不含密码）和原始的连接配置数组。
diff --git a/docs/content/docs/config-export.mdx b/docs/content/docs/config-export.mdx
index ec89b7229a..f0604acd46 100644
--- a/docs/content/docs/config-export.mdx
+++ b/docs/content/docs/config-export.mdx
@@ -1,36 +1,52 @@
 ---
 title: Config Export/Import
-description: Export and import database connections with encrypted passwords to migrate between machines.
+description: Export database connections with AES-256-GCM encrypted passwords. Migrate securely between machines.
 ---
 
-# Config Export/Import
-
-Export your database connections (with encrypted passwords) to migrate between machines.
+<Callout type="info">
+Export your database connections with encrypted passwords (AES-256-GCM). Securely migrate between machines.
+</Callout>
 
 ## Export
 
-1. Click the **Export** button in the sidebar header
-2. Enter a passphrase to encrypt your passwords
-3. Choose a save location
-4. The exported file contains all connections with passwords, encrypted
+<Steps>
+  <Step>
+    ### Start Export
+    Click the **Export** button in the sidebar header.
+  </Step>
+  <Step>
+    ### Set Passphrase
+    Enter a passphrase to encrypt your passwords.
+  </Step>
+  <Step>
+    ### Save File
+    Choose a save location. The exported file contains all connections with passwords, encrypted.
+  </Step>
+</Steps>
 
 ## Import
 
-1. Click the **Import** button in the sidebar header
-2. Select the exported file
-3. If encrypted, enter the passphrase
-4. Connections are imported with passwords restored
+<Steps>
+  <Step>
+    ### Start Import
+    Click the **Import** button in the sidebar header.
+  </Step>
+  <Step>
+    ### Select File and Decrypt
+    Select the exported file and enter the passphrase.
+  </Step>
+  <Step>
+    ### Done
+    Connections are imported with passwords restored. Deduplicated by name + host + port.
+  </Step>
+</Steps>
 
 ## Security
 
-- Passwords are encrypted using AES-256-GCM with PBKDF2 key derivation
+- Passwords are encrypted using **AES-256-GCM** with **PBKDF2** key derivation
 - Without the passphrase, the file cannot be decrypted
-- The export file is a standard JSON file that can be transferred via USB drive, cloud storage, etc.
+- The export file is standard JSON, transferable via USB drive, cloud storage, etc.
 
 ## Backward Compatibility
 
-Import also supports:
-- Plain JSON files exported from older versions (without passwords)
-- Raw connection config arrays
-
-Connections are deduplicated by name + host + port during import.
+Import also supports plain JSON files from older versions (without passwords) and raw connection config arrays.
diff --git a/docs/content/docs/data-grid.cn.mdx b/docs/content/docs/data-grid.cn.mdx
index 2b0999e494..3a5b884619 100644
--- a/docs/content/docs/data-grid.cn.mdx
+++ b/docs/content/docs/data-grid.cn.mdx
@@ -1,9 +1,11 @@
 ---
 title: 数据表格
-description: 浏览和编辑表中的数据，支持虚拟滚动、行内编辑、排序过滤和多种格式导出。
+description: 虚拟滚动浏览大数据量，行内编辑，SQL 预览，多格式导出。
 ---
 
-DBX 的数据表格组件用于浏览和编辑表中的数据，支持大数据量虚拟滚动、行内编辑、排序过滤以及多种格式导出。
+<Callout type="info">
+虚拟滚动技术，10 万行数据依然流畅。行内编辑，保存前可预览将要执行的 SQL 语句。
+</Callout>
 
 ## 虚拟滚动
 
@@ -11,33 +13,35 @@ DBX 的数据表格组件用于浏览和编辑表中的数据，支持大数据
 
 ## 行内编辑
 
-你可以直接在表格中编辑数据，无需编写 SQL 语句：
+直接在表格中编辑数据，无需编写 SQL 语句：
 
-- **修改数据** -- 双击单元格即可编辑，修改后的单元格会高亮标记
-- **新增行** -- 点击工具栏中的"新增行"按钮，在表格底部插入一行空记录
-- **删除行** -- 选中行后点击"删除"按钮，标记该行待删除
+- **修改数据** — 双击单元格即可编辑，修改后的单元格会高亮标记
+- **新增行** — 点击工具栏中的"新增行"按钮，在表格底部插入一行空记录
+- **删除行** — 选中行后点击"删除"按钮，标记该行待删除
 
 所有修改会暂存在本地，不会立即写入数据库。
 
 ## SQL 预览
 
-在点击"保存"之前，你可以预览 DBX 即将执行的 SQL 语句（`UPDATE`、`INSERT`、`DELETE`），确认无误后再提交。这样可以避免误操作对数据造成不可逆的影响。
+<Callout type="info">
+在点击"保存"之前，可以预览 DBX 即将执行的 `UPDATE`、`INSERT`、`DELETE` 语句，确认无误后再提交。
+</Callout>
+
+这样可以避免误操作对数据造成不可逆的影响。
 
 ## 排序与过滤
 
-- **排序** -- 点击列头可按该列升序或降序排列
-- **搜索** -- 使用搜索框快速查找包含指定文本的行
-- **WHERE 过滤** -- 输入自定义的 `WHERE` 条件，精确筛选满足条件的数据
+- **排序** — 点击列头可按该列升序或降序排列
+- **搜索** — 使用搜索框快速查找包含指定文本的行
+- **WHERE 过滤** — 输入自定义的 `WHERE` 条件，在数据库层面精确筛选，大表场景比客户端搜索更高效
 
 ## 列宽调整与行号
 
-- 拖拽列头边缘可以调整列宽，以适应不同长度的数据内容
-- 表格左侧显示行号，方便定位和引用
+- 拖拽列头边缘可以调整列宽
+- 表格左侧显示行号，方便定位
 
 ## 数据导出
 
-选择工具栏中的导出功能，可将当前表格数据导出为以下格式：
-
 | 格式 | 说明 |
 |---|---|
 | CSV | 逗号分隔的文本文件，适合导入 Excel 或其他工具 |
diff --git a/docs/content/docs/data-grid.mdx b/docs/content/docs/data-grid.mdx
index 17756ce70d..4f05c6b6f3 100644
--- a/docs/content/docs/data-grid.mdx
+++ b/docs/content/docs/data-grid.mdx
@@ -1,50 +1,49 @@
 ---
 title: Data Grid
-description: Browse, edit, and export query results in a high-performance spreadsheet-like interface.
+description: Virtual scrolling for 100K+ rows, inline editing with SQL preview, multi-format export.
 ---
 
-# Data Grid
-
-The Data Grid displays query results and table data in a high-performance, spreadsheet-like interface. It supports browsing large datasets, inline editing, and exporting data in multiple formats.
+<Callout type="info">
+Virtual scrolling keeps it smooth at 100K+ rows. Inline editing with full SQL preview before committing any changes.
+</Callout>
 
 ## Virtual Scrolling
 
-The grid uses virtual scrolling to handle large result sets efficiently. Only the rows visible on screen are rendered at any given time, so performance remains consistent whether you are viewing 100 rows or 100,000 rows.
+The grid uses virtual scrolling — only the rows visible on screen are rendered at any given time, so performance remains consistent whether you are viewing 100 rows or 100,000 rows.
 
 ## Inline Editing
 
-You can edit data directly in the grid without writing SQL manually. The following operations are supported:
+Edit data directly in the grid without writing SQL:
 
-- **UPDATE** -- Click a cell to modify its value. Changed cells are highlighted to indicate pending modifications.
-- **INSERT** -- Add a new row at the bottom of the grid and fill in cell values.
-- **DELETE** -- Select one or more rows and mark them for deletion.
+- **UPDATE** — Click a cell to modify its value. Changed cells are highlighted
+- **INSERT** — Add a new row at the bottom and fill in cell values
+- **DELETE** — Select rows and mark them for deletion
 
-### SQL Preview Before Saving
+All changes are staged locally and not written to the database until you confirm.
 
-Before any changes are committed to the database, DBX shows a preview of the exact SQL statements that will be executed (`UPDATE`, `INSERT`, or `DELETE`). You can review the generated SQL and confirm or cancel.
+## SQL Preview
 
-## Sorting
+<Callout type="info">
+Before saving, DBX shows a preview of the exact `UPDATE`, `INSERT`, or `DELETE` statements that will be executed. Review and confirm before committing.
+</Callout>
 
-Click a column header to sort by that column. Click again to toggle between ascending and descending order.
+This prevents accidental data modifications and gives you full visibility into what will change.
 
-## Search and Filtering
+## Sorting and Filtering
 
-- **Search** -- Use the search bar to find text across all visible columns.
-- **WHERE Filter** -- Apply a custom `WHERE` clause to filter data at the database level. This is more efficient than client-side search for large tables because only matching rows are fetched.
+- **Sort** — Click a column header to sort ascending or descending
+- **Search** — Use the search bar to find text across all visible columns
+- **WHERE Filter** — Apply a custom `WHERE` clause for database-level filtering. More efficient than client-side search for large tables
 
 ## Column Resize and Row Numbers
 
-- Drag column borders to resize columns to your preferred width.
-- Row numbers are displayed in the leftmost column for easy reference.
+- Drag column borders to resize columns
+- Row numbers are displayed in the leftmost column
 
 ## Export
 
-Export the current result set in one of the following formats:
-
 | Format | Description |
 |---|---|
-| CSV | Comma-separated values, compatible with Excel and other spreadsheet tools |
+| CSV | Comma-separated values, compatible with Excel and spreadsheet tools |
 | JSON | Array of objects, suitable for use in code or APIs |
 | Markdown | Markdown table, useful for pasting into documentation or chat |
-
-Use the export button in the grid toolbar and select the desired format.
diff --git a/docs/content/docs/data-transfer.cn.mdx b/docs/content/docs/data-transfer.cn.mdx
index b7e0ec58a9..360a0f4626 100644
--- a/docs/content/docs/data-transfer.cn.mdx
+++ b/docs/content/docs/data-transfer.cn.mdx
@@ -1,33 +1,43 @@
 ---
 title: 数据传输
-description: 在不同数据库引擎之间传输数据，支持跨引擎迁移。
+description: 跨引擎数据迁移，MySQL → PostgreSQL、SQLite → SQL Server，自动处理类型映射。
 ---
 
-DBX 支持在不同数据库引擎之间传输数据，例如将 MySQL 中的数据迁移到 PostgreSQL，或从 SQLite 导入数据到 SQL Server。
+<Callout type="info">
+跨数据库引擎数据迁移，自动处理类型映射和语法差异。MySQL 到 PostgreSQL，SQLite 到 SQL Server，开箱即用。
+</Callout>
 
-## 使用方式
+## 典型场景
 
-1. 打开数据传输功能
-2. 选择**源连接**和**目标连接**（可以是不同类型的数据库引擎）
-3. 选择要传输的表
-4. 点击"开始传输"
+- **跨引擎迁移** — MySQL → PostgreSQL、SQLite → SQL Server
+- **环境数据同步** — 从生产库拉取数据到开发环境
+- **数据整合** — 将多个数据源的数据汇集到一个数据库
 
-DBX 会自动处理不同数据库之间的类型映射和语法差异。
+## 使用流程
 
-## 选择要传输的表
-
-你可以选择传输源数据库中的全部表，也可以手动勾选需要传输的特定表。对于不需要迁移的表，取消勾选即可跳过。
+<Steps>
+  <Step>
+    ### 选择源和目标
+    选择**源连接**和**目标连接**，可以是不同类型的数据库引擎。
+  </Step>
+  <Step>
+    ### 选择要传输的表
+    选择传输全部表，或手动勾选需要传输的特定表。
+  </Step>
+  <Step>
+    ### 开始传输
+    点击"开始传输"，DBX 自动处理类型映射和语法差异。
+  </Step>
+</Steps>
 
 ## 进度追踪
 
-传输过程中，DBX 会实时显示：
+传输过程中，DBX 实时显示：
 
 - 当前正在传输的表名
 - 已传输的行数
 - 整体传输进度
 
-你可以随时查看传输状态，了解剩余工作量。
-
 ## 错误处理
 
 如果传输过程中遇到错误（如类型不兼容、约束冲突等），DBX 会：
diff --git a/docs/content/docs/data-transfer.mdx b/docs/content/docs/data-transfer.mdx
index ba71b28e72..736e12936c 100644
--- a/docs/content/docs/data-transfer.mdx
+++ b/docs/content/docs/data-transfer.mdx
@@ -1,23 +1,34 @@
 ---
 title: Data Transfer
-description: Move data between database connections, even across different database engines.
+description: Cross-engine data migration with automatic type mapping. MySQL to PostgreSQL, SQLite to SQL Server.
 ---
 
-# Data Transfer
+<Callout type="info">
+Cross-engine data migration with automatic type mapping and syntax adaptation. MySQL to PostgreSQL, SQLite to SQL Server — it just works.
+</Callout>
 
-Data Transfer moves data between two database connections, even when they use different database engines. This is useful for migrating data, populating a development environment, or consolidating data from multiple sources.
+## Use Cases
 
-## Setting Up a Transfer
+- **Cross-engine migration** — MySQL → PostgreSQL, SQLite → SQL Server
+- **Environment sync** — Pull production data into your dev environment
+- **Data consolidation** — Merge data from multiple sources into one database
 
-1. Select the **source** connection and database.
-2. Select the **target** connection and database.
-3. Choose the tables you want to transfer.
+## Workflow
 
-You can transfer all tables at once or pick a subset. DBX handles the necessary type mapping between different database engines automatically.
-
-## Cross-Engine Support
-
-Data Transfer works across different database engines. For example, you can transfer data from MySQL to PostgreSQL, or from SQLite to SQL Server. DBX translates data types and adapts insert statements as needed for the target engine.
+<Steps>
+  <Step>
+    ### Select Source and Target
+    Choose the **source** and **target** connections. They can be different database engines.
+  </Step>
+  <Step>
+    ### Choose Tables
+    Transfer all tables at once, or pick a subset.
+  </Step>
+  <Step>
+    ### Start Transfer
+    Click "Start Transfer". DBX handles type mapping and syntax differences automatically.
+  </Step>
+</Steps>
 
 ## Progress Tracking
 
@@ -27,8 +38,10 @@ During the transfer, a progress indicator shows:
 - How many rows have been transferred so far
 - The overall progress across all selected tables
 
-This lets you monitor long-running transfers without guessing how much work remains.
-
 ## Error Handling
 
-If an error occurs during transfer (for example, a type incompatibility or a constraint violation), DBX reports the error with details about which table and row caused the problem. The transfer can be reviewed and retried after correcting the issue.
+If an error occurs during transfer (type incompatibility, constraint violation, etc.), DBX:
+
+- Logs the error with details about which table caused the problem
+- Continues transferring other tables without stopping the entire job
+- Shows a summary of all errors after the transfer completes
diff --git a/docs/content/docs/database-export.cn.mdx b/docs/content/docs/database-export.cn.mdx
index 9ff890f2b3..e230069bf6 100644
--- a/docs/content/docs/database-export.cn.mdx
+++ b/docs/content/docs/database-export.cn.mdx
@@ -1,22 +1,20 @@
 ---
 title: 数据库导出
-description: 将整个数据库导出为 SQL 文件，包含表结构和数据，适用于备份和迁移。
+description: 将数据库导出为 SQL 文件，包含表结构和数据，支持行数限制。
 ---
 
-DBX 支持将整个数据库导出为 SQL 文件，包含表结构（DDL）和数据，适用于数据库备份和迁移。
+<Callout type="info">
+一键导出完整数据库：表结构（DDL）+ 数据（INSERT），批量 INSERT 提高导入效率，可配置行数限制。
+</Callout>
 
 ## 导出内容
 
-导出的 SQL 文件包含：
+- **表结构（DDL）** — `CREATE TABLE` 语句，包括列定义、主键、索引、约束等
+- **表数据** — 以批量 `INSERT` 语句的形式导出
 
-- **表结构（DDL）** -- `CREATE TABLE` 语句，包括列定义、主键、索引、约束等
-- **表数据** -- 以 `INSERT` 语句的形式导出表中的数据
+## 批量 INSERT
 
-## 批量 INSERT 语句
-
-为了提高导入效率，DBX 会将数据生成为批量 `INSERT` 语句，每条语句包含多行数据，减少执行次数，加快数据恢复速度。
-
-示例：
+为了提高导入效率，DBX 将数据生成为批量 `INSERT` 语句：
 
 ```sql
 INSERT INTO users (id, name, email) VALUES
@@ -25,14 +23,33 @@ INSERT INTO users (id, name, email) VALUES
 (3, '王五', 'wangwu@example.com');
 ```
 
-## 配置选项
+## 行数限制
 
-### 行数限制
+可以配置每张表导出的最大行数，适用于：
 
-你可以配置每张表导出的最大行数。这在以下场景中非常有用：
-
-- 只需要导出表结构和少量示例数据时
-- 表中数据量过大，完整导出文件体积过大时
-- 需要创建用于开发或测试的精简数据集时
+- 只需要表结构和少量示例数据
+- 表中数据量过大，完整导出文件体积过大
+- 创建用于开发或测试的精简数据集
 
 设置为 0 或留空表示导出全部数据。
+
+## 使用方式
+
+<Steps>
+  <Step>
+    ### 选择数据库
+    选择要导出的连接和数据库。
+  </Step>
+  <Step>
+    ### 配置选项
+    设置行数限制（可选）。
+  </Step>
+  <Step>
+    ### 选择保存位置
+    选择导出文件的保存路径。
+  </Step>
+  <Step>
+    ### 开始导出
+    导出的 `.sql` 文件可以通过 [SQL 文件执行](/cn/docs/sql-file) 功能重新导入。
+  </Step>
+</Steps>
diff --git a/docs/content/docs/database-export.mdx b/docs/content/docs/database-export.mdx
index 2cb9e0fc2f..41120ef066 100644
--- a/docs/content/docs/database-export.mdx
+++ b/docs/content/docs/database-export.mdx
@@ -1,22 +1,20 @@
 ---
 title: Database Export
-description: Generate SQL dump files with table definitions and row data.
+description: Export database structure and data as SQL dump with batched INSERT and configurable row limits.
 ---
 
-# Database Export
-
-Database Export generates a SQL dump of your database, including table definitions (DDL) and row data. The output is a `.sql` file that can be used to recreate the database or transfer it to another environment.
+<Callout type="info">
+One-click database export: DDL + data as batched INSERT statements. Configurable row limits for dev/test datasets.
+</Callout>
 
 ## What Gets Exported
 
-The export includes:
-
-- **DDL (Data Definition Language)** -- `CREATE TABLE` statements for all tables, including columns, types, defaults, constraints, and indexes.
-- **Data** -- `INSERT` statements for all rows in each table.
+- **DDL** — `CREATE TABLE` statements with columns, types, defaults, constraints, and indexes
+- **Data** — Row data as batched `INSERT` statements
 
 ## Batched INSERT Statements
 
-To keep the export file manageable and compatible with database import tools, row data is written as batched `INSERT` statements. Instead of one `INSERT` per row, multiple rows are grouped into a single statement:
+Multiple rows are grouped into a single statement for smaller file size and faster imports:
 
 ```sql
 INSERT INTO users (id, name, email) VALUES
@@ -25,19 +23,33 @@ INSERT INTO users (id, name, email) VALUES
   (3, 'Carol', 'carol@example.com');
 ```
 
-This reduces file size and improves import performance.
-
 ## Configurable Row Limit
 
-You can set a maximum number of rows to export per table. This is useful when you need a representative sample of data rather than a full dump, or when working with very large tables where a complete export would be impractical.
+Set a maximum number of rows to export per table. Useful for:
 
-Set the row limit to `0` or leave it blank to export all rows.
+- Exporting structure with sample data only
+- Working with very large tables where full export is impractical
+- Creating lightweight dev/test datasets
+
+Set to `0` or leave blank to export all rows.
 
 ## Usage
 
-1. Select the connection and database to export.
-2. Configure the row limit (optional).
-3. Choose the output file location.
-4. Start the export.
-
-The generated `.sql` file can be executed in DBX using the [SQL File Execution](/docs/sql-file) feature, or in any compatible database client.
+<Steps>
+  <Step>
+    ### Select Database
+    Choose the connection and database to export.
+  </Step>
+  <Step>
+    ### Configure Options
+    Set the row limit (optional).
+  </Step>
+  <Step>
+    ### Choose Output Location
+    Select where to save the export file.
+  </Step>
+  <Step>
+    ### Start Export
+    The generated `.sql` file can be re-imported using the [SQL File Execution](/en/docs/sql-file) feature.
+  </Step>
+</Steps>
diff --git a/docs/content/docs/databases.cn.mdx b/docs/content/docs/databases.cn.mdx
index 6dce0486ca..ef8431fd87 100644
--- a/docs/content/docs/databases.cn.mdx
+++ b/docs/content/docs/databases.cn.mdx
@@ -1,9 +1,11 @@
 ---
 title: 数据库支持
-description: DBX 通过 Rust 原生驱动支持 25+ 种数据库。
+description: 通过 Rust 原生驱动支持 25+ 种数据库，无 JDBC 依赖。
 ---
 
-DBX 通过 Rust 原生驱动支持 25+ 种数据库。
+<Callout type="info">
+Rust 原生驱动，不依赖 JDBC。MySQL / PostgreSQL 兼容数据库开箱即用。
+</Callout>
 
 ## 完整支持
 
@@ -24,7 +26,7 @@ DBX 通过 Rust 原生驱动支持 25+ 种数据库。
 
 ## MySQL 兼容
 
-以下数据库使用 MySQL 协议，通过 MySQL 驱动连接：
+以下数据库使用 MySQL 协议，通过 MySQL 驱动连接，开箱即用：
 
 | 数据库 | 默认端口 |
 |---|---|
@@ -41,13 +43,13 @@ DBX 通过 Rust 原生驱动支持 25+ 种数据库。
 
 以下数据库使用 PostgreSQL 协议，通过 PostgreSQL 驱动连接：
 
-| 数据库 | 默认端口 | 备注 |
-|---|---|---|
-| openGauss | 5432 | |
-| KingBase（人大金仓） | 54321 | |
-| Vastbase | 5432 | |
-| Redshift | 5439 | |
-| CockroachDB | 26257 | |
+| 数据库 | 默认端口 |
+|---|---|
+| openGauss | 5432 |
+| KingBase（人大金仓） | 54321 |
+| Vastbase | 5432 |
+| Redshift | 5439 |
+| CockroachDB | 26257 |
 
 ## ODBC 数据库
 
@@ -57,27 +59,27 @@ DM（达梦）通过 ODBC 连接，需要在系统上安装对应的 ODBC 驱动
 
 达梦 DM8 通过 ODBC 驱动连接。默认端口：**5236**，默认用户：**SYSDBA**。
 
-**Linux 配置：**
+<Tabs groupId="dm-platform" items={['Linux', 'Windows', 'macOS']}>
+  <Tab value="Linux">
+    ```bash
+    # 安装 unixODBC
+    sudo apt install unixodbc
 
-```bash
-# 安装 unixODBC
-sudo apt install unixodbc
+    # 安装达梦数据库（安装包含 ODBC 驱动）
+    # 下载地址：https://eco.dameng.com/download/
 
-# 安装达梦数据库（安装包含 ODBC 驱动）
-# 下载地址：https://eco.dameng.com/download/
-
-# 在 /etc/odbcinst.ini 中注册驱动
-sudo tee -a /etc/odbcinst.ini << 'EOF'
-[DM8 ODBC DRIVER]
-Description = DM8 ODBC Driver
-Driver = /opt/dmdbms/bin/libdodbc.so
-EOF
-```
-
-**Windows 配置：**
-
-达梦安装程序会自动注册 ODBC 驱动，无需手动配置。
-
-**macOS 配置：**
-
-达梦暂未提供 macOS 原生 ODBC 驱动。开发/测试建议使用 Linux 环境连接。
+    # 在 /etc/odbcinst.ini 中注册驱动
+    sudo tee -a /etc/odbcinst.ini << 'EOF'
+    [DM8 ODBC DRIVER]
+    Description = DM8 ODBC Driver
+    Driver = /opt/dmdbms/bin/libdodbc.so
+    EOF
+    ```
+  </Tab>
+  <Tab value="Windows">
+    达梦安装程序会自动注册 ODBC 驱动，无需手动配置。
+  </Tab>
+  <Tab value="macOS">
+    达梦暂未提供 macOS 原生 ODBC 驱动。开发/测试建议使用 Linux 环境连接。
+  </Tab>
+</Tabs>
diff --git a/docs/content/docs/databases.mdx b/docs/content/docs/databases.mdx
index d89601515c..4bf1dac3a5 100644
--- a/docs/content/docs/databases.mdx
+++ b/docs/content/docs/databases.mdx
@@ -1,11 +1,11 @@
 ---
 title: Database Support
-description: DBX supports 25+ database engines through native Rust drivers.
+description: 25+ database engines through native Rust drivers, no JDBC dependency.
 ---
 
-# Database Support
-
-DBX supports 25+ database engines through native Rust drivers.
+<Callout type="info">
+Native Rust drivers, no JDBC dependency. MySQL and PostgreSQL compatible databases work out of the box.
+</Callout>
 
 ## Fully Supported
 
@@ -26,7 +26,7 @@ DBX supports 25+ database engines through native Rust drivers.
 
 ## MySQL Compatible
 
-These databases use MySQL protocol and work with the MySQL driver:
+These databases use MySQL protocol and work with the MySQL driver out of the box:
 
 | Database | Default Port |
 |---|---|
@@ -43,13 +43,13 @@ These databases use MySQL protocol and work with the MySQL driver:
 
 These databases use PostgreSQL protocol and work with the PostgreSQL driver:
 
-| Database | Default Port | Notes |
-|---|---|---|
-| openGauss | 5432 | |
-| KingBase | 54321 | |
-| Vastbase | 5432 | |
-| Redshift | 5439 | |
-| CockroachDB | 26257 | |
+| Database | Default Port |
+|---|---|
+| openGauss | 5432 |
+| KingBase | 54321 |
+| Vastbase | 5432 |
+| Redshift | 5439 |
+| CockroachDB | 26257 |
 
 ## ODBC Databases
 
@@ -59,27 +59,27 @@ DM (Dameng) connects through ODBC, which requires an ODBC driver installed on yo
 
 DM8 connects via the DM ODBC driver. Default port: **5236**, default user: **SYSDBA**.
 
-**Linux setup:**
+<Tabs groupId="dm-platform" items={['Linux', 'Windows', 'macOS']}>
+  <Tab value="Linux">
+    ```bash
+    # Install unixODBC
+    sudo apt install unixodbc
 
-```bash
-# Install unixODBC
-sudo apt install unixodbc
+    # Install DM8 (includes ODBC driver)
+    # Download from https://eco.dameng.com/download/
 
-# Install DM8 (includes ODBC driver)
-# Download from https://eco.dameng.com/download/
-
-# Register the driver in /etc/odbcinst.ini
-sudo tee -a /etc/odbcinst.ini << 'EOF'
-[DM8 ODBC DRIVER]
-Description = DM8 ODBC Driver
-Driver = /opt/dmdbms/bin/libdodbc.so
-EOF
-```
-
-**Windows setup:**
-
-The DM8 installer automatically registers the ODBC driver. No manual configuration needed.
-
-**macOS setup:**
-
-DM does not provide a native macOS ODBC driver. For development/testing, DM is best accessed from Linux.
+    # Register the driver in /etc/odbcinst.ini
+    sudo tee -a /etc/odbcinst.ini << 'EOF'
+    [DM8 ODBC DRIVER]
+    Description = DM8 ODBC Driver
+    Driver = /opt/dmdbms/bin/libdodbc.so
+    EOF
+    ```
+  </Tab>
+  <Tab value="Windows">
+    The DM8 installer automatically registers the ODBC driver. No manual configuration needed.
+  </Tab>
+  <Tab value="macOS">
+    DM does not provide a native macOS ODBC driver. For development/testing, DM is best accessed from Linux.
+  </Tab>
+</Tabs>
diff --git a/docs/content/docs/field-lineage.cn.mdx b/docs/content/docs/field-lineage.cn.mdx
index 4b14410f28..1999033d31 100644
--- a/docs/content/docs/field-lineage.cn.mdx
+++ b/docs/content/docs/field-lineage.cn.mdx
@@ -1,37 +1,43 @@
 ---
 title: 字段血缘
-description: 理解数据库中字段之间的关联关系，追踪数据的来源和去向。
+description: 追踪数据库中字段之间的关联关系，理解数据的来源和去向，数据治理必备功能。
 ---
 
-字段血缘功能帮助你理解数据库中字段之间的关联关系，追踪数据的来源和去向。DBX 会从多个维度自动分析字段之间的关联，并标注置信度。
+<Callout type="info">
+大多数数据库工具没有这个功能。DBX 从外键、视图、查询历史等多个维度自动分析字段关联，标注置信度，帮你理解数据的完整流向。
+</Callout>
+
+## 为什么需要字段血缘？
+
+- **数据治理** — 了解每个字段的数据来源，确保数据质量
+- **影响分析** — 修改表结构前，了解哪些下游视图或查询会受影响
+- **新人上手** — 快速理解复杂数据库中表与表之间的关系
 
 ## 关联来源
 
-DBX 通过以下方式检测字段之间的关联关系：
+DBX 通过多种方式检测字段关联，每种方式标注不同的置信度：
 
-### 外键关系（确定置信度）
+### 外键关系（确定）
 
-基于数据库中已定义的外键约束，这是最可靠的关联来源。例如，`orders.user_id` 通过外键指向 `users.id`，这种关联是确定的。
+基于数据库中已定义的外键约束。例如 `orders.user_id → users.id`，这是最可靠的关联来源。
 
 ### 视图引用（高置信度）
 
-分析视图定义中的 SQL 语句，提取视图字段与底层表字段的映射关系。由于视图定义是明确的 SQL 逻辑，这类关联具有较高的置信度。
+分析视图定义中的 SQL 语句，提取视图字段与底层表字段的映射关系。
 
 ### 查询历史引用
 
-从你执行过的 SQL 查询历史中，分析 `JOIN` 条件和 `WHERE` 子句，推断字段之间可能存在的关联。
+从你执行过的 SQL 查询中，分析 `JOIN` 条件和 `WHERE` 子句，推断字段之间可能存在的关联。
 
 ### 同名字段检测
 
-检测不同表中名称相同的字段，提示它们之间可能存在逻辑关联。这类关联的置信度相对较低，需要人工判断。
+检测不同表中名称相同的字段（如多个表中的 `user_id`），提示它们之间可能存在逻辑关联。
 
 ## 搜索与筛选
 
-你可以通过以下方式快速定位关注的关联：
+- **搜索** — 输入表名或字段名，过滤显示相关的血缘关系
+- **按置信度筛选** — 选择只查看特定置信度级别的关联（确定 / 高 / 全部）
 
-- **搜索** -- 输入表名或字段名，过滤显示相关的血缘关系
-- **按置信度筛选** -- 选择只查看特定置信度级别的关联，例如仅显示"确定"和"高"置信度的结果
-
-## 跳转到关联表
+## 跳转导航
 
 在血缘视图中，点击任意关联的表或字段，可以直接跳转到该表的数据浏览或结构查看页面，方便你快速了解上下游数据。
diff --git a/docs/content/docs/field-lineage.mdx b/docs/content/docs/field-lineage.mdx
index af5e49ee82..90188ab10e 100644
--- a/docs/content/docs/field-lineage.mdx
+++ b/docs/content/docs/field-lineage.mdx
@@ -1,11 +1,17 @@
 ---
 title: Field Lineage
-description: Trace column relationships across foreign keys, views, and query history.
+description: Trace column relationships across foreign keys, views, and query history. Essential for data governance.
 ---
 
-# Field Lineage
+<Callout type="info">
+Most database tools don't have this. DBX automatically traces column relationships from foreign keys, views, and query history, with confidence levels — essential for understanding how data flows through your schema.
+</Callout>
 
-Field Lineage helps you understand how columns in your database relate to each other. It traces relationships across foreign keys, views, and query history to give you a complete picture of where data comes from and where it flows.
+## Why Field Lineage?
+
+- **Data governance** — Understand where each column's data comes from and ensure data quality
+- **Impact analysis** — Before changing a table structure, see which downstream views or queries are affected
+- **Onboarding** — Quickly understand relationships across tables in a complex database
 
 ## Relationship Sources
 
@@ -13,27 +19,25 @@ DBX discovers column relationships from multiple sources, each with a different
 
 ### Foreign Key Relationships (Certain)
 
-Relationships defined by foreign key constraints in the database schema. These are authoritative and marked with **certain** confidence because they are explicitly declared in the schema.
+Relationships defined by foreign key constraints. For example, `orders.user_id → users.id`. These are authoritative and the most reliable source.
 
 ### View References (Likely)
 
-When a view references columns from underlying tables, DBX traces those references. These relationships are marked with **likely** confidence because they are derived from view definitions rather than explicit constraints.
+DBX analyzes view definitions to trace which columns in the view map back to columns in the underlying tables.
 
 ### Query History References
 
-DBX analyzes your local query history to identify columns that are frequently joined or referenced together. These relationships are inferred from usage patterns.
+DBX analyzes your local query history to identify columns that are frequently joined or referenced together in `JOIN` and `WHERE` clauses.
 
 ### Same-Name Column Detection
 
-Columns that share the same name across different tables are flagged as potential relationships. This heuristic is useful for discovering implicit conventions (such as `user_id` appearing in multiple tables) that are not enforced by foreign keys.
+Columns that share the same name across different tables (e.g., `user_id` appearing in multiple tables) are flagged as potential relationships.
 
 ## Searching and Filtering
 
-The lineage panel provides:
-
-- **Search** -- Filter relationships by table name or column name.
-- **Confidence filter** -- Show only relationships at a specific confidence level (certain, likely, or all). This lets you focus on verified relationships or explore speculative ones.
+- **Search** — Filter relationships by table name or column name
+- **Confidence filter** — Show only relationships at a specific confidence level (certain, likely, or all)
 
 ## Click-Through Navigation
 
-Click any related table or column in the lineage view to navigate directly to it. This opens the target table in the Data Grid or Schema Browser, making it easy to follow data relationships across your schema without manually searching.
+Click any related table or column in the lineage view to navigate directly to it in the Data Grid or Schema Browser.
diff --git a/docs/content/docs/getting-started.cn.mdx b/docs/content/docs/getting-started.cn.mdx
index 2160c306f4..d22ab0fde8 100644
--- a/docs/content/docs/getting-started.cn.mdx
+++ b/docs/content/docs/getting-started.cn.mdx
@@ -5,74 +5,118 @@ description: 安装 DBX 并创建你的第一个数据库连接。
 
 ## 安装
 
-从 [Releases](https://github.com/t8y2/dbx/releases) 页面下载最新版本。
+<Tabs groupId="platform" items={['macOS', 'Windows', 'Linux', 'Docker']}>
+  <Tab value="macOS">
+    **Homebrew（推荐）：**
 
-### Homebrew (macOS)
+    ```bash
+    brew install --cask t8y2/tap/dbx
+    ```
 
-```bash
-brew install --cask t8y2/tap/dbx
-```
+    更新：
+    ```bash
+    brew upgrade --cask t8y2/tap/dbx
+    ```
 
-更新：
-```bash
-brew upgrade --cask t8y2/tap/dbx
-```
+    也可以从 [Releases](https://github.com/t8y2/dbx/releases) 页面下载 `.dmg` 安装包。
+  </Tab>
+  <Tab value="Windows">
+    **Scoop（推荐）：**
 
-### Scoop (Windows)
+    ```bash
+    scoop bucket add dbx https://github.com/t8y2/scoop-bucket
+    scoop install dbx
+    ```
 
-```bash
-scoop bucket add dbx https://github.com/t8y2/scoop-bucket
-scoop install dbx
-```
+    更新：
+    ```bash
+    scoop update dbx
+    ```
 
-更新：
-```bash
-scoop update dbx
-```
+    也可以从 [Releases](https://github.com/t8y2/dbx/releases) 页面下载 `.msi` 安装包。
+  </Tab>
+  <Tab value="Linux">
+    从 [Releases](https://github.com/t8y2/dbx/releases) 页面下载对应的安装包（`.deb` / `.AppImage`）。
+  </Tab>
+  <Tab value="Docker">
+    通过 Docker 部署 DBX，适合团队共享和服务器环境：
 
-### Docker 自托管
+    ```bash
+    docker run -d --name dbx -p 4224:4224 -v dbx-data:/app/data t8y2/dbx
+    ```
 
-你也可以通过 Docker 部署 DBX，适合团队共享和服务器环境：
+    部署后通过浏览器访问 `http://localhost:4224` 即可使用。
 
-```bash
-docker run -d --name dbx -p 4224:4224 -v dbx-data:/app/data t8y2/dbx
-```
+    **Docker Compose：**
 
-部署后通过浏览器访问 `http://localhost:4224` 即可使用。
+    ```yaml
+    services:
+      dbx:
+        image: t8y2/dbx
+        ports:
+          - "4224:4224"
+        volumes:
+          - dbx-data:/app/data
+        restart: unless-stopped
+
+    volumes:
+      dbx-data:
+    ```
+  </Tab>
+</Tabs>
 
 ## 创建第一个连接
 
-1. 点击工具栏的 **新建连接**
-2. 选择数据库类型（MySQL、PostgreSQL 等）
-3. 填写主机、端口、用户名、密码
-4. 点击 **测试** 验证连接
-5. 点击 **保存并连接**
+<Steps>
+  <Step>
+    ### 新建连接
+    点击工具栏的 **新建连接** 按钮。
+  </Step>
+  <Step>
+    ### 选择数据库类型
+    选择你要连接的数据库类型（MySQL、PostgreSQL、SQLite 等）。
+  </Step>
+  <Step>
+    ### 填写连接信息
+    填写主机、端口、用户名、密码。如需通过跳板机连接，可启用 [SSH 隧道](/cn/docs/ssh-tunnel)。
+  </Step>
+  <Step>
+    ### 测试并保存
+    点击 **测试** 验证连接是否正常，然后点击 **保存并连接**。
+  </Step>
+</Steps>
+
+<Callout type="info">
+连接密码存储在系统钥匙串中（macOS Keychain / Windows 凭据管理器 / Linux Secret Service），不会明文保存在配置文件中。
+</Callout>
 
 ## 开发环境搭建
 
+如果你想从源码运行 DBX，请参考以下步骤。
+
 ### 环境要求
 
 - [Node.js](https://nodejs.org/) >= 18
 - [pnpm](https://pnpm.io/)
 - [Rust](https://www.rust-lang.org/tools/install) >= 1.77
 
-#### 系统依赖
+### 系统依赖
 
-**macOS：**
-
-```bash
-brew install unixodbc
-```
-
-**Linux (Ubuntu/Debian)：**
-
-```bash
-sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev libappindicator3-dev librsvg2-dev patchelf libssl-dev unixodbc-dev
-```
-
-**Windows：**
-
-无需额外安装（ODBC 已内置于 Windows）。
+<Tabs groupId="dev-platform" items={['macOS', 'Linux', 'Windows']}>
+  <Tab value="macOS">
+    ```bash
+    brew install unixodbc
+    ```
+  </Tab>
+  <Tab value="Linux">
+    ```bash
+    sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev libappindicator3-dev librsvg2-dev patchelf libssl-dev unixodbc-dev
+    ```
+  </Tab>
+  <Tab value="Windows">
+    无需额外安装（ODBC 已内置于 Windows）。
+  </Tab>
+</Tabs>
 
 ### 运行
 
diff --git a/docs/content/docs/getting-started.mdx b/docs/content/docs/getting-started.mdx
index cba3812e79..813d6969aa 100644
--- a/docs/content/docs/getting-started.mdx
+++ b/docs/content/docs/getting-started.mdx
@@ -3,94 +3,120 @@ title: Getting Started
 description: Install DBX and create your first database connection.
 ---
 
-# Getting Started
-
 ## Install
 
-Download the latest release from the [Releases](https://github.com/t8y2/dbx/releases) page.
+<Tabs groupId="platform" items={['macOS', 'Windows', 'Linux', 'Docker']}>
+  <Tab value="macOS">
+    **Homebrew (recommended):**
 
-### Homebrew (macOS)
+    ```bash
+    brew install --cask t8y2/tap/dbx
+    ```
 
-```bash
-brew install --cask t8y2/tap/dbx
-```
+    Update:
+    ```bash
+    brew upgrade --cask t8y2/tap/dbx
+    ```
 
-Update:
-```bash
-brew upgrade --cask t8y2/tap/dbx
-```
+    You can also download the `.dmg` installer from the [Releases](https://github.com/t8y2/dbx/releases) page.
+  </Tab>
+  <Tab value="Windows">
+    **Scoop (recommended):**
 
-### Scoop (Windows)
+    ```bash
+    scoop bucket add dbx https://github.com/t8y2/scoop-bucket
+    scoop install dbx
+    ```
 
-```bash
-scoop bucket add dbx https://github.com/t8y2/scoop-bucket
-scoop install dbx
-```
+    Update:
+    ```bash
+    scoop update dbx
+    ```
 
-Update:
-```bash
-scoop update dbx
-```
+    You can also download the `.msi` installer from the [Releases](https://github.com/t8y2/dbx/releases) page.
+  </Tab>
+  <Tab value="Linux">
+    Download the appropriate package (`.deb` / `.AppImage`) from the [Releases](https://github.com/t8y2/dbx/releases) page.
+  </Tab>
+  <Tab value="Docker">
+    Run DBX as a self-hosted web application using Docker:
 
-### Docker (Self-Hosted)
+    ```bash
+    docker run -d --name dbx -p 4224:4224 -v dbx-data:/app/data t8y2/dbx
+    ```
 
-You can run DBX as a self-hosted web application using Docker:
+    Then open `http://localhost:4224` in your browser.
 
-```bash
-docker run -d --name dbx -p 4224:4224 -v dbx-data:/app/data t8y2/dbx
-```
+    **Docker Compose:**
 
-Then open `http://localhost:4224` in your browser.
+    ```yaml
+    services:
+      dbx:
+        image: t8y2/dbx
+        ports:
+          - "4224:4224"
+        volumes:
+          - dbx-data:/app/data
+        restart: unless-stopped
 
-For Docker Compose:
-
-```yaml
-services:
-  dbx:
-    image: t8y2/dbx
-    ports:
-      - "4224:4224"
     volumes:
-      - dbx-data:/app/data
-    restart: unless-stopped
-
-volumes:
-  dbx-data:
-```
+      dbx-data:
+    ```
+  </Tab>
+</Tabs>
 
 ## Create Your First Connection
 
-1. Click **New Connection** in the toolbar
-2. Select your database type (MySQL, PostgreSQL, etc.)
-3. Fill in host, port, username, password
-4. Click **Test** to verify the connection
-5. Click **Save & Connect**
+<Steps>
+  <Step>
+    ### New Connection
+    Click the **New Connection** button in the toolbar.
+  </Step>
+  <Step>
+    ### Select Database Type
+    Choose the database engine you want to connect to (MySQL, PostgreSQL, SQLite, etc.).
+  </Step>
+  <Step>
+    ### Enter Connection Details
+    Fill in host, port, username, and password. For databases behind a firewall, enable the [SSH Tunnel](/en/docs/ssh-tunnel).
+  </Step>
+  <Step>
+    ### Test and Save
+    Click **Test** to verify the connection, then click **Save & Connect**.
+  </Step>
+</Steps>
+
+<Callout type="info">
+Connection passwords are stored in your system keyring (macOS Keychain / Windows Credential Manager / Linux Secret Service), never as plain text in config files.
+</Callout>
 
 ## Development Setup
 
+To run DBX from source:
+
 ### Prerequisites
 
 - [Node.js](https://nodejs.org/) >= 18
 - [pnpm](https://pnpm.io/)
 - [Rust](https://www.rust-lang.org/tools/install) >= 1.77
 
-#### System Dependencies
+### System Dependencies
 
-**macOS:**
-
-```bash
-brew install unixodbc
-```
-
-**Linux (Ubuntu/Debian):**
-
-```bash
-sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev libappindicator3-dev librsvg2-dev patchelf libssl-dev unixodbc-dev
-```
-
-**Windows:**
-
-No additional dependencies required (ODBC is built into Windows).
+<Tabs groupId="dev-platform" items={['macOS', 'Linux', 'Windows']}>
+  <Tab value="macOS">
+    ```bash
+    brew install unixodbc
+    ```
+  </Tab>
+  <Tab value="Linux">
+    ```bash
+    sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev libappindicator3-dev librsvg2-dev patchelf libssl-dev unixodbc-dev
+    ```
+  </Tab>
+  <Tab value="Windows">
+    No additional dependencies required (ODBC is built into Windows).
+  </Tab>
+</Tabs>
 
 ### Run
 
diff --git a/docs/content/docs/mcp.cn.mdx b/docs/content/docs/mcp.cn.mdx
index 3a82f9c8c7..48beca2d9b 100644
--- a/docs/content/docs/mcp.cn.mdx
+++ b/docs/content/docs/mcp.cn.mdx
@@ -1,11 +1,15 @@
 ---
 title: MCP 集成
-description: 通过 MCP 协议让 AI 编程助手直接查询你的数据库。
+description: 通过 MCP 协议让 Claude Code、Cursor 等 AI 编程助手直接查询你的数据库。
 ---
 
+<Callout type="info">
+一行配置，让 AI 编程助手直接查询你的数据库。支持 Claude Code、Cursor、Windsurf、VS Code Copilot。
+</Callout>
+
 ## 什么是 MCP？
 
-MCP（Model Context Protocol）是一个开放协议，让 AI 编程助手（Claude Code、Cursor 等）能够调用外部工具。DBX 的 MCP Server 把你在 DBX 中配置的数据库连接暴露给 AI 助手，这样你可以用自然语言查询数据库，而不需要手动写 SQL。
+MCP（Model Context Protocol）是一个开放协议，让 AI 编程助手能够调用外部工具。DBX 的 MCP Server 把你在 DBX 中配置的数据库连接暴露给 AI 助手，这样你可以用自然语言查询数据库，AI 自动生成并执行 SQL。
 
 ```
 你："查看 orders 表最近 7 天的订单量趋势"
@@ -17,48 +21,56 @@ AI 助手 → MCP Server → 你的数据库 → 返回结果
 
 ## 快速开始
 
-### 1. 安装
+<Steps>
+  <Step>
+    ### 安装 MCP Server
 
-```bash
-npm install -g @dbx-app/mcp-server
-```
+    ```bash
+    npm install -g @dbx-app/mcp-server
+    ```
+  </Step>
+  <Step>
+    ### 配置 AI 助手
 
-### 2. 配置 AI 助手
+    在你的工作目录创建 `.mcp.json`：
 
-在你的工作目录创建 `.mcp.json`：
-
-```json
-{
-  "mcpServers": {
-    "dbx": {
-      "command": "npx",
-      "args": ["-y", "@dbx-app/mcp-server"]
+    ```json
+    {
+      "mcpServers": {
+        "dbx": {
+          "command": "npx",
+          "args": ["-y", "@dbx-app/mcp-server"]
+        }
+      }
     }
-  }
-}
-```
+    ```
+  </Step>
+  <Step>
+    ### 开始使用
 
-### 3. 开始使用
+    在 AI 助手中直接用自然语言说：
 
-在 AI 助手中直接说：
-
-- "列出我的数据库连接"
-- "查看 local-pg 上有哪些表"
-- "查看 users 表的结构"
-- "查询最近 7 天的订单数量"
-- "打开 orders 表"（需要 DBX 运行中）
+    - "列出我的数据库连接"
+    - "查看 local-pg 上有哪些表"
+    - "查看 users 表的结构"
+    - "查询最近 7 天的订单数量"
+    - "打开 orders 表"（需要 DBX 运行中）
+  </Step>
+</Steps>
 
 ## 支持的 AI 助手
 
-| 助手 | 支持情况 | 配置方式 |
-|---|---|---|
-| Claude Code | 原生支持 | `.mcp.json` |
-| Cursor | 支持 | `.cursor/mcp.json` |
-| Windsurf | 支持 | `.windsurfrules` |
-| VS Code + Copilot | 支持 | MCP 扩展 |
+| 助手 | 配置方式 |
+|---|---|
+| Claude Code | `.mcp.json`（原生支持） |
+| Cursor | `.cursor/mcp.json` |
+| Windsurf | `.windsurfrules` |
+| VS Code + Copilot | MCP 扩展 |
 
 ## 工具列表
 
+DBX MCP Server 提供以下工具，AI 助手会根据你的需求自动调用：
+
 ### `dbx_list_connections`
 
 列出 DBX 中所有已配置的数据库连接。
@@ -85,7 +97,7 @@ npm install -g @dbx-app/mcp-server
 
 ### `dbx_describe_table`
 
-获取表的列定义。
+获取表的列定义，AI 用它来理解你的数据结构。
 
 | 参数 | 必填 | 说明 |
 |---|---|---|
@@ -163,17 +175,23 @@ MCP 查询支持 PostgreSQL 和 MySQL（及兼容数据库：Doris、StarRocks 
 
 ## 常见问题
 
-**MCP Server 连不上数据库**
-- 检查 DBX 中该连接是否能正常连接。MCP Server 使用相同的连接配置和密码。
-
-**`dbx_open_table` 报 "DBX is not running"**
-- 需要先启动 DBX 桌面应用。UI 联动功能依赖 DBX 运行时的本地 HTTP 服务。
-
-**连接名称找不到**
-- 连接名称匹配不区分大小写，但需要和 DBX 中配置的名称一致。用 `dbx_list_connections` 查看所有可用名称。
-
-**查询超时**
-- MCP Server 的查询超时为 30 秒。如果查询较慢，考虑添加索引或简化查询。
+<Accordions>
+  <Accordion title="MCP Server 连不上数据库">
+    检查 DBX 中该连接是否能正常连接。MCP Server 使用相同的连接配置和密码。确认数据库服务正在运行，网络可达。
+  </Accordion>
+  <Accordion title="dbx_open_table 报 'DBX is not running'">
+    需要先启动 DBX 桌面应用。UI 联动功能依赖 DBX 运行时的本地 HTTP 服务（端口 4224）。
+  </Accordion>
+  <Accordion title="连接名称找不到">
+    连接名称匹配不区分大小写，但需要和 DBX 中配置的名称一致。用 `dbx_list_connections` 查看所有可用名称。
+  </Accordion>
+  <Accordion title="查询超时">
+    MCP Server 的查询超时为 30 秒。如果查询较慢，考虑添加索引或简化查询。也可以让 AI 助手先用 `dbx_describe_table` 了解表结构，再生成优化后的查询。
+  </Accordion>
+  <Accordion title="Docker 环境下如何使用 MCP？">
+    Docker 部署的 DBX 同样支持 MCP。MCP Server 会读取 Docker 容器内的连接配置。确保 MCP Server 能访问到 DBX 的配置目录。
+  </Accordion>
+</Accordions>
 
 ## 系统要求
 
diff --git a/docs/content/docs/mcp.mdx b/docs/content/docs/mcp.mdx
index 35ec665aa2..e82f0cba6e 100644
--- a/docs/content/docs/mcp.mdx
+++ b/docs/content/docs/mcp.mdx
@@ -3,11 +3,13 @@ title: MCP Integration
 description: Let AI coding agents query your databases through the Model Context Protocol.
 ---
 
-# MCP Integration
+<Callout type="info">
+One line of config to let AI coding agents query your databases directly. Works with Claude Code, Cursor, Windsurf, and VS Code Copilot.
+</Callout>
 
 ## What is MCP?
 
-MCP (Model Context Protocol) is an open protocol that lets AI coding agents (Claude Code, Cursor, etc.) call external tools. DBX's MCP Server exposes your database connections to AI agents, so you can query databases using natural language without writing SQL manually.
+MCP (Model Context Protocol) is an open protocol that lets AI coding agents call external tools. DBX's MCP Server exposes your database connections to AI agents, so you can query databases using natural language — the AI generates and executes SQL automatically.
 
 ```
 You: "Show me the order volume trend for the last 7 days"
@@ -19,48 +21,56 @@ AI Agent → MCP Server → Your Database → Results
 
 ## Quick Start
 
-### 1. Install
+<Steps>
+  <Step>
+    ### Install the MCP Server
 
-```bash
-npm install -g @dbx-app/mcp-server
-```
+    ```bash
+    npm install -g @dbx-app/mcp-server
+    ```
+  </Step>
+  <Step>
+    ### Configure Your AI Agent
 
-### 2. Configure Your AI Agent
+    Create `.mcp.json` in your working directory:
 
-Create `.mcp.json` in your working directory:
-
-```json
-{
-  "mcpServers": {
-    "dbx": {
-      "command": "npx",
-      "args": ["-y", "@dbx-app/mcp-server"]
+    ```json
+    {
+      "mcpServers": {
+        "dbx": {
+          "command": "npx",
+          "args": ["-y", "@dbx-app/mcp-server"]
+        }
+      }
     }
-  }
-}
-```
+    ```
+  </Step>
+  <Step>
+    ### Start Using
 
-### 3. Start Using
+    Just ask your AI agent in natural language:
 
-Just ask your AI agent:
-
-- "List my database connections"
-- "Show the tables in my local-pg connection"
-- "Describe the users table"
-- "Query the average salary from employees"
-- "Open the orders table" (requires DBX running)
+    - "List my database connections"
+    - "Show the tables in my local-pg connection"
+    - "Describe the users table"
+    - "Query the average salary from employees"
+    - "Open the orders table" (requires DBX running)
+  </Step>
+</Steps>
 
 ## Supported AI Agents
 
-| Agent | Status | Configuration |
-|---|---|---|
-| Claude Code | Native | `.mcp.json` |
-| Cursor | Supported | `.cursor/mcp.json` |
-| Windsurf | Supported | `.windsurfrules` |
-| VS Code + Copilot | Supported | MCP extension |
+| Agent | Configuration |
+|---|---|
+| Claude Code | `.mcp.json` (native support) |
+| Cursor | `.cursor/mcp.json` |
+| Windsurf | `.windsurfrules` |
+| VS Code + Copilot | MCP extension |
 
 ## Tools
 
+DBX MCP Server provides the following tools. Your AI agent calls them automatically based on your requests:
+
 ### `dbx_list_connections`
 
 List all database connections configured in DBX.
@@ -87,7 +97,7 @@ List tables and views for a connection.
 
 ### `dbx_describe_table`
 
-Get column definitions for a table.
+Get column definitions for a table. The AI uses this to understand your data structure before generating queries.
 
 | Parameter | Required | Description |
 |---|---|---|
@@ -125,7 +135,7 @@ Open a table in DBX desktop app UI. **Requires DBX to be running.**
 | `database` | No | Database name |
 | `schema` | No | Schema name |
 
-DBX will open a new tab with the table data and bring the window to front.
+DBX opens a new tab with the table data and brings the window to front.
 
 ### `dbx_execute_and_show`
 
@@ -165,17 +175,23 @@ MCP query support: PostgreSQL, MySQL, and compatible databases (Doris, StarRocks
 
 ## FAQ
 
-**MCP Server can't connect to my database**
-: Check that the connection works in DBX first. The MCP Server uses the same config and credentials.
-
-**`dbx_open_table` says "DBX is not running"**
-: Start the DBX desktop app first. UI integration requires DBX's local HTTP service.
-
-**Connection name not found**
-: Connection name matching is case-insensitive but must match exactly. Use `dbx_list_connections` to see all available names.
-
-**Query timeout**
-: MCP Server has a 30-second query timeout. Consider adding indexes or simplifying your query.
+<Accordions>
+  <Accordion title="MCP Server can't connect to my database">
+    Check that the connection works in DBX first. The MCP Server uses the same config and credentials. Make sure the database is running and network-reachable.
+  </Accordion>
+  <Accordion title="dbx_open_table says 'DBX is not running'">
+    Start the DBX desktop app first. UI integration requires DBX's local HTTP service (port 4224).
+  </Accordion>
+  <Accordion title="Connection name not found">
+    Connection name matching is case-insensitive but must match the name configured in DBX. Use `dbx_list_connections` to see all available names.
+  </Accordion>
+  <Accordion title="Query timeout">
+    MCP Server has a 30-second query timeout. Consider adding indexes or simplifying your query. You can also ask the AI to use `dbx_describe_table` first to understand the schema, then generate an optimized query.
+  </Accordion>
+  <Accordion title="How to use MCP with Docker?">
+    DBX deployed via Docker also supports MCP. The MCP Server reads connection configs from inside the Docker container. Make sure the MCP Server can access DBX's config directory.
+  </Accordion>
+</Accordions>
 
 ## Requirements
 
diff --git a/docs/content/docs/query-editor.cn.mdx b/docs/content/docs/query-editor.cn.mdx
index dc4ff30d3e..de78555be6 100644
--- a/docs/content/docs/query-editor.cn.mdx
+++ b/docs/content/docs/query-editor.cn.mdx
@@ -1,9 +1,11 @@
 ---
 title: 查询编辑器
-description: 基于 CodeMirror 6 的 SQL 查询编辑器，提供语法高亮、智能补全和快捷操作。
+description: 基于 CodeMirror 6 的 SQL 编辑器，语法高亮、智能补全、JOIN 建议和查询历史。
 ---
 
-DBX 内置了基于 CodeMirror 6 的 SQL 查询编辑器，提供语法高亮、智能补全和快捷操作，帮助你高效编写和执行 SQL。
+<Callout type="info">
+基于 CodeMirror 6 构建，深度感知数据库元数据，SQL 编写体验媲美 IDE。
+</Callout>
 
 ## 语法高亮
 
@@ -11,25 +13,27 @@ DBX 内置了基于 CodeMirror 6 的 SQL 查询编辑器，提供语法高亮、
 
 ## SQL 自动补全
 
-在编辑器中输入时，DBX 会自动弹出补全建议，支持以下内容：
+在编辑器中输入时，DBX 会自动弹出补全建议：
 
-- **关键字** -- `SELECT`、`FROM`、`WHERE`、`GROUP BY` 等 SQL 关键字
-- **表名** -- 当前数据库中的所有表和视图
-- **字段名** -- 根据已输入的表名，自动补全对应的字段
-- **JOIN 补全** -- 输入 `JOIN` 后，自动建议可关联的表及关联条件
+- **关键字** — `SELECT`、`FROM`、`WHERE`、`GROUP BY` 等 SQL 关键字
+- **表名** — 当前数据库中的所有表和视图
+- **字段名** — 根据已输入的表名，自动补全对应的字段
+- **JOIN 补全** — 输入 `JOIN` 后，自动建议可关联的表及基于外键的关联条件
 
 补全列表会随着输入内容实时过滤，按 `Tab` 或 `Enter` 即可确认选择。
 
 ## 执行查询
 
-DBX 提供多种执行方式：
+<Callout type="info">
+快捷键：`Cmd+Enter`（macOS）/ `Ctrl+Enter`（Windows/Linux）。选中文本时，仅执行选中部分。
+</Callout>
 
 | 操作 | 快捷键 |
 |---|---|
-| 执行当前编辑器中的全部 SQL | `Cmd+Enter`（macOS）/ `Ctrl+Enter`（Windows/Linux） |
-| 仅执行选中的 SQL 片段 | 先选中文本，再按 `Cmd+Enter` |
+| 执行全部 SQL | `Cmd+Enter` / `Ctrl+Enter` |
+| 执行选中的 SQL | 先选中文本，再按 `Cmd+Enter` / `Ctrl+Enter` |
 
-执行结果会显示在编辑器下方的结果面板中，包括返回的数据行、执行耗时和影响行数。
+执行结果会显示在编辑器下方的数据表格中，包括返回的数据行、执行耗时和影响行数。
 
 ## SQL 格式化
 
@@ -37,8 +41,9 @@ DBX 提供多种执行方式：
 
 ## 查询历史
 
-DBX 会自动记录你执行过的 SQL 语句。你可以：
+DBX 会自动记录你执行过的 SQL 语句：
 
 - 在查询历史面板中浏览之前执行过的所有 SQL
 - 点击某条历史记录，将其填入编辑器重新执行
 - 按时间顺序查看历史记录
+- 每个连接独立记录，切换连接后只显示该连接的历史
diff --git a/docs/content/docs/query-editor.mdx b/docs/content/docs/query-editor.mdx
index 4e5cc3abdf..0df2d332a7 100644
--- a/docs/content/docs/query-editor.mdx
+++ b/docs/content/docs/query-editor.mdx
@@ -1,37 +1,39 @@
 ---
 title: Query Editor
-description: Write and execute SQL with syntax highlighting, autocomplete, and query history.
+description: CodeMirror 6-powered SQL editor with syntax highlighting, smart autocomplete, JOIN suggestions, and query history.
 ---
 
-# Query Editor
-
-The Query Editor is the primary workspace for writing and executing SQL in DBX. It is built on CodeMirror 6, providing a fast, modern editing experience with deep database awareness.
+<Callout type="info">
+Built on CodeMirror 6 with deep database metadata awareness. A SQL editing experience that rivals a full IDE.
+</Callout>
 
 ## Syntax Highlighting
 
-The editor applies language-aware syntax highlighting for SQL. Keywords, identifiers, strings, numbers, and comments are visually distinguished, making queries easier to read and write.
+The editor applies language-aware syntax highlighting for SQL. Keywords, identifiers, strings, numbers, and comments are visually distinguished, making queries easier to read and write. Highlighting rules adapt automatically based on the connected database type.
 
 ## Autocomplete
 
 As you type, the editor suggests completions drawn from your actual database metadata:
 
-- **Keywords** -- standard SQL keywords (`SELECT`, `FROM`, `WHERE`, etc.)
-- **Table names** -- all tables and views visible in the current connection
-- **Column names** -- columns scoped to the tables referenced in your query
-- **JOIN suggestions** -- when typing a `JOIN` clause, the editor suggests related tables and join conditions based on foreign key relationships
+- **Keywords** — standard SQL keywords (`SELECT`, `FROM`, `WHERE`, etc.)
+- **Table names** — all tables and views visible in the current connection
+- **Column names** — columns scoped to the tables referenced in your query
+- **JOIN suggestions** — when typing a `JOIN` clause, the editor suggests related tables and join conditions based on foreign key relationships
 
 Completions appear automatically and can also be triggered manually with the platform shortcut.
 
 ## Executing Queries
 
+<Callout type="info">
+Shortcut: `Cmd+Enter` (macOS) / `Ctrl+Enter` (Windows/Linux). When text is selected, only the selection is executed.
+</Callout>
+
 | Action | Shortcut |
 |---|---|
-| Execute the current query | `Cmd+Enter` (macOS) / `Ctrl+Enter` (Windows/Linux) |
-| Execute selected text | Select text, then `Cmd+Enter` / `Ctrl+Enter` |
+| Execute all SQL | `Cmd+Enter` / `Ctrl+Enter` |
+| Execute selected SQL | Select text, then `Cmd+Enter` / `Ctrl+Enter` |
 
-When no text is selected, the editor executes the full content of the editor. When a portion of text is selected, only that selection is executed. This is useful for running a single statement out of a multi-statement script.
-
-Results appear immediately below the editor in the Data Grid.
+Results appear immediately below the editor in the Data Grid, showing returned rows, execution time, and affected row count.
 
 ## SQL Formatting
 
@@ -39,10 +41,9 @@ Use the format button in the toolbar to auto-format your SQL. The formatter stan
 
 ## Query History
 
-Every executed query is recorded in your local query history. You can open the history panel to:
+Every executed query is recorded in your local query history:
 
-- Browse previously executed queries
+- Browse previously executed queries in the history panel
+- Click any past query to load it back into the editor
 - Search through past queries by keyword
-- Re-open a previous query in the editor with a single click
-
-Query history is stored per connection, so switching connections shows only the relevant history.
+- History is stored per connection — switching connections shows only the relevant history
diff --git a/docs/content/docs/schema-browser.cn.mdx b/docs/content/docs/schema-browser.cn.mdx
index fb2662d061..833d100a1f 100644
--- a/docs/content/docs/schema-browser.cn.mdx
+++ b/docs/content/docs/schema-browser.cn.mdx
@@ -1,43 +1,47 @@
 ---
 title: 结构浏览
-description: 树形结构浏览器，快速浏览和管理数据库中的所有对象。
+description: 树形结构浏览器，搜索、置顶、右键菜单、字段注释、连接颜色标记。
 ---
 
-DBX 提供树形结构浏览器，让你可以快速浏览和管理数据库中的所有对象。
+<Callout type="info">
+树形层级浏览数据库中的所有对象，支持搜索、置顶、字段注释显示和连接颜色标记，多连接多环境轻松区分。
+</Callout>
 
 ## 树形视图
 
-侧边栏以树形层级展示数据库结构，层级关系如下：
+侧边栏以树形层级展示数据库结构：
 
 ```
 连接
  └── 数据库
       └── Schema
            └── 表 / 视图
-                └── 字段
+                └── 字段（类型、约束、默认值）
 ```
 
-点击节点可展开或折叠下级内容。点击表名可直接打开该表的数据浏览视图。
+点击节点展开或折叠，点击表名直接打开数据浏览视图。字段节点会显示数据类型等属性。
 
 ## 搜索与置顶
 
-- **搜索** -- 在侧边栏顶部的搜索框中输入关键词，可快速过滤显示匹配的表、视图或字段
-- **置顶** -- 将常用的表或连接置顶显示，方便快速访问
+- **搜索** — 在侧边栏顶部输入关键词，可跨连接过滤匹配的表、视图或字段
+- **置顶** — 将常用的表或连接置顶显示，不管层级多深都能快速访问
 
 ## 右键上下文菜单
 
-在树形视图中右键点击节点，可以调出上下文菜单，根据节点类型提供不同的操作选项，例如：
+右键点击节点，根据类型提供不同操作：
 
-- 打开表数据
-- 查看表结构
-- 复制表名
-- 刷新节点
-- 删除表
+- **表** — 打开数据、查看结构、复制表名、删除表
+- **字段** — 复制字段名
+- **连接** — 刷新元数据、断开连接
 
 ## 字段注释显示
 
-如果数据库中的字段设置了注释（COMMENT），树形视图中会在字段名旁边显示对应的注释文本，帮助你理解字段含义。
+如果数据库中的字段设置了注释（`COMMENT`），树形视图会在字段名旁边显示注释文本，帮助理解字段含义。
 
 ## 连接颜色标记
 
-你可以为每个数据库连接设置不同的颜色标记。颜色会显示在侧边栏的连接名称旁，便于在多个连接之间快速区分，尤其适用于区分开发环境和生产环境。
+<Callout type="info">
+为每个连接设置颜色标记，开发环境用绿色、生产环境用红色，一眼区分，避免误操作。
+</Callout>
+
+颜色显示在侧边栏的连接名称旁和标签页中，多连接场景下尤其实用。
diff --git a/docs/content/docs/schema-browser.mdx b/docs/content/docs/schema-browser.mdx
index 7d29338e49..eece25022c 100644
--- a/docs/content/docs/schema-browser.mdx
+++ b/docs/content/docs/schema-browser.mdx
@@ -1,11 +1,11 @@
 ---
 title: Schema Browser
-description: Explore database structure with a navigable tree view, search, and context menus.
+description: Tree view with search, pin, context menus, column comments, and connection colors.
 ---
 
-# Schema Browser
-
-The Schema Browser is the sidebar panel that lets you explore the structure of all your connected databases. It presents your database objects in a navigable tree and provides quick actions via context menus.
+<Callout type="info">
+Explore your database objects in a hierarchical tree with search, pin, column comments, and color-coded connections to tell dev from production at a glance.
+</Callout>
 
 ## Tree View
 
@@ -13,35 +13,35 @@ The browser organizes objects in a hierarchical tree:
 
 ```
 Connection
-  +-- Database
-        +-- Schema
-              +-- Tables
-              |     +-- Table
-              |           +-- Column (type, nullable, default)
-              +-- Views
+  └── Database
+        └── Schema
+              └── Tables / Views
+                    └── Columns (type, constraints, defaults)
 ```
 
-Expand any node to drill down into its children. Column entries display their data type and other attributes inline.
+Expand any node to drill down. Click a table name to open it in the Data Grid. Column entries display their data type and attributes inline.
 
 ## Search and Pin
 
-- **Search** -- Use the search field at the top of the sidebar to filter the tree. The filter applies across all connections and matches table names, view names, and column names.
-- **Pin** -- Pin frequently used tables or views to keep them at the top of the sidebar for quick access, regardless of how deep they are in the tree.
+- **Search** — Type in the search field to filter across all connections, matching table names, view names, and column names
+- **Pin** — Pin frequently used tables or views to the top of the sidebar for instant access, regardless of tree depth
 
 ## Context Menus
 
-Right-click any node in the tree to access context-specific actions. Examples include:
+Right-click any node for context-specific actions:
 
-- **Table** -- Open data, open structure, copy table name, drop table
-- **Column** -- Copy column name
-- **Connection** -- Refresh metadata, disconnect
-
-The available actions depend on the type of object selected.
+- **Table** — Open data, open structure, copy table name, drop table
+- **Column** — Copy column name
+- **Connection** — Refresh metadata, disconnect
 
 ## Column Comments
 
-If your database supports column comments (e.g., MySQL `COMMENT`, PostgreSQL `COMMENT ON COLUMN`), the Schema Browser displays them alongside each column. This makes it easy to understand the purpose of columns without leaving the sidebar.
+If your database supports column comments (`COMMENT`), the Schema Browser displays them alongside each column, making it easy to understand column purposes without leaving the sidebar.
 
 ## Connection Colors
 
-Each connection can be assigned a color. The color is displayed as a visual indicator in the tree and in tabs, helping you distinguish between environments (for example, green for development and red for production) at a glance.
+<Callout type="info">
+Assign colors to connections — green for dev, red for production — to tell them apart at a glance and avoid accidental operations on the wrong environment.
+</Callout>
+
+Colors appear next to connection names in the sidebar and in tabs, especially useful when working with multiple connections.
diff --git a/docs/content/docs/schema-diff.cn.mdx b/docs/content/docs/schema-diff.cn.mdx
index 664421a5a2..86917b87f5 100644
--- a/docs/content/docs/schema-diff.cn.mdx
+++ b/docs/content/docs/schema-diff.cn.mdx
@@ -1,32 +1,42 @@
 ---
 title: Schema 对比
-description: 比较两个数据库之间的结构差异，并生成同步 SQL。
+description: 比较两个数据库的结构差异，自动生成同步 SQL，开发与生产环境一键对齐。
 ---
 
-DBX 的 Schema 对比功能可以比较两个数据库之间的结构差异，并生成同步 SQL，帮助你快速对齐数据库结构。
+<Callout type="info">
+跨数据库结构对比，自动生成同步 SQL。无论是开发 vs 生产、还是不同环境之间的数据库结构对齐，一键搞定。
+</Callout>
 
-## 对比两个数据库
+## 典型场景
 
-1. 打开 Schema 对比功能
-2. 分别选择**源数据库**和**目标数据库**连接
-3. 点击"对比"按钮，DBX 将自动分析两个数据库中所有表和字段的差异
+- **开发 vs 生产** — 检查开发环境的 Schema 变更是否已同步到生产
+- **多环境对齐** — 确保 staging、QA、production 的表结构一致
+- **版本迁移** — 对比新旧版本数据库结构，生成迁移脚本
 
-对比结果会以清晰的列表展示：
+## 使用流程
 
-- **仅在源库存在的表** -- 目标库中缺少的表
-- **仅在目标库存在的表** -- 源库中没有的表
-- **结构不同的表** -- 字段类型、默认值、索引等存在差异的表
+<Steps>
+  <Step>
+    ### 选择源和目标
+    分别选择**源数据库**和**目标数据库**连接。可以是不同的服务器，甚至不同的数据库引擎。
+  </Step>
+  <Step>
+    ### 执行对比
+    点击"对比"按钮，DBX 自动分析两个数据库中所有表和字段的差异。
+  </Step>
+  <Step>
+    ### 审查差异
+    对比结果以清晰的列表展示：
+    - **仅在源库存在的表** — 目标库中缺少的表
+    - **仅在目标库存在的表** — 源库中没有的表
+    - **结构不同的表** — 字段类型、默认值、索引等存在差异的表
+  </Step>
+  <Step>
+    ### 生成并执行同步 SQL
+    DBX 根据差异自动生成 `CREATE TABLE`、`ALTER TABLE`、`DROP TABLE` 等 SQL 语句。确认无误后，可以直接在 DBX 中执行。
+  </Step>
+</Steps>
 
-## 生成同步 SQL
-
-对比完成后，DBX 会根据差异自动生成同步 SQL 语句，包括：
-
-- `CREATE TABLE` -- 创建目标库中缺少的表
-- `ALTER TABLE` -- 修改存在差异的列、索引等
-- `DROP TABLE` -- 删除目标库中多余的表（可选）
-
-你可以查看生成的 SQL 内容，确认每条语句的变更是否符合预期。
-
-## 执行同步
-
-确认同步 SQL 无误后，可以直接在 DBX 中执行这些语句，将目标数据库的结构同步为与源数据库一致。无需手动复制 SQL 到其他工具中运行。
+<Callout type="warn">
+Schema 同步可能包含破坏性操作（如删除表或列）。执行前请仔细审查生成的 SQL，建议先备份目标数据库。
+</Callout>
diff --git a/docs/content/docs/schema-diff.mdx b/docs/content/docs/schema-diff.mdx
index e67bd4d9aa..03debc2a36 100644
--- a/docs/content/docs/schema-diff.mdx
+++ b/docs/content/docs/schema-diff.mdx
@@ -1,36 +1,42 @@
 ---
 title: Schema Diff
-description: Compare database schemas and generate SQL to synchronize them.
+description: Compare database schemas, generate sync SQL, and align dev with production in one click.
 ---
 
-# Schema Diff
+<Callout type="info">
+Compare schemas across databases and generate sync SQL. Align dev, staging, and production environments in one click.
+</Callout>
 
-Schema Diff compares the structure of two databases and generates the SQL needed to synchronize them. This is useful for identifying differences between development and production environments, or between any two database instances.
+## Use Cases
 
-## Comparing Schemas
+- **Dev vs Production** — Check whether schema changes in development have been applied to production
+- **Multi-environment alignment** — Ensure staging, QA, and production share the same table structure
+- **Version migration** — Compare old and new database versions and generate migration scripts
 
-To start a comparison:
+## Workflow
 
-1. Open the Schema Diff panel.
-2. Select the **source** connection and database.
-3. Select the **target** connection and database.
-4. Run the comparison.
+<Steps>
+  <Step>
+    ### Select Source and Target
+    Choose the **source** and **target** database connections. They can be on different servers or even different database engines.
+  </Step>
+  <Step>
+    ### Run Comparison
+    Click "Compare" and DBX analyzes all tables and columns across both databases.
+  </Step>
+  <Step>
+    ### Review Differences
+    Results are presented in a clear list:
+    - Tables that exist only in the source
+    - Tables that exist only in the target
+    - Tables with structural differences (column types, defaults, indexes)
+  </Step>
+  <Step>
+    ### Generate and Execute Sync SQL
+    DBX generates `CREATE TABLE`, `ALTER TABLE`, and `DROP TABLE` statements based on the differences. Review and execute them directly in DBX.
+  </Step>
+</Steps>
 
-DBX analyzes both schemas and presents a side-by-side diff of all structural differences, including:
-
-- Tables that exist in one database but not the other
-- Columns that differ in type, default value, or nullability
-- Index and constraint differences
-
-## Generating Sync SQL
-
-After the comparison is complete, DBX generates the SQL statements required to bring the target database in line with the source. This may include `CREATE TABLE`, `ALTER TABLE`, `DROP TABLE`, and related statements depending on the differences found.
-
-You can review the generated SQL before taking any action.
-
-## Executing Sync Directly
-
-Once you have reviewed the generated SQL, you can execute it directly within DBX against the target database. There is no need to copy the SQL to an external tool -- the sync can be completed in a single workflow.
-
-> **Warning:**
-> Schema sync can make destructive changes (such as dropping tables or columns). Always review the generated SQL carefully before executing, and consider backing up the target database first.
+<Callout type="warn">
+Schema sync may include destructive operations (such as dropping tables or columns). Always review the generated SQL carefully and consider backing up the target database first.
+</Callout>
diff --git a/docs/content/docs/sql-file.cn.mdx b/docs/content/docs/sql-file.cn.mdx
index 64a93aa663..cae1549a23 100644
--- a/docs/content/docs/sql-file.cn.mdx
+++ b/docs/content/docs/sql-file.cn.mdx
@@ -1,29 +1,41 @@
 ---
 title: SQL 文件执行
-description: 直接执行 .sql 文件，适用于运行数据库迁移脚本、初始化脚本或批量 SQL 操作。
+description: 直接执行 .sql 文件，智能语句分割，进度追踪，支持取消。
 ---
 
-DBX 支持直接执行 `.sql` 文件，适用于运行数据库迁移脚本、初始化脚本或批量 SQL 操作。
+<Callout type="info">
+直接执行 `.sql` 文件，智能分割语句（正确处理函数、触发器、字符串中的分号），实时显示进度。
+</Callout>
 
 ## 执行 SQL 文件
 
-1. 打开 SQL 文件执行功能
-2. 选择要执行的 `.sql` 文件
-3. 选择目标数据库连接
-4. 点击"执行"
-
-执行过程中会实时显示进度，包括已执行的语句数量和当前状态。
+<Steps>
+  <Step>
+    ### 打开功能
+    打开 SQL 文件执行面板。
+  </Step>
+  <Step>
+    ### 选择文件
+    选择要执行的 `.sql` 文件。
+  </Step>
+  <Step>
+    ### 选择目标
+    选择目标数据库连接。
+  </Step>
+  <Step>
+    ### 执行
+    点击"执行"，实时查看进度。
+  </Step>
+</Steps>
 
 ## 智能语句分割
 
-SQL 文件中通常包含多条语句，DBX 使用智能分割逻辑来正确解析每条语句的边界，能够正确处理以下情况：
+DBX 使用智能分割逻辑来正确解析每条语句的边界：
 
-- **函数和存储过程** -- 包含 `BEGIN...END` 块的语句不会被错误地按分号拆分
-- **触发器定义** -- 使用自定义分隔符的触发器语句能被正确识别
-- **引号内的字符串** -- 字符串中包含的分号不会被当作语句分隔符
-
-这确保了即使是结构复杂的 SQL 文件也能被正确执行。
+- **函数和存储过程** — `BEGIN...END` 块不会被错误地按分号拆分
+- **触发器定义** — 自定义分隔符的触发器语句能被正确识别
+- **引号内的字符串** — 字符串中的分号不会被当作语句分隔符
 
 ## 取消执行
 
-如果 SQL 文件较大或执行时间较长，你可以随时点击"取消"按钮中断执行。已执行的语句不会被回滚，仅停止后续语句的执行。
+SQL 文件较大时，可以随时点击"取消"按钮中断执行。已执行的语句不会被回滚，仅停止后续语句的执行。
diff --git a/docs/content/docs/sql-file.mdx b/docs/content/docs/sql-file.mdx
index e23a389b59..e2581ef3a5 100644
--- a/docs/content/docs/sql-file.mdx
+++ b/docs/content/docs/sql-file.mdx
@@ -1,39 +1,41 @@
 ---
 title: SQL File Execution
-description: Run .sql files directly within DBX with progress tracking and cancellation support.
+description: Run .sql files with smart statement splitting, progress tracking, and cancellation support.
 ---
 
-# SQL File Execution
-
-SQL File Execution lets you run `.sql` files directly within DBX, with progress tracking and the ability to cancel mid-execution. This is useful for running migration scripts, seed data, or database setup files.
+<Callout type="info">
+Execute `.sql` files directly with smart statement splitting (handles functions, triggers, quoted strings), real-time progress tracking, and cancellation.
+</Callout>
 
 ## Running a SQL File
 
-1. Open the SQL File Execution panel.
-2. Select a `.sql` file from your filesystem.
-3. Choose the target connection and database.
-4. Click execute.
-
-## Progress Tracking
-
-During execution, DBX displays:
-
-- The total number of statements detected in the file
-- How many statements have been executed so far
-- The currently executing statement
-
-This gives you visibility into long-running scripts without waiting blindly for completion.
+<Steps>
+  <Step>
+    ### Open the Panel
+    Open the SQL File Execution panel.
+  </Step>
+  <Step>
+    ### Select File
+    Choose a `.sql` file from your filesystem.
+  </Step>
+  <Step>
+    ### Choose Target
+    Select the target connection and database.
+  </Step>
+  <Step>
+    ### Execute
+    Click execute and monitor progress in real time.
+  </Step>
+</Steps>
 
 ## Smart Statement Splitting
 
-DBX parses the SQL file intelligently rather than naively splitting on semicolons. The parser correctly handles:
+DBX parses SQL files intelligently rather than naively splitting on semicolons:
 
-- **Functions and procedures** -- Multi-statement bodies with `BEGIN...END` blocks are treated as a single unit.
-- **Triggers** -- `CREATE TRIGGER` statements with embedded logic are kept intact.
-- **Quoted strings** -- Semicolons inside string literals or identifiers are not treated as statement delimiters.
-
-This ensures that complex SQL files execute correctly without requiring manual editing.
+- **Functions and procedures** — `BEGIN...END` blocks are treated as a single unit
+- **Triggers** — `CREATE TRIGGER` statements with embedded logic are kept intact
+- **Quoted strings** — Semicolons inside string literals are not treated as delimiters
 
 ## Cancelling Execution
 
-If you need to stop execution before the file finishes, click the cancel button. DBX will stop after the current statement completes. Statements that have already been executed are not rolled back.
+Click the cancel button to stop execution before the file finishes. Statements already executed are not rolled back — only subsequent statements are skipped.
diff --git a/docs/content/docs/ssh-tunnel.cn.mdx b/docs/content/docs/ssh-tunnel.cn.mdx
index b27f8aa61e..beec1f4cf7 100644
--- a/docs/content/docs/ssh-tunnel.cn.mdx
+++ b/docs/content/docs/ssh-tunnel.cn.mdx
@@ -1,35 +1,52 @@
 ---
 title: SSH 隧道
-description: 通过 SSH 隧道安全地连接不允许直接远程访问的数据库服务器。
+description: 通过 SSH 隧道安全连接防火墙后的数据库，支持密码和密钥认证。
 ---
 
-当数据库服务器不允许直接远程访问时，你可以通过 SSH 隧道安全地连接。DBX 内置了 SSH 隧道支持，无需手动在终端中建立隧道。
+<Callout type="info">
+内置 SSH 隧道，无需在终端手动建立。支持密码和密钥认证，可选暴露给局域网供团队共享。
+</Callout>
 
-## 配置 SSH 隧道
+当数据库服务器不允许直接远程访问时（例如在防火墙或私有网络后面），你可以通过 SSH 隧道安全地连接。
 
-在创建或编辑数据库连接时，启用"SSH 隧道"选项，然后填写以下信息：
+## 配置
 
-- **SSH 主机** -- SSH 服务器的地址
-- **SSH 端口** -- SSH 服务器的端口（默认 22）
-- **SSH 用户名** -- 用于登录 SSH 服务器的用户名
+在创建或编辑数据库连接时，启用"SSH 隧道"选项：
+
+| 字段 | 说明 |
+|---|---|
+| SSH 主机 | SSH 服务器的地址 |
+| SSH 端口 | SSH 端口（默认 22） |
+| SSH 用户名 | 登录 SSH 服务器的用户名 |
 
 ## 认证方式
 
-DBX 支持两种 SSH 认证方式：
+<Tabs groupId="ssh-auth" items={['密钥认证（推荐）', '密码认证']}>
+  <Tab value="密钥认证（推荐）">
+    选择本地的 SSH 私钥文件（如 `~/.ssh/id_rsa`、`~/.ssh/id_ed25519`）：
 
-### 密码认证
+    - **密钥路径** — 点击文件选择器浏览并选择私钥文件
+    - **密钥密码** — 如果私钥设置了密码保护，在此输入
 
-输入 SSH 用户的登录密码即可。适用于允许密码登录的服务器。
-
-### 密钥认证
-
-选择本地的 SSH 私钥文件进行认证：
-
-- **密钥路径** -- 点击文件选择器，浏览并选择私钥文件（如 `~/.ssh/id_rsa`）
-- **密钥密码** -- 如果私钥设置了密码保护，在此处输入密钥密码
-
-密钥认证比密码认证更安全，推荐优先使用。
+    密钥认证比密码认证更安全，推荐优先使用。
+  </Tab>
+  <Tab value="密码认证">
+    输入 SSH 用户的登录密码即可。适用于允许密码登录的服务器。
+  </Tab>
+</Tabs>
 
 ## 允许局域网访问
 
-DBX 提供"允许局域网访问隧道"选项。启用后，同一局域网中的其他设备也可以通过你的机器访问该 SSH 隧道，适用于团队协作或需要在多个设备上共享数据库连接的场景。
+<Callout type="warn">
+启用"允许局域网访问"后，同一网络中的其他设备也可以通过你的机器访问该 SSH 隧道。仅在可信网络中启用此选项。
+</Callout>
+
+默认情况下，SSH 隧道仅监听 `localhost`。启用局域网访问后，隧道绑定到 `0.0.0.0`，适用于团队协作或多设备共享数据库连接的场景。
+
+## 工作原理
+
+1. DBX 与 SSH 服务器建立连接
+2. 创建本地端口，将流量通过 SSH 隧道转发到数据库服务器
+3. DBX 通过转发的本地端口连接数据库
+
+隧道在数据库连接期间保持活跃，断开连接时自动关闭。
diff --git a/docs/content/docs/ssh-tunnel.mdx b/docs/content/docs/ssh-tunnel.mdx
index c69873ac6c..fa61ad7868 100644
--- a/docs/content/docs/ssh-tunnel.mdx
+++ b/docs/content/docs/ssh-tunnel.mdx
@@ -1,50 +1,52 @@
 ---
 title: SSH Tunnel
-description: Connect to databases through SSH tunnels for secure access to remote servers.
+description: Connect securely to databases behind firewalls via SSH tunnel. Password and key authentication.
 ---
 
-# SSH Tunnel
+<Callout type="info">
+Built-in SSH tunnel — no manual terminal setup. Supports password and private key authentication, with optional LAN exposure for team sharing.
+</Callout>
 
-DBX can connect to databases through an SSH tunnel, allowing you to securely access database servers that are not directly reachable from your machine. This is common in production environments where the database is behind a firewall or on a private network.
+DBX can connect to databases through an SSH tunnel, allowing secure access to servers behind firewalls or on private networks.
 
 ## Configuration
 
-When creating or editing a connection, enable the SSH tunnel option and provide the following details:
+When creating or editing a connection, enable the SSH tunnel option:
 
 | Field | Description |
 |---|---|
-| SSH Host | Hostname or IP address of the SSH server |
-| SSH Port | Port for the SSH connection (default: 22) |
+| SSH Host | Hostname or IP of the SSH server |
+| SSH Port | Port for SSH (default: 22) |
 | SSH User | Username for SSH authentication |
-| Authentication | Password or private key |
 
 ## Authentication Methods
 
-### Password
+<Tabs groupId="ssh-auth" items={['Private Key (Recommended)', 'Password']}>
+  <Tab value="Private Key (Recommended)">
+    Select a private key file (e.g., `~/.ssh/id_rsa`, `~/.ssh/id_ed25519`):
 
-Enter your SSH password directly. The password is stored securely alongside your connection configuration.
+    - **Key Path** — Use the file picker to browse and select your key file
+    - **Key Passphrase** — Enter the passphrase if your key is password-protected
 
-### Private Key
-
-Select a private key file (e.g., `~/.ssh/id_rsa`, `~/.ssh/id_ed25519`) using the file picker. You do not need to type the path manually -- click the browse button to select the key file from your filesystem.
-
-#### Key Passphrase
-
-If your private key is protected by a passphrase, DBX will prompt you to enter it. The passphrase is used to decrypt the key at connection time.
+    Key authentication is more secure than password authentication.
+  </Tab>
+  <Tab value="Password">
+    Enter your SSH password directly. Works on servers that allow password authentication.
+  </Tab>
+</Tabs>
 
 ## Expose Tunnel to LAN
 
-By default, the SSH tunnel listens only on `localhost` (`127.0.0.1`). If you enable the **Expose to LAN** option, the tunnel binds to `0.0.0.0`, making it accessible to other devices on your local network.
+<Callout type="warn">
+Enabling LAN exposure means any device on the same network can access the tunneled database port. Only enable this on trusted networks.
+</Callout>
 
-> **Warning:**
-> Exposing the tunnel to your LAN means any device on the same network can access the tunneled database port. Only enable this on trusted networks.
+By default, the SSH tunnel listens on `localhost` only. Enable LAN exposure to bind to `0.0.0.0`, making the tunnel accessible to other devices on your network — useful for team collaboration or multi-device access.
 
 ## How It Works
 
-When you connect, DBX:
+1. DBX establishes an SSH connection to the specified server
+2. Creates a local port that forwards traffic through the tunnel to the database
+3. Connects to the database through the forwarded local port
 
-1. Establishes an SSH connection to the specified SSH server.
-2. Creates a local port that forwards traffic through the SSH tunnel to the database server.
-3. Connects to the database through the forwarded local port.
-
-The tunnel remains active for the duration of the database connection and is closed automatically when you disconnect.
+The tunnel remains active for the duration of the connection and closes automatically when you disconnect.
diff --git a/docs/content/docs/table-import.cn.mdx b/docs/content/docs/table-import.cn.mdx
index 01c7e8ae56..ef8f85cc25 100644
--- a/docs/content/docs/table-import.cn.mdx
+++ b/docs/content/docs/table-import.cn.mdx
@@ -1,9 +1,11 @@
 ---
 title: 表数据导入
-description: 将外部文件中的数据导入到数据库表中，支持 CSV、TSV、JSON、Excel 格式。
+description: 导入 CSV、TSV、JSON、Excel 文件到数据库表，自动列映射。
 ---
 
-DBX 支持将外部文件中的数据导入到数据库表中，适用于批量数据录入和数据迁移场景。
+<Callout type="info">
+支持 CSV、TSV、JSON、Excel 文件导入，自动匹配列名，可选追加或清空后导入。
+</Callout>
 
 ## 支持的文件格式
 
@@ -12,27 +14,36 @@ DBX 支持将外部文件中的数据导入到数据库表中，适用于批量
 | CSV | 逗号分隔的文本文件 |
 | TSV | 制表符分隔的文本文件 |
 | JSON | JSON 数组格式 |
-| Excel | `.xlsx` 格式的 Excel 文件 |
+| Excel | `.xlsx` 格式 |
 
 ## 使用方式
 
-1. 在目标表上右键，选择"导入数据"
-2. 选择要导入的文件
-3. 确认列映射关系
-4. 选择导入模式
-5. 点击"开始导入"
-
-## 自动列映射
-
-选择文件后，DBX 会自动将文件中的列与目标表的字段进行匹配：
-
-- 根据列名（或表头名称）自动映射到同名字段
-- 你可以手动调整映射关系，将文件中的列指向不同的目标字段
-- 不需要导入的列可以取消映射
+<Steps>
+  <Step>
+    ### 选择目标表
+    在目标表上右键，选择"导入数据"。
+  </Step>
+  <Step>
+    ### 选择文件
+    选择要导入的文件。
+  </Step>
+  <Step>
+    ### 确认列映射
+    DBX 自动将文件中的列与目标表的字段按名称匹配。你可以手动调整映射关系，不需要导入的列可以取消映射。
+  </Step>
+  <Step>
+    ### 选择模式并导入
+    选择导入模式后，点击"开始导入"。
+  </Step>
+</Steps>
 
 ## 导入模式
 
-DBX 提供两种导入模式：
+| 模式 | 说明 |
+|---|---|
+| **追加** | 将文件数据追加到现有数据之后 |
+| **清空后导入** | 先清空表中所有数据，再导入文件内容 |
 
-- **追加模式** -- 将文件中的数据追加到表的现有数据之后，不影响已有记录
-- **清空后导入** -- 先清空表中的所有数据，再导入文件内容。适用于需要完全替换表数据的场景
+<Callout type="warn">
+清空模式会永久删除目标表中的所有现有数据。请确认这是你的预期操作。
+</Callout>
diff --git a/docs/content/docs/table-import.mdx b/docs/content/docs/table-import.mdx
index ab5533f5ae..0d644c884e 100644
--- a/docs/content/docs/table-import.mdx
+++ b/docs/content/docs/table-import.mdx
@@ -1,11 +1,11 @@
 ---
 title: Table Import
-description: Import data from CSV, TSV, JSON, and Excel files into database tables.
+description: Import CSV, TSV, JSON, and Excel files into database tables with automatic column mapping.
 ---
 
-# Table Import
-
-Table Import lets you load data from local files into a database table. It supports common file formats and provides column mapping to ensure data lands in the right place.
+<Callout type="info">
+Import CSV, TSV, JSON, and Excel files with automatic column name matching. Choose between append and truncate modes.
+</Callout>
 
 ## Supported Formats
 
@@ -18,24 +18,32 @@ Table Import lets you load data from local files into a database table. It suppo
 
 ## Import Workflow
 
-1. Select the target connection, database, and table.
-2. Choose a file to import.
-3. Review the auto-generated column mapping.
-4. Select the import mode.
-5. Start the import.
-
-## Column Mapping
-
-After selecting a file, DBX reads the file headers (or keys, for JSON) and automatically maps them to columns in the target table by matching names. You can adjust the mapping manually if the names do not match exactly.
-
-Unmapped file columns are skipped. Unmapped table columns receive their default value or NULL.
+<Steps>
+  <Step>
+    ### Select Target Table
+    Right-click the target table and select "Import Data".
+  </Step>
+  <Step>
+    ### Choose File
+    Select the file to import.
+  </Step>
+  <Step>
+    ### Review Column Mapping
+    DBX auto-maps file columns to table columns by name. Adjust mappings manually if names don't match. Unmapped columns are skipped.
+  </Step>
+  <Step>
+    ### Select Mode and Import
+    Choose the import mode and click "Start Import".
+  </Step>
+</Steps>
 
 ## Import Modes
 
 | Mode | Behavior |
 |---|---|
-| **Append** | Insert the imported rows into the table alongside existing data. |
-| **Truncate then import** | Delete all existing rows from the table first, then insert the imported data. |
+| **Append** | Insert rows alongside existing data |
+| **Truncate then import** | Delete all existing rows first, then insert |
 
-> **Warning:**
-> Truncate mode permanently removes all existing data in the target table before importing. Make sure this is the intended behavior before proceeding.
+<Callout type="warn">
+Truncate mode permanently removes all existing data in the target table. Make sure this is the intended behavior.
+</Callout>
diff --git a/docs/content/docs/table-structure.cn.mdx b/docs/content/docs/table-structure.cn.mdx
index 96003b84cf..a2756153b4 100644
--- a/docs/content/docs/table-structure.cn.mdx
+++ b/docs/content/docs/table-structure.cn.mdx
@@ -1,23 +1,25 @@
 ---
 title: 表结构编辑器
-description: 可视化的表结构编辑器，无需手写 DDL 语句即可管理表的列和索引。
+description: 可视化管理表的列和索引，无需手写 DDL，保存前预览 ALTER TABLE 语句。
 ---
 
-DBX 提供可视化的表结构编辑器，让你无需手写 DDL 语句即可管理表的列和索引。
+<Callout type="info">
+可视化编辑表结构，无需手写 `ALTER TABLE`。所有变更保存前可预览完整的 DDL 语句。
+</Callout>
 
 ## 列编辑
 
-在表结构编辑器中，你可以通过可视化界面管理表的列：
+在表结构编辑器中，通过可视化界面管理表的列：
 
-- **添加列** -- 点击"添加列"按钮，设置列名、数据类型、是否允许 NULL、默认值等属性
-- **修改列** -- 直接编辑已有列的属性，包括重命名、更改类型、调整默认值等
-- **删除列** -- 选中列后点击删除，标记该列待移除
+- **添加列** — 设置列名、数据类型、是否允许 NULL、默认值等属性
+- **修改列** — 直接编辑已有列的属性，包括重命名、更改类型、调整默认值
+- **删除列** — 选中列后标记待移除
 
 所有修改不会立即生效，而是暂存在本地等待确认。
 
 ## 索引管理
 
-除了列之外，你还可以在同一界面中管理表的索引：
+在同一界面中管理表的索引：
 
 - 添加新索引，指定索引列和索引类型（普通索引、唯一索引等）
 - 修改已有索引的配置
@@ -25,19 +27,17 @@ DBX 提供可视化的表结构编辑器，让你无需手写 DDL 语句即可
 
 ## SQL 预览
 
-在点击"应用"之前，DBX 会展示即将执行的 `ALTER TABLE` 语句，让你确认每一项变更。你可以：
-
-- 查看完整的 DDL 变更语句
-- 确认无误后执行
-- 如发现问题，返回继续调整
+<Callout type="info">
+在点击"应用"之前，DBX 会展示即将执行的 `ALTER TABLE` 语句，包括 `ADD COLUMN`、`MODIFY COLUMN`、`DROP COLUMN`、`CREATE INDEX` 等。确认无误后再执行。
+</Callout>
 
 ## 数据库支持
 
-表结构编辑器支持以下数据库引擎，并针对各引擎的特性做了适配：
-
 | 数据库 | 支持情况 |
 |---|---|
-| MySQL | 支持 |
-| PostgreSQL | 支持 |
-| SQLite | 支持 |
-| SQL Server | 支持 |
+| MySQL | 完整支持 |
+| PostgreSQL | 完整支持 |
+| SQLite | 完整支持 |
+| SQL Server | 完整支持 |
+
+DBX 会根据每种引擎的特性自动适配。例如，SQLite 有限的 `ALTER TABLE` 能力由 DBX 透明处理。
diff --git a/docs/content/docs/table-structure.mdx b/docs/content/docs/table-structure.mdx
index 25d3c7798f..29a35ad2c2 100644
--- a/docs/content/docs/table-structure.mdx
+++ b/docs/content/docs/table-structure.mdx
@@ -1,48 +1,43 @@
 ---
 title: Table Structure Editor
-description: Visually modify table schemas -- add, edit, and delete columns and indexes.
+description: Visually manage columns and indexes without writing DDL. Preview ALTER TABLE statements before applying.
 ---
 
-# Table Structure Editor
-
-The Table Structure Editor provides a visual interface for modifying table schemas. Instead of writing `ALTER TABLE` statements by hand, you can add, modify, and delete columns and indexes through a form-based UI.
+<Callout type="info">
+Edit table structure visually — no `ALTER TABLE` by hand. All changes are previewed as SQL before execution.
+</Callout>
 
 ## Column Editor
 
-The column editor displays all columns of the selected table in an editable list. For each column, you can modify:
+Manage columns through a visual interface:
 
-- **Name** -- Rename the column
-- **Type** -- Change the data type
-- **Nullable** -- Toggle whether the column allows NULL values
-- **Default** -- Set or change the default value
-- **Comment** -- Add or update the column comment (on supported engines)
+- **Add column** — Set name, type, nullable, default, and comment
+- **Modify column** — Rename, change type, adjust defaults
+- **Delete column** — Mark for removal
 
-You can also:
-
-- **Add a column** -- Append a new column definition to the table
-- **Delete a column** -- Remove an existing column from the table
+All changes are staged locally until you confirm.
 
 ## Index Management
 
-Below the column list, the index section lets you manage table indexes:
+Manage indexes in the same interface:
 
-- View existing indexes and their columns
-- Create new indexes (unique, non-unique)
-- Remove existing indexes
+- Create new indexes (unique, non-unique) with selected columns
+- Modify existing index configurations
+- Remove indexes
 
 ## SQL Preview
 
-Before applying any structural changes, DBX generates and displays the corresponding SQL statements (`ALTER TABLE ADD COLUMN`, `ALTER TABLE MODIFY COLUMN`, `DROP COLUMN`, `CREATE INDEX`, etc.). You can review the exact SQL that will be executed and confirm or cancel.
+<Callout type="info">
+Before applying, DBX shows the exact `ALTER TABLE` statements — `ADD COLUMN`, `MODIFY COLUMN`, `DROP COLUMN`, `CREATE INDEX`, etc. Review and confirm before committing.
+</Callout>
 
 ## Database Support
 
-The Table Structure Editor supports the following database engines:
-
 | Engine | Support |
 |---|---|
-| MySQL | Full support |
-| PostgreSQL | Full support |
-| SQLite | Full support |
-| SQL Server | Full support |
+| MySQL | Full |
+| PostgreSQL | Full |
+| SQLite | Full |
+| SQL Server | Full |
 
-Behavior adapts to the capabilities and syntax of each engine. For example, SQLite's limited `ALTER TABLE` support is handled transparently by DBX.
+Behavior adapts to the capabilities of each engine. For example, SQLite's limited `ALTER TABLE` support is handled transparently by DBX.
diff --git a/docs/content/docs/what-is-dbx.cn.mdx b/docs/content/docs/what-is-dbx.cn.mdx
index db121fcf9c..ad28cbf4ae 100644
--- a/docs/content/docs/what-is-dbx.cn.mdx
+++ b/docs/content/docs/what-is-dbx.cn.mdx
@@ -1,35 +1,68 @@
 ---
 title: 什么是 DBX？
-description: DBX 是一款开源、轻量、跨平台的数据库管理工具，基于 Tauri 2 和 Rust 构建。
+description: 开源、轻量、AI 驱动的数据库管理工具，15 MB 管理 25+ 种数据库。
 ---
 
-DBX 是一款开源、轻量、跨平台的数据库管理工具，基于 [Tauri 2](https://tauri.app/) 和 Rust 构建。
+<Callout type="info">
+15 MB 安装包，25+ 种数据库，内置 AI 助手，桌面 + Docker 双模式部署。
+</Callout>
+
+DBX 是一款开源、轻量、跨平台的数据库管理工具，基于 [Tauri 2](https://tauri.app/) 和 Rust 构建。无需内嵌 Chromium，安装包仅 15 MB，却能管理 MySQL、PostgreSQL、MongoDB、Redis 等 25+ 种数据库。
+
+![DBX 截图](/screenshot-dark.png)
 
 ## 为什么选择 DBX？
 
-- **轻量** — 安装包约 15 MB，不内嵌 Chromium
-- **多数据库** — 一个工具管理 MySQL、PostgreSQL、SQLite、Redis、MongoDB 等 25+ 种数据库
-- **AI 驱动** — 内置 AI 助手 + MCP Server 对接外部 AI 编程助手
-- **安全** — 密码存储在系统钥匙串，支持 SSH 隧道，加密配置导出
-- **跨平台** — macOS、Windows、Linux
-- **Docker 自托管** — 支持通过 Docker 部署，适合团队共享和服务器环境
+<Cards>
+  <Card title="极致轻量" href="/cn/docs/getting-started">
+    ~15 MB 安装包，不内嵌 Chromium。Tauri 2 + Rust 原生性能，启动秒开。
+  </Card>
+  <Card title="25+ 数据库" href="/cn/docs/databases">
+    一个工具管理 MySQL、PostgreSQL、SQLite、Redis、MongoDB、ClickHouse、SQL Server、Oracle 等 25+ 种数据库。
+  </Card>
+  <Card title="AI 驱动" href="/cn/docs/ai-assistant">
+    内置 AI 助手：自然语言转 SQL、查询优化、错误修复。MCP Server 让 Claude/Cursor 直接查询你的数据库。
+  </Card>
+  <Card title="安全可靠" href="/cn/docs/ssh-tunnel">
+    密码存储在系统钥匙串（macOS Keychain / Windows Credential Manager），SSH 隧道，AES-256-GCM 加密配置导出。
+  </Card>
+</Cards>
 
 ## 核心功能
 
-- SQL 查询编辑器（语法高亮、智能补全、查询历史）
-- 数据表格（虚拟滚动、行内编辑、导出）
-- 结构浏览（树形视图、搜索、右键菜单）
-- Schema 图 / ER 图
-- 执行计划可视化
-- 表结构编辑器（可视化 DDL）
-- Schema 对比与同步
-- 数据迁移（跨引擎传输）
-- 数据导入（CSV、TSV、JSON、Excel）
-- 数据库导出（DDL + 数据）
-- 字段血缘分析
-- 配置导出/导入（加密传输）
-- AI 助手（自然语言转 SQL、优化、修复）
-- MCP Server（对接 Claude Code、Cursor 等）
+<Cards>
+  <Card title="查询编辑器" href="/cn/docs/query-editor">
+    CodeMirror 6 驱动，语法高亮、智能补全、JOIN 建议、查询历史。
+  </Card>
+  <Card title="数据表格" href="/cn/docs/data-grid">
+    虚拟滚动 10 万行不卡顿，行内编辑，保存前预览 SQL。
+  </Card>
+  <Card title="结构浏览" href="/cn/docs/schema-browser">
+    树形视图，搜索、置顶、右键菜单、字段注释、连接颜色标记。
+  </Card>
+  <Card title="Schema 对比" href="/cn/docs/schema-diff">
+    跨数据库结构对比，自动生成同步 SQL，开发 vs 生产一键对齐。
+  </Card>
+  <Card title="数据传输" href="/cn/docs/data-transfer">
+    跨引擎迁移 — MySQL → PostgreSQL，自动处理类型映射。
+  </Card>
+  <Card title="字段血缘" href="/cn/docs/field-lineage">
+    追踪外键、视图、查询历史中的字段关联，标注置信度。
+  </Card>
+</Cards>
+
+## 与竞品对比
+
+| | DBX | DBeaver | Navicat | TablePlus |
+|---|---|---|---|---|
+| **安装体积** | ~15 MB | ~300 MB | ~200 MB | ~80 MB |
+| **价格** | 免费 (AGPL) | 免费 / $230 | $180+ | $99+ |
+| **数据库支持** | 25+ | 80+ | 15+ | 20+ |
+| **内置 AI** | ✅ | ❌ | ✅ | ❌ |
+| **MCP 集成** | ✅ | ❌ | ❌ | ❌ |
+| **Docker 自托管** | ✅ | ❌ | ❌ | ❌ |
+| **字段血缘** | ✅ | ❌ | ❌ | ❌ |
+| **Schema 对比** | ✅ | ✅ | ✅ | ❌ |
 
 ## 技术栈
 
diff --git a/docs/content/docs/what-is-dbx.mdx b/docs/content/docs/what-is-dbx.mdx
index 2cfb0d2646..bb4c6d63d3 100644
--- a/docs/content/docs/what-is-dbx.mdx
+++ b/docs/content/docs/what-is-dbx.mdx
@@ -1,39 +1,68 @@
 ---
 title: What is DBX?
-description: An open-source, lightweight, cross-platform database management tool built with Tauri 2 and Rust.
+description: Open-source, lightweight, AI-powered database management tool. 15 MB for 25+ databases.
 ---
 
-# What is DBX?
+<Callout type="info">
+15 MB install size. 25+ database engines. Built-in AI assistant. Desktop + Docker deployment.
+</Callout>
 
-DBX is an open-source, lightweight, cross-platform database management tool built with [Tauri 2](https://tauri.app/) and Rust.
+DBX is an open-source, lightweight, cross-platform database management tool built with [Tauri 2](https://tauri.app/) and Rust. No bundled Chromium — just a 15 MB installer that manages MySQL, PostgreSQL, MongoDB, Redis, and 25+ more databases.
 
-<div style={{textAlign: "center"}}>
-  <img src="/screenshot.png" alt="DBX Screenshot" style={{maxWidth: "100%", borderRadius: "8px", margin: "16px 0"}} />
-</div>
+![DBX Screenshot](/screenshot-dark.png)
 
 ## Why DBX?
 
-- **Lightweight** — ~15 MB installer, no bundled Chromium
-- **Multi-database** — One tool for MySQL, PostgreSQL, SQLite, Redis, MongoDB, and 20+ more
-- **AI-powered** — Built-in AI assistant + MCP server for external AI agents
-- **Secure** — Passwords in system keyring, SSH tunnels, encrypted config export
-- **Cross-platform** — macOS, Windows, Linux, Docker (self-hosted)
+<Cards>
+  <Card title="Ultra-Lightweight" href="/en/docs/getting-started">
+    ~15 MB installer, no Chromium. Tauri 2 + Rust for native performance and instant startup.
+  </Card>
+  <Card title="25+ Databases" href="/en/docs/databases">
+    One tool for MySQL, PostgreSQL, SQLite, Redis, MongoDB, ClickHouse, SQL Server, Oracle, and more.
+  </Card>
+  <Card title="AI-Powered" href="/en/docs/ai-assistant">
+    Built-in AI assistant: natural language to SQL, query optimization, error fixing. MCP Server lets Claude/Cursor query your databases directly.
+  </Card>
+  <Card title="Secure by Default" href="/en/docs/ssh-tunnel">
+    Passwords in system keyring (macOS Keychain / Windows Credential Manager). SSH tunnels and AES-256-GCM encrypted config export.
+  </Card>
+</Cards>
 
 ## Key Features
 
-- **Query Editor** — Syntax highlighting, autocomplete, query history
-- **Data Grid** — Virtual scrolling, inline editing, data export
-- **Schema Browser** — Tree view, search, pin, column comments
-- **Schema Diagram** — Visual ER diagram of your database schema
-- **Schema Diff** — Compare and sync schemas between databases
-- **Explain Plan** — Visualize query execution plans
-- **Data Transfer** — Move data between different database engines
-- **Table Import** — Import CSV, TSV, JSON, Excel files into tables
-- **Database Export** — Export database structure and data as SQL
-- **Field Lineage** — Trace column relationships across tables and views
-- **Config Export** — Encrypted export/import of connection configurations
-- **AI Assistant** — Natural language to SQL, query explanation, optimization
-- **MCP Server** — Let AI agents query your databases directly
+<Cards>
+  <Card title="Query Editor" href="/en/docs/query-editor">
+    Powered by CodeMirror 6. Syntax highlighting, smart autocomplete, JOIN suggestions, query history.
+  </Card>
+  <Card title="Data Grid" href="/en/docs/data-grid">
+    Virtual scrolling for 100K+ rows. Inline editing with SQL preview before saving.
+  </Card>
+  <Card title="Schema Browser" href="/en/docs/schema-browser">
+    Tree view with search, pin, context menus, column comments, and connection colors.
+  </Card>
+  <Card title="Schema Diff" href="/en/docs/schema-diff">
+    Compare schemas across databases and generate sync SQL. Dev vs Production in one click.
+  </Card>
+  <Card title="Data Transfer" href="/en/docs/data-transfer">
+    Cross-engine migration — MySQL to PostgreSQL with automatic type mapping.
+  </Card>
+  <Card title="Field Lineage" href="/en/docs/field-lineage">
+    Trace column relationships across foreign keys, views, and query history with confidence levels.
+  </Card>
+</Cards>
+
+## How DBX Compares
+
+| | DBX | DBeaver | Navicat | TablePlus |
+|---|---|---|---|---|
+| **Install Size** | ~15 MB | ~300 MB | ~200 MB | ~80 MB |
+| **Price** | Free (AGPL) | Free / $230 | $180+ | $99+ |
+| **Database Support** | 25+ | 80+ | 15+ | 20+ |
+| **Built-in AI** | ✅ | ❌ | ✅ | ❌ |
+| **MCP Integration** | ✅ | ❌ | ❌ | ❌ |
+| **Docker Self-Host** | ✅ | ❌ | ❌ | ❌ |
+| **Field Lineage** | ✅ | ❌ | ❌ | ❌ |
+| **Schema Diff** | ✅ | ✅ | ✅ | ❌ |
 
 ## Tech Stack
 
diff --git a/docs/next-env.d.ts b/docs/next-env.d.ts
index 9edff1c7ca..c4b7818fbb 100644
--- a/docs/next-env.d.ts
+++ b/docs/next-env.d.ts
@@ -1,6 +1,6 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/types/routes.d.ts";
+import "./.next/dev/types/routes.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/app/api-reference/config/typescript for more information.