Sitejet Builder: create and publish a website

Sitejet Builder lets you design a website visually from cPanel. You can start from a template, edit the content and publish it on a domain in your hosting. You do not need to code for everyday tasks, although you should check the result, the forms and how it looks on mobile.

Initial setup

1. Go to cPanel > Sitejet Builder.
2. Find the domain and check its document root.
3. Look at what is in that folder, including its subfolders: when you publish, Sitejet deletes everything (we explain this below). If it contains a website, take a backup first.
4. Use Build With Sitejet and read any warning about existing content.

Do not empty a folder to get past a warning without identifying what it contains. The editor project and the files published on the hosting are separate things. The cPanel documentation explains the actions available for creating, managing, moving and restoring projects.

Choose the template

Preview a template and check its layout at several screen sizes. Choose it for its structure and your needs: number of pages, forms, navigation and content, not just the cover photo.

Replace the sample text, images and details. Before changing the template on an advanced project, check how it affects the content and keep a restorable point.

The editor

Options menu

Here you will find settings and features such as preferences or project backups, depending on the version. Check what each backup keeps before relying on it to recover a website from before you used Sitejet.

Sidebar

Use the available elements to add headings, text, images, columns or forms. Keep a consistent heading hierarchy and describe the images that convey information.

Central area

Select a block to edit it and review its styles. Avoid adjusting everything for a single resolution: a position that works on desktop may overlap on mobile.

Top bar

Use the device views and the undo/redo options. In page management, review the title, address and navigation. If you change a published URL, plan its redirect to keep links and traffic.

The text generation tools can help you write, but check accuracy, tone and your business details before publishing. Filling in SEO fields does not guarantee rankings.

Bottom bar

The element and code navigation tools help you find what you are editing. If you edit code by hand, keep a restorable version and check how it behaves after publishing.

Publishing deletes everything in the domain folder

When you publish, Sitejet deletes all the files and folders in the domain's document root before copying the new website, including subfolders. If you have another website or application inside, for example a shop in public_html/tienda or a blog in public_html/blog, publishing deletes it. cPanel acknowledges this as a known Sitejet issue in its support knowledge base.

Before publishing, choose one of these two options:

• Publish on a domain or subdomain with its own empty folder. This is the safest option: the Sitejet website does not share a folder with anything else.
• Move the subfolders with other websites out first. Move them out of the document root with the File Manager and put them back when publishing has finished. While they are out, those websites will not be visible.

Repeat the check each time you publish if you have put content back in that folder.

If you have already published and a website has disappeared

It can be recovered from our backups. Restore only the folder of the missing website, for example public_html/tienda, from a date before you published. Do not restore the domain's whole folder: the old website would come back and you would lose the one you have just published with Sitejet.

If that website used a database, also check that it is still in cPanel > MySQL Databases; if it is missing, it can be recovered from the backups in the same way. If you are not sure, contact us with the domain, the missing folder and when you published, and we will recover it for you.

Publish and check

Saving the project does not always publish its changes. Use Publish when it is ready and open the domain in a private window to check the version being served.

Check HTTPS, the menu, links, readability on mobile and the real recipient of each form. Check the success messages and that submissions are received: a confirmation message does not prove that the email has arrived.

Do not edit the generated files separately expecting the editor to pick them up: a later publish may replace them. Make changes through the project and its publishing mechanism.

Remove or replace a published website

Keep a backup of the document root before replacing it. If Sitejet offers a point to recover the previous website, review Details > Restore and the scope of the warning before confirming.

To move a project to another domain, use the move option when it is available. Deleting files from the hosting does not prove that the editor project has been deleted. If the action you need does not appear, contact support with the domain and the result you want before deleting content.

Next steps

Update your contact information, check forms regularly and keep the project's login details. A published website needs content maintenance and checks even if it does not manage plugins like WordPress.