Everything a custom template needs is contained in the single sub-folder named for the template under webAppDir\templates\views or webAppDir\templates\components, depending on the type of template. This sub-folder contains additional folders and files required for both project design and code generation.
For example, the sub-folder for the custom-data-grid view template contains:
angularjs — A folder containing everything required for a web app that is generated to run in the AngularJS framework.
design-time — A folder containing everything required to visualize the template at design time, specifying what you see in the Designer.
custom-data-grid.json — A JSON file that provides the schema definition for the view, what properties it has that will be stored as meta-data, and how they are presented in the VIEW PROPERTIES pane on a view design page.
The sub-folder for the custom-slider component template contains:
angularjs — A folder containing everything required for a web app that is generated to run in the AngularJS framework.
design-time — A folder containing everything required to visualize the template at design time, specifying what you see in the Designer.
custom-slider.json — A JSON file that provides the schema definition for the component, what properties it has that will be stored as meta-data, and how they are presented in the COMPONENT PROPERTIES pane on a Blank view design page.
Note that custom templates are designed to support additional target web app frameworks in the future. For example, if Kendo UI Builder supports the generation of web apps using the Angular framework, an additional folder with an appropriate name (such as angular) will be included under the template sub-folder.
Caution: Custom templates must be edited with extreme care. Always make a backup copy of the template folder or ensure that the app project folder is under source code management before editing any of its files.