Traditional setup tools used a programmatic, script-based approach to describe the various steps involved in the deployment of the application to be installed on the target machine: files to be copied, registry settings to be created, device drivers and services to be started. The technology behind Windows Installer, while it maintains a comparable look and feel for the end user, underwent important philosophical changes. The fundamental change was to move from the imperative description to a declarative one: rather than to describe the individual steps of installation, the declarative form specifies the state the target machine should be left in after various phases of installation and uninstallation. While the imperative description seems to be quite sufficient until some error occurs, the declarative one makes it possible to cope with unexpected conditions, differing target machine environments, aborted installations, shared resources. It is of paramount importance for setup developers to make sure that whatever happens during the process, the target machine should be left in a known, stable state, without introducing any detrimental side effects.

In addition to this integration, providing basically nothing more but developer comfort, WiX offers another level of integration, far more advantageous than the first one: the integration of the setup development process with that of the application. Traditionally, setup programs were only written when the main application had already been finished; often even by different developers. This approach requires a tedious and error prone process of collecting information about all the resources making up the application. While the files themselves are usually obvious, registry entries, services and most forms of inter-resource dependencies are often hard to reconstruct in a later stage: if solid development documentation is lacking, the setup developers have to collect all pieces of information from the original developers or try to extract it from the source code.
The major player in the blog game is WordPress, a content management system (CMS) that powers millions of websites, including The New York Times, Quartz, and Variety. WordPress-powered sites are incredibly easy to set up, customize, and update—ideally on a daily basis. You aren't required to learn fancy-schmancy FTP tricks (though you can certainly use them if you like), and there are ridiculous numbers of free and paid WordPress themes and WordPress plug-ins to give your website a pretty face and vastly expanded functionality. Though WordPress dominates the blogging space, it isn't the only blogging CMS of note, however.
Hi Glyn, You can indeed keep your domain name. Domain registration is a separate process to site building, so there's no risk of getting one stuck on a platform you don't want to use any more. Wix is great at walking you through the domain transfer process step by step when you sign up. There's an official video guide here if you'd like a sense of how it's done. Hope that's helpful! Ta, Fred

A website is a collection of many types of content. Your website can contain a collection of content including blog posts, product descriptions, images that highlight your product, explainer videos that tell your story, and contact information. These different types of content have one thing in common. Each piece of content has seconds to capture the attention of your audience.

×