langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #1684] [MERGED] feat: New Plugin Submission - microCMS v0.0.1 #1778

New Issue
Closed
opened 2026-02-22 18:07:36 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:07:36 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1684
Author: @tplog
Created: 12/7/2025
Status: ✅ Merged
Merged: 12/14/2025
Merged by: @crazywoola

Base: main ← Head: suzulang-microcms-plugin

📝 Commits (4)

  • 0d53538 feat: Add microCMS Plugin by suzulang - Content Management Integration
  • 0300aaa fix: Restructure microCMS plugin directory to comply with dify-plugins convention
  • 4566829 fix: Keep only .difypkg file for microCMS plugin submission
  • 0ec1989 feat: Add GitHub repository link to plugin README

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ suzulang/microcms/microcms.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

A comprehensive microCMS plugin for the Dify ecosystem that enables seamless integration with microCMS headless CMS for content management workflows. This plugin provides three core tools: Get Content List, Get Content Detail, and Get Full Contents, supporting complete microCMS API functionality with multi-language support, concurrent processing, and comprehensive error handling.

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

This plugin does not collect any personal user data. It only uses the information explicitly provided by the user to access microCMS API. This plugin has the following characteristics:

  • Does not store user files permanently
  • Uses temporary storage only during the API request process
  • Does not collect user metadata or personal information
  • Does not track usage patterns or user behavior
  • Only requires microCMS service domain and API key credentials

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 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-plugins/pull/1684 **Author:** [@tplog](https://github.com/tplog) **Created:** 12/7/2025 **Status:** ✅ Merged **Merged:** 12/14/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `suzulang-microcms-plugin` --- ### 📝 Commits (4) - [`0d53538`](https://github.com/langgenius/dify-plugins/commit/0d53538a2f84344e61860fc7fb5b1ca7e9af84a3) feat: Add microCMS Plugin by suzulang - Content Management Integration - [`0300aaa`](https://github.com/langgenius/dify-plugins/commit/0300aaa3c707464cad21e14268f9e0a2a075b2e1) fix: Restructure microCMS plugin directory to comply with dify-plugins convention - [`4566829`](https://github.com/langgenius/dify-plugins/commit/4566829abbaf3bf88f52c1cdbff64296995902cb) fix: Keep only .difypkg file for microCMS plugin submission - [`0ec1989`](https://github.com/langgenius/dify-plugins/commit/0ec1989da0897e73ccb646d07040c498964605ba) feat: Add GitHub repository link to plugin README ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `suzulang/microcms/microcms.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> - **Plugin Author**: suzulang - **Plugin Name**: microcms - **Repository URL**: https://github.com/suzulang/microCMS ## 2. Submission Type - [x] New plugin submission - [ ] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> A comprehensive microCMS plugin for the Dify ecosystem that enables seamless integration with microCMS headless CMS for content management workflows. This plugin provides three core tools: Get Content List, Get Content Detail, and Get Full Contents, supporting complete microCMS API functionality with multi-language support, concurrent processing, and comprehensive error handling. ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> This plugin does not collect any personal user data. It only uses the information explicitly provided by the user to access microCMS API. This plugin has the following characteristics: - Does not store user files permanently - Uses temporary storage only during the API request process - Does not collect user metadata or personal information - Does not track usage patterns or user behavior - Only requires microCMS service domain and API key credentials ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <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-22 18:07:36 -05:00
yindo closed this issue 2026-02-22 18:07:36 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
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-plugins#1778
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?