Add-ons documentation → For Builder

Adding custom templates available since version 4.0.0 / 3.7.23 On-Premises

To create custom templates in builder, take the following steps:

access builder as admin by expanding your on-premises brand, going to section "Custom templates" and clicking Create custom templates button;
choose a desired template and rebuild it at your wish;
when you are done save new website hovering Publish button and clicking on Save as...;
fill the form for a new template

Note: Checking Overwrite existing template will overwrite the current template without the possibility to restore it
;
click Save Draft and you are done.

All templates are stored under "[builder_path]/templates" directory. If you want to remove some template, just remove appropriate directory.

Notes:

If you want your template to be automatically translated to other languages (not only one language) use existing phrases from different templates in English. If you want your template to be single-language then save it with option Do not translate selected.
If you want your template to be not visible for your clients then check option Make private. This works only with your custom templates but not with built-in default templates (to hide default template scroll below to section "Hide template" for more information).

Remove custom template

To remove template, just delete appropriate folder of created template "[builder_path]/templates/[category]/[template]".

Add/remove category

To create a new category in builder, take the following steps:

navigate to "[builder_path]/templates" directory;
add a folder with a desired category name;
access builder as admin clicking on Create custom templates button, create a website and save it as described above.

To remove a category, just remove appropriate category directory.

Note: Do not remove native builder templates and categories, since with the next builder update, they will appear again. Use Hide category and Hide template methods instead.

Important: Be careful not to accidentally remove all templates within some category.

Hide category

In order to hide some category, take the following steps:

navigate to "[builder_path]/templates/[category you want to hide]" directory;
create file "config.json" there with contents {"isPrivate":true} and save file;
remove cache file "[builder_path]/templates/index.json".

After that your clients will not see this category on template chooser page.

Hide template available since version 4.0.0 / 3.7.304

In order to hide some template, take the following steps:

open "[builder_path]/templates/[template category]" directory;
create file "config.json" there with contents {"privateTemplates": ["Template One", "Template Two"]}. Replace "Template One/Two" with name of template(s) you want to hide in that category (names must be specified in English language).

If file "config.json" already exists and has some content then you need to add "privateTemplates" parameter to that file.
remove cache file "[builder_path]/templates/index.json".

After that your clients will not see templates you hide in this category.

Enable/disable templates by hosting plan available since version 4.0.0

There is a possibility in builder to have specific templates enabled (or disabled) depending on hosting plan the customer has. In order to activate this feature create file in your builder installation templates/plans.json with the following structure:

{
    "list": [
        {
            "hostingPlan": "plan1",
            "templates": [
                "ID of template 1",
                "ID of template 2",
                ...
            ]
        },
        {
            "hostingPlan": "plan2",
            "templates": [
                "ID of template 3",
                "ID of template 4",
                ...
            ]
        },
        ...
    ]
}

There hostingPlan can be a plan or list of plans, e.g. ["plan1", "plan2"].

The template ID is a string which is constructed from category name and template name in English language (you can see real names of categories and templates in folder "templates" of your builder installation), for example:
"Services/Accounting"
"E-commerce/Happy Walls"
etc.

{
    "list": [
        {
            "hostingPlan": "plan1",
            "action": "exclude",
            "templates": [
                "ID of template 1",
                "ID of template 2"
            ]
        },
        ...
    ]
}

If you want to have a plan or plans where only few templates are disabled and all other are enabled then it is not necessary to list all templates in the file, instead you can add extra parameter "action": "exclude" as shown in an example.
In specified example the plan "plan1" will have all templates available except templates "ID of template 1" and "ID of template 2".

{
    "templateBundles": [
        {
            "id": "group1",
            "list": [
                "ID of template 1",
                "ID of template 2",
                ...
            ]
        },
        {
            "id": "group2",
            "list": [
                "ID of template 3",
                "ID of template 4",
                ...
            ]
        }
    ],
    "list": [
        {
            "hostingPlan": "plan1",
            "templates": [
                "bundle:group1",
                "ID of template 5",
                "ID of template 6",
            ]
        },
        {
            "hostingPlan": "plan2",
            "templates": [
                "bundle:group1",
                "bundle:group2"
            ]
        },
        ...
    ]
}

If you have many plans for which the similar group of templates is enabled (or disabled) then it is not necessary to repeat the same list of templates for multiple plans, instead you can use parameter "templateBundles". There you specify groups of templates as shown in an example and then use IDs of those groups in parameter "templates".
It is convenient when you want to enable/disable whole categories of templates by hosting plans. Then you can split all templates into bundles where each bundle will represent different templates category.

Note: If you use this feature of plans.json file then the option "Templates in Each of 22 categories" in section "Edit Plans" will be ignored.