File tree Expand file tree Collapse file tree
en/use-dify/knowledge/knowledge-pipeline
knowledge/knowledge-pipeline
zh/use-dify/knowledge/knowledge-pipeline Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -15,27 +15,27 @@ Dify provides built-in pipeline templates that is optimized for certain use case
1515
1616<Steps >
1717 <Step >
18- <Card title = " Step 1: Create Knowledge Pipeline" horizontal href = " . /create-knowledge-pipeline" >
18+ <Card title = " Step 1: Create Knowledge Pipeline" horizontal href = " /en/use-dify/knowledge/knowledge-pipeline /create-knowledge-pipeline" >
1919 Start from built-in templates, blank knowledge pipeline or import existing pipeline.
2020 </Card >
2121 </Step >
2222 <Step >
23- <Card title = " Step 2: Orchestrate Knowledge Pipeline" horizontal href = " . /knowledge-pipeline-orchestration" >
23+ <Card title = " Step 2: Orchestrate Knowledge Pipeline" horizontal href = " /en/use-dify/knowledge/knowledge-pipeline /knowledge-pipeline-orchestration" >
2424 Get to know how the knowledge pipeline works, orchestrate different nodes and make sure it’s ready to use.
2525 </Card >
2626 </Step >
2727 <Step >
28- <Card title = " Step 3: Publish Knowledge Pipeline" horizontal href = " . /publish-knowledge-pipeline" >
28+ <Card title = " Step 3: Publish Knowledge Pipeline" horizontal href = " /en/use-dify/knowledge/knowledge-pipeline /publish-knowledge-pipeline" >
2929 Let's make it ready for document processing.
3030 </Card >
3131 </Step >
3232 <Step >
33- <Card title = " Step 4: Upload Files" horizontal href = " . /upload-files" >
33+ <Card title = " Step 4: Upload Files" horizontal href = " /en/use-dify/knowledge/knowledge-pipeline /upload-files" >
3434 Add documents and process them into the searchable knowledge base.
3535 </Card >
3636 </Step >
3737 <Step >
38- <Card title = " Step 5: Manage and Use Knowledge Base" horizontal href = " . /manage-knowledge-base" >
38+ <Card title = " Step 5: Manage and Use Knowledge Base" horizontal href = " /en/use-dify/knowledge/knowledge-pipeline /manage-knowledge-base" >
3939 Maintain documents, test retrieval, modify settings, and more.
4040 </Card >
4141 </Step >
Original file line number Diff line number Diff line change @@ -17,27 +17,27 @@ Difyには特定の用途に最適化されたパイプラインテンプレー
1717
1818<Steps >
1919 <Step >
20- <Card title = " ステップ1:ナレッジパイプラインの作成" horizontal href = " . /create-knowledge-pipeline" >
20+ <Card title = " ステップ1:ナレッジパイプラインの作成" horizontal href = " /ja/use-dify/knowledge/knowledge-pipeline /create-knowledge-pipeline" >
2121 組み込みのテンプレート、空のナレッジパイプラインから始めるか、既存のパイプラインをインポートします。
2222 </Card >
2323 </Step >
2424 <Step >
25- <Card title = " ステップ2:ナレッジパイプラインの構築" horizontal href = " . /knowledge-pipeline-orchestration" >
25+ <Card title = " ステップ2:ナレッジパイプラインの構築" horizontal href = " /ja/use-dify/knowledge/knowledge-pipeline /knowledge-pipeline-orchestration" >
2626 ナレッジパイプラインの仕組みを理解し、異なるノードを構成して、必要なデータ処理フローを構築します。
2727 </Card >
2828 </Step >
2929 <Step >
30- <Card title = " ステップ3:ナレッジパイプラインの公開" horizontal href = " . /publish-knowledge-pipeline" >
30+ <Card title = " ステップ3:ナレッジパイプラインの公開" horizontal href = " /ja/use-dify/knowledge/knowledge-pipeline /publish-knowledge-pipeline" >
3131 設定をテストした後、パイプラインを公開し、ドキュメント処理の準備をします。
3232 </Card >
3333 </Step >
3434 <Step >
35- <Card title = " ステップ4:ファイルのアップロード" horizontal href = " . /upload-files" >
35+ <Card title = " ステップ4:ファイルのアップロード" horizontal href = " /ja/use-dify/knowledge/knowledge-pipeline /upload-files" >
3636 ドキュメントをアップロードして処理することで、検索可能なナレッジベースを構築します。
3737 </Card >
3838 </Step >
3939 <Step >
40- <Card title = " ステップ5:ナレッジベースの管理と活用" horizontal href = " . /manage-knowledge-base" >
40+ <Card title = " ステップ5:ナレッジベースの管理と活用" horizontal href = " /ja/use-dify/knowledge/knowledge-pipeline /manage-knowledge-base" >
4141 ドキュメントのメンテナンス、検索精度のテスト、設定の変更などを行います。
4242 </Card >
4343 </Step >
Original file line number Diff line number Diff line change @@ -88,18 +88,7 @@ docker compose up -d
8888
8989初期化されたチャットフローは以下のようになります:
9090
91- <div className = " image-side-by-side" >
92- <img
93- src = " https://assets-docs.dify.ai/dify-enterprise-mintlify/jp/workshop/intermediate/baee341b771d1cd77780fd4845b467b2.png"
94- className = " mx-auto"
95- alt = " 初期化されたチャットフロー画面1"
96- />
97- <img
98- src = " ../../.gitbook/assets/twitter_init.webp"
99- className = " mx-auto"
100- alt = " 初期化されたチャットフロー画面2"
101- />
102- </div >
91+ ![ 初期化されたチャットフロー画面] ( https://assets-docs.dify.ai/dify-enterprise-mintlify/jp/workshop/intermediate/baee341b771d1cd77780fd4845b467b2.png )
10392
10493## チャットフローにノードを追加
10594
Original file line number Diff line number Diff line change @@ -17,27 +17,27 @@ sidebarTitle: 概述
1717
1818<Steps >
1919 <Step >
20- <Card title = " 步骤一:创建知识流水线" horizontal href = " . /create-knowledge-pipeline" >
20+ <Card title = " 步骤一:创建知识流水线" horizontal href = " /zh/use-dify/knowledge/knowledge-pipeline /create-knowledge-pipeline" >
2121 从内置模板、空白知识库流水线开始创建,或导入现有流水线。
2222 </Card >
2323 </Step >
2424 <Step >
25- <Card title = " 步骤二: 编排知识流水线" horizontal href = " . /knowledge-pipeline-orchestration" >
25+ <Card title = " 步骤二: 编排知识流水线" horizontal href = " /zh/use-dify/knowledge/knowledge-pipeline /knowledge-pipeline-orchestration" >
2626 了解知识库流水线的工作原理,编排不同节点,构建你需要的的数据处理流程。
2727 </Card >
2828 </Step >
2929 <Step >
30- <Card title = " 步骤三:发布知识流水线" horizontal href = " . /publish-knowledge-pipeline" >
30+ <Card title = " 步骤三:发布知识流水线" horizontal href = " /zh/use-dify/knowledge/knowledge-pipeline /publish-knowledge-pipeline" >
3131 测试配置无误后,发布流水线,准备进行文档处理。
3232 </Card >
3333 </Step >
3434 <Step >
35- <Card title = " 步骤四:上传文件" horizontal href = " . /upload-files" >
35+ <Card title = " 步骤四:上传文件" horizontal href = " /zh/use-dify/knowledge/knowledge-pipeline /upload-files" >
3636 添加文档,经过处理后构建成可搜索的知识库。
3737 </Card >
3838 </Step >
3939 <Step >
40- <Card title = " 步骤五:管理和使用知识库" horizontal href = " . /manage-knowledge-base" >
40+ <Card title = " 步骤五:管理和使用知识库" horizontal href = " /zh/use-dify/knowledge/knowledge-pipeline /manage-knowledge-base" >
4141 日常维护文档、测试检索效果、修改设置等。
4242 </Card >
4343 </Step >
You can’t perform that action at this time.
0 commit comments