Visual QuickMenu
Publish Tips

1. Selecting an external file for all three sections will publish everything to a single separate file which may be shared by any number of documents. The published content under this scenario is automatically compacted for ultimate space savings, a full menu with all settings, structure, styles, and code can be as small as 6K.
2. Publishing the menus structure to an external file will not allow your links to be spidered by search engines. If you require SEO, choose the in-page option for the structure. The in-page structure may be included within a server side include for easy delivery to multiple documents.
3. Any portion of the menu may be generated by a server side include for delivery to multiple documents.
4. If you are using a FrontPage shared border or Dreamweaver template choose external file for all three publish sections. You can get away with in-page under this scenario, however the sections must all be included within the template or shared border document. This violates the instructions presented within the publish wizard, however the menu will still function correctly.
5. If you do not paste the sections as instructed within the publish wizard your menu may not validate.
6. Positioning your menu within a constricted width will cause display issues, especially with horizontal menus. The reason for this is that the scalability of the menu requires that there is enough container space to accommodate the natural expanded width of the menu. If the width is not made available, horizontal main menu items may wrap to the next line. To overcome this, define a fixed width on the menus containing element, or re-work the HTML surrounding the menu so enough width is available to accommodate the maximum space which may be occupied by the main items.

Copyright (c) 2007, OpenCube Inc., All Rights Reserved.