Using a Page Editor vs. SiteBuilder Print

  • 0

What is the difference between a site builder and page editor?

The key difference is in how they manipulate and work with your site files. I've emphasized files because, in order for any web-page to exist, it must have a file, on a server, somewhere, and that file must contain standardized HTML code. Many hosts bundle and "blur" the lines between these distinct pieces for simplicity; however, all web-sites consist of the aforementioned parts.

Click here for a better understanding of the key elements that make up a web-site.

A Site Building program - like our SiteBuilder - is truly that. You tell it how you want the site to look, and it builds it. While it does store a history of your previous editions to the site so that you can further modify it, it does not "edit" the site files in any sense of the word. Instead, it stores everything you tell it (about how your site is structured) in a proprietary database, and when you're ready to publish, it takes that data, runs it through a script, then the script outputs a set of HTML files and images, and uploads them to the server. When you go back to make editions to the site, it does not go back to the server and retrieve what it published previously - instead, it goes into its database, and retrieves the most recent list of updates you made to the site, so you can pick up there. You can see, with a "builder" it is not editing files, rather it is creating new ones each time you publish the site. This means that, if you edit a file outside of the builder after you've published it, the builder will not take those changes into account as it does not know they exist, and will overwrite them when you re-publish. Additionally, this means that in order to move your site to another host, and pick up where you left off, you would need the new host to have the exact same builder software, and your old host would need to provide the backup of your site in the proprietary format that the builder uses, so that the new host can have the files restored exactly as they were before. This is the primary reason that professionally built web-sites are not made on builder programs.

A site editor or WYSYWIG editor literally edits the pages. When you open up the page, it connects to the server, downloads the current version of the file, parses it (like a web-browser would) and shows you what the page will look like. When you make an edit in the code manually, it shows you how the page looks after the edit. Additionally, when you make an edition through the simplified interface, it updates the code for you. Since it is literally "reading" the code, then changing it, and finally re-writing it to the server, any changes made will not be recognized by builder programs. Most professional web-designers use more than one of these editors for the same site, since you can switch between most of them interchangeably, and they usually recognize the changes made by the other software (because we're using standardized HTML, not a proprietary web-builder format.)

If you are attempting to transfer your sites, you may face these obstacles:

If you cannot obtain the site files themselves, then we won't be able to transfer the site over. All you can do is download the pages from a browser as they appear on the web. (This won't save any dynamic content - just the html structure of the page - which is a good starting point if you're going to edit the site using a WYSIWYG editor from now on.)

If you can obtain the site files, we can transfer the site, but to edit it further, you would need to use a WYSIWIG editor - our SiteBuilder/SiteStudio would not work for this.

If the site was made in SiteBuilder or SiteStudio, and the old host will give you a backup of your site in the proprietary format. Thus, you can have a setup exactly like you had before, but on HostGator. Most hosts don't want to do this, since it's extra work for them. Also, they know they're retrieving this backup because you are about to leave their company.

Keep in mind that, if you do decide to rebuild the site, and do it with a WYSIWYG editor, you won't have to redo the same custom work over and over. If you transfer to another host, you can copy everything over without a hitch, and pick up right where you left off. You may also want to look into a Content Management System, which is basically a builder and site all integrated into one, and just as portable as a site made in a WYSIWIG editor.


Was this answer helpful?

« Back

Powered by WHMCompleteSolution