Skip to content

Commit a237348

Browse files
authored
Merge pull request #53 from mssssss123/page/project
fix: improve clarity and conciseness in documentation for UltraRAG 2.0
2 parents 1b3b744 + bdf1f91 commit a237348

File tree

2 files changed

+9
-10
lines changed

2 files changed

+9
-10
lines changed

index.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -255,8 +255,8 @@ <h2 class="subtitle has-text-centered">
255255
</div>
256256

257257
<p>
258-
其官方实现需要 <strong>900 行手写逻辑</strong>,FlashRAG 也需要 <strong>超过 110 行代码</strong>UltraRAG 2.0 仅用
259-
<strong>50 行代码</strong> 即可完成同等功能。更值得注意的是,其中约一半还是用于编排 Pipeline 的 Yaml 伪代码,这大幅降低了开发门槛与实现成本。
258+
在官方实现中,仅 <strong>Pipeline 部分就需要近 900 行手写逻辑</strong>;即便使用标杆级 RAG 框架(如 FlashRAG),也仍需 <strong>超过 110 行代码</strong>相比之下,UltraRAG 2.0 只需
259+
<strong>50 行代码</strong> 即可完成同等功能。更值得强调的是,其中约一半还是用于编排的 Yaml 伪代码,这大幅降低了开发门槛与实现成本。
260260
</p>
261261

262262
<div class="item">
@@ -277,7 +277,7 @@ <h2 class="subtitle has-text-centered">不同框架实现 IRCoT 的代码规模
277277

278278

279279
<p>
280-
我们进一步展示了不同框架在相同功能实现上的差异。可以看到,FlashRAG 的实现仍然需要冗长的控制逻辑,涉及显式的循环、条件判断与状态更新。而在 UltraRAG 2.0 中,这些逻辑仅需 <strong>几行
280+
我们进一步展示了不同框架在相同功能实现上的差异。可以看到,FlashRAG 的实现仍然需要较长的控制逻辑,涉及显式的循环、条件判断与状态更新。而在 UltraRAG 2.0 中,这些逻辑仅需 <strong>几行
281281
Pipeline YAML 配置</strong> 即可表达,分支与循环均以简洁的声明方式完成,避免了繁琐的手动编码。
282282
</p>
283283

index_en.html

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -265,12 +265,11 @@ <h2 class="subtitle has-text-centered">
265265
</div>
266266

267267
<p>
268-
Its official implementation requires <strong>nearly 900 lines of handwritten logic</strong>, and even
269-
FlashRAG still takes
270-
<strong>over 110 lines of code</strong>. In contrast, UltraRAG 2.0 achieves the same functionality with
271-
just
272-
<strong>50 lines</strong>. Notably, about half of this is merely Pipeline Yaml pseudo-code, dramatically
273-
lowering the development barrier and implementation cost.
268+
In the official implementation, the Pipeline alone requires <strong>nearly 900 lines of handwritten logic</strong>.
269+
Even with a benchmark RAG framework such as FlashRAG, it still takes <strong>over 110 lines of code</strong>.
270+
In contrast, UltraRAG 2.0 achieves the same functionality with just <strong>around 50 lines of code</strong>—and notably,
271+
nearly half of these are simply Yaml pseudo-code for pipeline orchestration.
272+
This dramatically lowers the development barrier and implementation cost.
274273
</p>
275274

276275
<div class="item">
@@ -290,7 +289,7 @@ <h2 class="subtitle has-text-centered">How Different Frameworks Implement IRCoT:
290289

291290
<p>
292291
We showcase how frameworks differ in implementing the same functionality.
293-
FlashRAG requires verbose control logic with explicit loops, conditionals, and state updates.
292+
FlashRAG requires lengthy control logic with explicit loops, conditionals, and state updates.
294293
UltraRAG 2.0, on the other hand, simplifies everything into just <strong>a few lines of Pipeline
295294
YAML—branches and loops</strong> are expressed declaratively,
296295
removing the burden of manual coding.

0 commit comments

Comments
 (0)