I would prefer to use other descriptions:
- template => source files, that are used in the UIBuilder designer to edit your app
- working files => target files, that are used in production, on publishing a container the UIBuilder composed files (js/model/styles/etc) into single ones to reduce the count of files to accelerate the first open in the browser
To get a full understanding I can recommend you separate these two features:
- publishing a UI container to the target directory
- custom domain mapping to a folder
Publishing a UI container means you can publish your ui-container into any folder, and you do not need to copy/paste files manually, the system already composes some directories and copies files into the target folder
Custom domain mapping to a folder, means you create a shortcut to get access to the directory, any sub folder will be accessible as well, so you can have mapping https://foo.bar
to the “/web” folder and by this URL https://foo.bar it opens the web folder, and if there is a sub folder “/web/test” it can be opened by the following URL https://foo.bar/test
Together both features give you a short way to build an app and then publish it to a folder and it will be available by the domain
According to backup:
when you publish something to a directory the UIBuilder system backups everything in the target directory and put it into the following folder: “/ui-builder/backups” in case the build fails it reverts previous files to the target directory