boluor opened a new pull request, #3777:
URL: https://github.com/apache/doris-website/pull/3777

   ## Summary
   
   While auditing 3.0.6 zh/EN parity, the zh page turned out to be more 
carefully organised than EN. Cross-port two structural improvements from zh:
   
   ### 1. Improvements section: split \`### Storage\`
   
   EN \`### Storage\` was a catch-all that lumped together three distinct 
categories of bullets:
   
   - Routine Load blacklist and \`load_task_high_priority_threshold_second\` → 
**Data Ingestion**
   - Reduced redundant log output → **Primary Key Model**
   - Compaction Profile / log streamlining and Compaction throughput scheduling 
→ **Storage**
   
   Split it into three proper H3s — \`### Data Ingestion\`, \`### Primary Key 
Model\`, \`### Storage\` — matching zh's \`### 导入\` / \`### 主键模型\` / \`### 
存储优化\`. Bullet order, content, and PR refs are preserved; only grouping changes.
   
   ### 2. Bug Fixes › Lakehouse: promote ad-hoc groupings to H4
   
   EN used bold paragraph leads (\`**Export fixes**\`, \`**Catalog fixes**\`, 
\`**File formats**\`) as ad-hoc sub-groupings inside a bullet list. zh uses 
proper H4 headings (\`#### Export 修复\`, \`#### Catalog 修复\`, \`#### 文件格式\`). 
Promote EN to the same H4 structure and flatten the nested 1-level-deep bullets 
to top-level so the on-page navigation matches.
   
   No content additions; the set of PR references is unchanged on both sides 
(98 unique refs each).
   
   ## Test plan
   
   - [x] zh and EN H2/H3/H4 structure now matches one-to-one (only translation 
differences remain)
   - [x] \`grep -oE 'pull/[0-9]+' | sort -u | wc -l\` returns 98 on both sides


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to