Revert "Docs: update contribution content (#616)"

This reverts commit 37e5ea2.

Author: AllenWriter

en/community/docs-contribution.md

@@ -6,9 +6,8 @@ Dify documentation is an [open-source project](https://github.com/langgenius/dif
 
 We categorize documentation issues into two main types:
 
-* Content Corrections
-* Content Additions
-* Best Practices
+* Content Corrections (Typos / Inaccuracies)
+* Content Additions (New documentation)
 
 ### Content Errors
 
@@ -40,41 +39,6 @@ For instance, if you're contributing documentation for third-party tools, please
 
 When submitting a pull request, please use the format `Docs: Add xxx` for the title and provide a brief description in the comment field. We'll review your submission and merge the changes if everything is in order.
 
-### Best Practices
-
-Best Practices
-
-We warmly encourage you to share the creative application scenarios you have built with Dify! To help community members better understand and replicate your hands-on experience, we recommend structuring your content as follows:
-
-
-```text
-1. Introduction
-   - Application scenarios and problems addressed
-   - Key features and highlights
-   - Final results and demonstrations
-
-2. Project Principles / Process Overview
-
-3. Prerequisites (if any)
-   - Required resource list
-   - Tool and dependency requirements
-
-4. Implementation in the Dify Platform (Suggested Steps)
-   - Application creation and basic configurations
-   - Process-building guide
-   - Configuration details for key nodes
-
-5. FAQ
-   - Typical development challenges
-   - Troubleshooting and solutions
-   - Performance optimization tips
-   - Additional notes and best practices
-```
-
-> For images and screenshots, please use online image hosting links in your documentation.
-
-We look forward to your valuable contributions and to fostering knowledge within the Dify community together!
-
 ## Getting Help
 
 If you ever get stuck or got a burning question while contributing, simply shoot your queries our way via the related GitHub issue, or hop onto our [Discord](https://discord.com/invite/8Tpq4AcN9c) for a quick chat.

zh_CN/community/docs-contribution.md

@@ -4,11 +4,10 @@ Dify 帮助文档是一个[开源项目](https://github.com/langgenius/dify-docs
 
 ## 如何提交贡献
 
-我们将文档划分为以下类型：
+我们将文档问题分为以下几类：
 
-* 内容勘误
-* 内容缺失
-* 最佳实践
+* 内容勘误（错别字 / 内容不正确）
+* 内容缺失（需要补充新的内容）
 
 ### 内容勘误
 
@@ -40,38 +39,6 @@ git clone https://github.com/<your-github-account>/dify-docs.git
 
 提交 pull request 时，请使用 `Docs: add xxx` 的格式，并在描述栏内简单说明文档的大致内容，我们在收到请求后进行 review，无误后将合并你的修改。
 
-### 最佳实践
-
-我们非常欢迎你分享使用 Dify 搭建的创新应用案例！为了帮助社区成员更好地理解和复现你的实践经验，建议按照以下框架来组织内容：
-
-```text
-1. 项目简介
-   - 应用场景和解决的问题
-   - 核心功能和特点介绍
-   - 最终效果展示
-
-2. 项目原理/流程介绍
-
-3. 前置准备（如有）
-   - 所需资源清单
-   - 工具依赖要求
-
-4. Dify 平台实践步骤（参考）
-   - 应用创建和基础配置
-   - 应用流程搭建详解
-   - 关键节点配置说明
-
-5. 常见问题
-   - 开发过程中的典型问题
-   - 故障排查和解决方案
-   - 性能优化建议
-   - 注意事项和最佳实践
-```
-
-> 为了便于用户理解，建议为文章添加必要说明截图。请以在线图床链接的形式提交图片内容。
-
-我们期待你的精彩分享，一起助力 Dify 社区的知识积累！
-
 ## 获取帮助
 
 如果你在贡献过程中遇到困难或者有任何问题，可以通过相关的 GitHub 问题提出你的疑问，或者加入我们的 [Discord](https://discord.com/invite/8Tpq4AcN9c) 进行快速交流。