The Toolbox in Designer displays all of the fragments that are available to you as you build your web site. For a description of these fragments, see Section C.4, "Other Fragments." Other Fragments: This category contains miscellaneous fragments that you may find useful for your site (a copyright line, an embedded Flash presentation, a dynamically converted native document, Manager, and so on). Contributors can then use the Contributor application to add, remove, and edit rows and columns of information in the list (see Section C.3, "Static List Fragments"). Static List Fragments: This category contains fragments that provide advanced contribution features for your web site, specifically the ability to create a structured layout of elements (WYISIWYG, plain text, image, and custom). Contributors can then use the Contributor application to add, remove, and edit the files in the list (see Section C.2, "Dynamic List Fragments"). For a description of these fragments, see Section C.1, "Navigation Fragments."ĭynamic List Fragments: This category contains fragments that provide advanced contribution features for your web site, specifically the ability to query for contributor data files and native documents in the content server.
See the fragments meaning update#
Consequently, you can update and change your site hierarchy, and those changes are seen immediately on your web site. The beauty of a navigation fragment is that it automatically reads your existing site hierarchy and converts the sections into hyperlinks that display in a navigation menu. Navigation Fragments: This category contains fragments that provide site navigation for your web site (navigation bar, breadcrumbs, search box, and so on). The sample fragments are available in the Toolbox and are divided into four categories: The fragment can then be used in any situation, whether it is on a page template, a subtemplate, or a region template.įigure 13-1 Sample Fragments in the Toolbox It is recommended that, whenever possible, you create fragments with a single body snippet. In both cases this can be seen in source view. When you put a fragment on a subtemplate or a region template, then a wcmFragment tag is placed in the HTML. When you put a fragment on a page template, this includes information in the XML data island, specifically in the tag.
If you place a fragment that has a snippet with a head location on a region template or a subtemplate, then the fragment cannot work. Those snippets designated with a head location must be placed on a template with a that is, they must be placed on a page template because they require the header to work.
These designations are made when creating or editing fragments in the Fragment Editor dialog (see Section A.57, "Fragment Editor Dialog").
The snippets inside of a fragment have a designated location of head, drop-point, top-of-body, or bottom-of-body. You must be aware of this distinction when placing a fragment, and also when creating and editing fragments. Subtemplates and region templates, however, do not have a section. Page t emplates, being complete HTML documents, have a and in their code.
0 kommentar(er)
