You can reference an entire site or section of a site from Site view. For example, you might reference an existing site you want to manage with Corel Website Creator X6 now and convert later. Or, you can reference files you prefer to maintain in their native code.
For links to work between the HTML files you reference, use relative path names in the original <A HREF> tags, keep all HTML files in the same directory, and publish files using the same directory structure as the original site. See Managing Referenced Assets for information.
When you reference HTML from Site view, Corel Website Creator X6 publishes the <HEAD> content from the original files, along with <HEAD> content it generates.
In Site view, select the page to be the parent of the pages you reference.
From the File menu, choose Reference External HTML.
The Reference External HTML dialog appears.
Click Browse.
The Open dialog appears.
Select the top-level HTML file you want to reference, and click Open to return to the Reference External HTML dialog.
Assign MasterBorder. Choose a MasterBorder from this drop-down list. Each HTML file you reference occupies the Layout area of a page, while the MasterBorder gives pages the consistent look of your site. To display external content with its original look, choose ZeroMargins. If the HTML contains frames, you must choose the ZeroMargins MasterBorder.
Limit number of pages to. Select this option to enter the number of files to reference. Corel Website Creator X6 begins with the Home page you select and stops referencing when it reaches the end of the site or the number of pages entered here.
Corel Website Creator X6 only follows <A HREF> links; it cannot follow links in JavaScript or cgi scripts.
Down to structural level. Select this option to enter how many levels of your SiteStructure to reference. Corel Website Creator X6 references as many pages as possible at a higher level before going to a lower level.
Do not manage or move assets. If you select this option, Corel Website Creator X6 doesn’t copy external assets into Assets view. Do this if you prefer that path names in the published HTML not be edited from your native code. However, you then have to manage images and other assets yourself. See Publishing Unmanaged Assets