The publication process is the process which starts when the client presses button "Publish" in builder toolbar. The process can be divided into several parts which are executed one after another in specified order:

1. saving draft — this step saves website draft — the same action which is triggered when pressing button "Save Draft". This step takes <1 second; when it completes the state "preparing..." is displayed
2. website generation — during this step builder generates final website files which will be published to client's hosting. They consist mostly of .php, .js, .css and different media files. During this step the state "building website..." is displayed.
3. connection to hosting FTP server — this is the 1st step of deploying part. The builder tries to establish FTP connection with hosting server where it will publish website. The connection is made with 3 different IPs in specified order until it finally connects (when it connects with some of them it does not try the rest):
   1. IP address which was passed by hosting control panel API to builder plugin when builder was opened (in case if "Custom (API)" is used then it is defined by parameter "apiUrl");
   2. IP address of domain which was opened (in case if "Custom (API)" is used then it is defined by parameter "baseDomain" [or "domain" if "baseDomain" is not provided]);
   3. remote IP address of server which made API call to builder during opening;
   During this step the state "connecting..." is displayed.
4. logging to hosting FTP account — this is the 2nd step of deploying part. After successful connection to FTP server builder tries to log in with username and password of FTP account. Builder gets FTP data from builder plugin on hosting control panel (API) (in case if "Custom (API)" is used then FTP details are defined by parameters "username" and "password").
5. files uploading — this is the 3rd step of deploying part. During this step website files are uploaded to hosting. Note that only changed files are uploaded from last publication. This is usually the longest part. It can take from few seconds to few minutes (depending on website size and connection speed between builder and hosting servers).
6. verification — this is the 4th step of deploying part. After successfully uploaded website files (only changed) to hosting then builder makes verification whose purpose is to check if all required website files are on hosting and they are all correct. During this step builder connects to website hosting on port 80 or 443. The connection is made also with different IPs in the same order and same IPs as during builder connection to FTP server with one difference — firstly it tries IP address which could successful establish connection to FTP server. During this step the state "verifying..." is displayed.
7. files re-uploading (full) (optional) — this step is taken only in the case if verification returned negative result, that is some website file on hosting was removed or changed since last publication. During files re-uploading the connection to FTP is made again as described in step (3). When the uploading ends then no second verification is made.

Note that practically all these steps are executed quite quickly and usually client does not see them all in publication process bar.

Builder plugin is a module for hosting control panel (cPanel, Plesk, etc.) which is installed on panel and displayed for end clients as an extra button among other buttons. The builder button can be customized with your own icon and title.

The builder plugin works as a gateway from panel to site builder. Plugin purpose is to retrieve all required information of client account from hosting control panel (using internal API) and pass it to site builder. The required information includes:

• client's FTP account data (username and password)
• client's hosting IP address (which is used as FTP host in builder during publication)
• client's domain
• client's account package (if supported by panel).

After plugin collects information it calls builder via API and pass information for it. Builder checks the license of your hosting server and determines whether to let you in or not. If the license is verified then builder API returns URL otherwise it returns error message. In case if plugin gets URL from builder it redirects the client by this URL to builder where client can construct his website. If the license verification fails then builder returns error message "License is required" meaning that the license could not be detected by API call and provided parameters (check how to fix this error).

The communication between builder plugin and builder is made via HTTP port 80 or 443 depending what protocol builder uses. In case if you use Cloud builder then 443 port is always used. If you use On-Premises builder then it depends on what protocol your builder is running on.

When the client opens builder for the first time then builder suggests to choose a template first before starting constructing website. During website construction all website data is saved in special ".dat" files in builder storage and all media files which client uploads are also stored in builder. Note that during website construction in builder no changes are made on client's hosting. Changes are applied only when client presses button "Publish" in builder toolbar — then builder generates real website files (consisting of .php, .js, .css and other files) and publishes them to client's hosting via FTP connection (see how publication works in more details).
When the client next time opens builder then builder finds his ".dat" files and loads them instead of offering to choose template anew. Note that when client opens builder then builder does not download client's current website files from hosting — builder has all website data in his own storage.

The identification of website in builder is made only by domain. It means that the client can have multiple websites in his account (addon domains, sub-domains) and construct websites in builder separately for all of them. If client's domain is renamed further then it also must be renamed in builder separately. Otherwise the client will be offered to choose template anew as if the website was opened for the first time.

If you have your own hosting control system for your customers and do not use predefined hosting control panel which we support then you can also use site builder by implementing your own plugin using builder API method to create session.