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.
Everybody loves featured snippets—those handy text boxes that pop up when we search and provide quick answers to our questions without needing to click a link. They’re becoming a particularly important part of the UX as convenience becomes the norm and mobile and voice searches rise in prominence. Below is an example featured snippet...on featured snippets!

The developers of the widely used setup tools also embraced the new technology and started to offer new versions of their tools to create setup programs of this nature. However, as the experience of many developers shows, while these tools are perfectly capable of creating simpler installation packages, they often prove too limiting, inflexible when it comes to more complex requirements.
Finally, create web pages for the content you collected for the site and add the web page parts such as images, videos, headlines, and text. If a template includes pages that you don’t need, either delete those pages or save the pages as drafts. If you save the pages as drafts, you’ll have access to them in the future. There are a few essential pages that you should consider adding: