Merge pull request #75 from langgenius/docs/opt-plugin-development

Remove docs json and optimize plugin development
This commit is contained in:
AllenWriter
2025-05-14 11:12:00 +08:00
committed by GitHub
2 changed files with 5 additions and 1390 deletions

File diff suppressed because it is too large Load Diff

View File

@@ -7,9 +7,7 @@ dimensions:
standard_title: Contributor Covenant Code of Conduct
language: en
title: Plugin Development Guidelines
description: >-
To ensure the quality of all plugins in the Dify Marketplace and provide a consistent, high-quality experience for Dify Marketplace users, you must adhere to all requirements outlined in these Plugin Development Guidelines when submitting a plugin for review.
By submitting a plugin, **you acknowledge that you have read, understood, and agree to comply with all the following terms**. Adhering to these guidelines will help ensure your plugin moves quickly and smoothly through the review process.
description: To ensure the quality of all plugins in the Dify Marketplace and provide a consistent, high-quality experience for Dify Marketplace users, you must adhere to all requirements outlined in these Plugin Development Guidelines when submitting a plugin for review. By submitting a plugin, **you acknowledge that you have read, understood, and agree to comply with all the following terms**. Following these guidelines will help your plugin get reviewed faster.
---
## 1. Plugin Value and Uniqueness
@@ -45,7 +43,7 @@ description: >-
- Do **not** link to 404 pages or pages that return errors.
- Avoid excessive spelling or punctuation errors.
- **User Data Use**: Data collected should be used only for connecting services and improving plugin functionality.
- **User Data Use**: Use collected data only for connecting services and improving plugin functionality.
- **Error Clarity**: Mark required fields and provide clear error messages that help users understand issues.
@@ -71,7 +69,7 @@ description: >-
Plugins must not mislead users. Do not create plugins for spamming, phishing, or sending unsolicited messages. Attempts to deceive the review process, steal user data, or impersonate users will result in removal and possible bans from future submissions.
- **Prohibited: Offensive Content**
Plugins must not contain content involving violence, hate speech, discrimination, or disrespect toward global cultures, religions, or users.
Plugins must not contain violent content, hate speech, discrimination, or disrespect toward global cultures, religions, or users.
- **Prohibited: Financial Transactions**
Plugins must not facilitate any financial transactions, asset transfers, or payment processing. This includes token or asset ownership transfers in blockchain/crypto applications.
@@ -95,7 +93,7 @@ description: >-
- **Authorization Required**: Ensure you have rights to use any logos or trademarks submitted.
- **Verification Rights**: The review team may request proof of authorization if third-party logos are used—especially if they clearly belong to known brands.
- **Verification Rights**: We may ask you to prove you have permission if third-party logos are used—especially if they clearly belong to known brands.
- **Violation Consequences**: Dify reserves the right to ask for changes or remove the plugin if unauthorized use is found. Complaints from rights holders may also result in removal.
@@ -140,7 +138,7 @@ description: >-
- What is shared with third parties (with their privacy links if applicable).
- **Review Focus**:
- **Formal Check**: Ensure data collection statements are declared.
- **Formal Check**: Make sure you declare what data you collect.
- **Sensitive Data Scan**: Plugins collecting sensitive data (e.g., health, finance, children's info) require additional scrutiny.
- **Malicious Behavior Scan**: Plugins must not collect or upload user data without consent.