# Mini Program Template Library Management

# I. Overview

  • The path of the third party generation development Mini Program is as shown in the figure below. When the code is submitted to the draft box, it needs to be added to the template library to submit the code. Therefore, the Mini Program template library is introduced to store the Mini Program code developed by the service provider. If you use directCommit mode to submit code, you do not need to go through the template library, details can be foundThird-Party Mini Program Development Model Dxplaination
  • The storage number of the Mini Program template library is 200(The standard template library and the ordinary template library are 200, respectively, and the template id of the two template libraries will not be duplicated), so please be careful to clean up the unwanted Mini Program templates in time

# II. Details of the operation of the Mini Program template library

  • The Mini Program template library is divided into standard template library and ordinary template library, and the operating steps on the third-party platform are as follows:

# 1. Add code from the draft box to the template library

  • Click "Add to Template Gallery" Select Standard Template Library to add your draft box code to the standard template library

  • Click "Add to Template Gallery" Select Normal Template Library to add your Draft Box code to the normal template library

# 2, remove the template

  • Select the template, click the details, you can delete the template

# 3, standard template submitted for review

  • Note: The template that is under review and has passed the audit can not be submitted for reviewUnaudited and unaudited templates can be submitted for audit

  • You need to select the scene label when submitting the template for review (currently only supports the transaction component one scene, Different scenarios have different audit requirements), service category (the service category is the same as the service category content of the Mini Program, and it is also a maximum of 5 optional) and extjson (this field is not required, it is mainly used to generate the experience version of the Mini Program for audit.Failure to build the demo will also result in an audit failure, so submit ext as it is_json)

  • Note: If the template involves the introduction of Mini Program plug-ins, it is not supported to submit as a standard template, that is, it is not possible to submit this template for review

# 4, the standard template review results

Service providers can obtain the results of template audits in the following ways:

1, by logging on to the open platform, view the station letter way to get

2, the third-party platform administrator can be obtained by receiving the template message

  1. Third-party developers can alsogettemplatelistObtain

4, the follow-up will support the audit results pushed to the third-party platform message and event URL way

# III. Introduction to the Standard Template Library

# (one)Difference between standard templates and common templates

1, the biggest difference between the ordinary template library and the standard template library is that callingSubmit Code InterfaceWhen, ext_JSON supports different passwords.

  1. If it is a template from a normal template library, ext_Json supports more parameters, details can be found:Ext.json-specific fieldsas well asMini Program Configuration Documentation

  2. If it is a standard template library, ext_Json supports only {"extAppid": ", "ext": {}, "window": {}}

# (two)Standard Template Library

  • The main purpose of the standard template is: based on the Mini Program code submitted by the standard template that has been reviewed and approved, under the condition that the category meets the requirements and other conditions, it can enter the "standard template Mini Program" audit queue to accelerate the review, and then submit the release, and improve the release efficiency.

  • After arraignment, enter the "standard template Mini Program" audit queue. The conditions for speeding up the audit are as follows(The following conditions must be met at the same time):

1, the Mini ProgramSubmit CodeStandard templates are used. Can be accessed throughgettemplatelistTemplate returned by the interface_Type to judge

2、1 The standard templates used in thegettemplatelistThe audit returned by the interface_Status to judge

3, the service category configured by the Mini Program belongs to the category whose standard template has been reviewed (for example, the template is configured with a/b/c/D These four secondary categories, the Mini Program is configured b/C these two secondary categories, then the Mini Program category meets the conditions of automatic review), which can be passed through thegettemplatelistThe category returned by the interface_List for viewing.

4、 The current Mini Program has opened a custom transaction component, andGet Access StatusAccess returned by the interface_The content inside the info is 1 (completed) state.

5, to meet the other requirements and specifications of the Mini Program code review, details can be viewedhttps://developers.weixin.qq.com/miniprogram/product/reject.html