In Release Management for Custom Plugins, developers can apply to publish a plugin to the Plugin Market. After the publishing application is approved, a company can, based on its own needs, choose to list the plugin in the Plugin Market or share the installation link with others.
Note: The Publish permission is independent of the Custom Plugins permission. Currently, the Publish Plugin permission is not available to all users who can create custom plugins. To obtain the Publish permission, please contact the operations team in advance. For contact details, see the Onboarding Application Phase.
Publish and Review
After plugin development is complete, you must complete both of the following steps:
On the Release Management page, click Apply to Publish Plugin. The plugin will then be published to the platform and enter the review stage.
In the attachment section of the Plugin Development Project Application Form, submit the necessary materials to the Jodoo Open Platform for verifying plugin quality and security, such as test case documentation and performance test reports. Then, select Published; please accept in the Confirm Plugin Delivery field.
Publishing a Plugin
1.Request Publish the Plugin
The developer enters the details page of the plugin to be published, and clicks Request Publish the Plugin under Publish Management >> Release Information. When publishing the plugin, you can specify whether the plugin will be listed in the Plugin Market, provide release notes, and set the pricing plan. This helps us review your plugin more efficiently.
Note:
The installation link is an external link. Anyone who obtains the link can install the plugin. If it is a paid plugin, please deliver the link with caution.
2.Set the Pricing Plan
When publishing a plugin, you can set pricing plans for the plugin as a whole and for individual plugin functions. After selecting a pricing plan, you can continue to configure the corresponding pricing rules.
Overall Plugin:
Free: Users can install the plugin for free. However, when calling plugin functions, users will be charged according to the pricing rules of those plugin functions.
Subscription: Users pay to install the plugin based on the configured subscription package price. Multiple subscription packages can be added.
Plugin functions:
Free: Users can call the plugin function for free.
Pay-per-use: Users are charged based on the number of times they call the plugin function.
Notes:
Whether a plugin developed by a developer is free or paid is defined by the platform. Developers can view this information on the plugin requirements board. By applying to develop the plugin, the developer is deemed to have agreed to the pricing type defined for the plugin.
Plugin pricing and payment methods must be discussed and determined jointly by the developer and the platform.
Plugin prices must be set reasonably based on actual development costs. Developers must not intentionally inflate prices to obtain improper benefits.
3.Review Time
After the publishing application is submitted, we will complete the review within 3–5 business days.
4.Review Status
During the review period, when viewing the publishing information, you can see the plugin’s review status in Current Publishing Information and Version Publishing Records, as shown below:
Note: The acceptance result of your developed plugin will be provided through the Plugin Development Project Application Form:
If the plugin passes acceptance, the requirement status corresponding to your custom plugin will be changed to Published but Not Listed. Official staff will contact you regarding subsequent matters.
If the plugin does not pass acceptance, you must make targeted modifications based on the returned feedback and submit the plugin for acceptance again. Repeat this process until the workflow reaches This version of the plugin has passed acceptance; pending new release, which means this version of your custom plugin has passed acceptance.
5.Share the Plugin
After the plugin is published, you can share it directly with other companies for use. Copy the shared installation link and send it to subsidiaries or companies you collaborate with. After logging in, the company can click the link to install the plugin.
Reviewing the Plugin
1.Standards for Plugin Overview, Icon, and Help Documentation
The plugin overview must briefly summarize the plugin’s core functionality and be within 30 characters.
The icon must be consistent with the overall visual style of the Plugin Market. Its elements should be simple, its colors should be harmonious, and it should have a certain relevance to the plugin’s functionality.
The icon must be a jpg, jpeg, or png image within 20 MB, with dimensions of 200 × 200 px.
The icon must avoid issues such as image distortion or abnormal display.
2.Standards for the Plugin Details Page
The plugin details page must include a detailed plugin introduction, a demo video, and an illustrative image.
The detailed plugin introduction must include how the plugin is called, as well as the business pain points it addresses in real-world scenarios. The introduction should be approximately 50–100 characters.
The demo video must be in .mp4 format, with a file size of no more than 30 MB, a duration of less than 15 seconds, and an aspect ratio of 16:9. If the dimensions are incorrect, users will not be able to view the video properly. Please carefully confirm this before delivery.
Only one illustrative image is required. The image can be in jpg, jpeg, or png format, with a 16:9 aspect ratio, and must clearly show the effect of the plugin.
If a new version of the plugin is released with major changes, the above materials must be updated accordingly and provided to the platform.