langgenius/dify-docs-archived
1
0
Fork 0
mirror of https://github.com/langgenius/dify-docs-archived.git synced 2026-07-13 20:41:55 -04:00
Code Issues 39 Packages Projects Releases Wiki Activity

[PR #170] [MERGED] Fix urls in contribution page #300

New Issue
Closed
opened 2026-02-16 11:20:27 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 11:20:27 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-docs-archived/pull/170
Author: @sorphwer
Created: 7/21/2024
Status: ✅ Merged
Merged: 7/25/2024
Merged by: @crazywoola

Base: main ← Head: fix-urls-in-contribution-page

📝 Commits (2)

📊 Changes

3 files changed (+9 additions, -6 deletions)

View changed files

📝 en/community/contribution.md (+5 -2)
📝 jp/community/contribution.md (+2 -2)
📝 zh_CN/community/contribution.md (+2 -2)

📄 Description

Hi Dify Team,

I've noticed some hyperlinks do not works, and here is a quick fix.

Moreover, I suggest you align the design across lanaguages:

  1. You use https://docs.dify.ai/v/zh-hans/guides/gong-ju in zh-CN but use https://docs.dify.ai/guides/tools in en-US.
  2. Lang code is not the same : .../v/japanese/ , .../v/zh-hans , and default path is English.

I understand that document design is not the top priority compared to the rapidly changing requirements of Dify itself. But you can take this as the roadmap or I am willing to help, I would like to know if someone/some team is working with:

  1. Align the design of doc path, for example , the tools page could be like:

Regards,

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-docs-archived/pull/170 **Author:** [@sorphwer](https://github.com/sorphwer) **Created:** 7/21/2024 **Status:** ✅ Merged **Merged:** 7/25/2024 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `fix-urls-in-contribution-page` --- ### 📝 Commits (2) - [`eaf5884`](https://github.com/langgenius/dify-docs-archived/commit/eaf588412ecdc2dc00608c260927054ec02fa1b2) fix: update urls in contribution page - [`376edc0`](https://github.com/langgenius/dify-docs-archived/commit/376edc0f67521e20cd2d42d9a7bdc46109036292) clean up ### 📊 Changes **3 files changed** (+9 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `en/community/contribution.md` (+5 -2) 📝 `jp/community/contribution.md` (+2 -2) 📝 `zh_CN/community/contribution.md` (+2 -2) </details> ### 📄 Description Hi Dify Team, I've noticed some hyperlinks do not works, and here is a quick fix. Moreover, I suggest you align the design across lanaguages: 1. You use `https://docs.dify.ai/v/zh-hans/guides/gong-ju` in zh-CN but use `https://docs.dify.ai/guides/tools` in en-US. 2. Lang code is not the same : `.../v/japanese/` , `.../v/zh-hans` , and default path is English. I understand that document design is not the top priority compared to the rapidly changing requirements of Dify itself. But you can take this as the roadmap or I am willing to help, I would like to know if someone/some team is working with: 1. Align the design of doc path, for example , the tools page could be like: - https://docs.dify.ai/en-us/guides/tools - https://docs.dify.ai/zh-cn/guides/tools - https://docs.dify.ai/ja-jp/guides/tools Regards, --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 11:20:27 -05:00
yindo closed this issue 2026-02-16 11:20:27 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
documentation
enhancement
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-docs-archived#300
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?