Fragments

Fragments are chunks of code that enhance the functionality of a Site Studio Web site. They are essentially containers for HTML, Idoc Script, JavaScript, JSP, ASP, and referenced files (images, CSS, includes, and so on). Examples of fragments would be a breadcrumb trail, a navigation bar, or a copyright notice in a footer.

The fragment specification is written in XML and is stored in a fragment library (along with other fragments, if you choose). The fragment library comprises a single XML file that describes its contents and a zip file that stores all of the assets used by each fragment. Fragment libraries are stored in the content server. Several default fragment libraries with many predefined samples are automatically checked in when you install the Site Studio component on the content server.

The predefined fragments come in four categories: navigation fragments, dynamic list fragments, static list fragments, and other fragments. Each category contains a variety of fragments in multiple scripting languages. You can use any fragment as-is or copy and edit the fragment to suit your needs. You can also create fragments from scratch. See Sample Fragments for details on the fragments provided with Designer.

As you start building your own fragments, you should create your own fragment libraries for these fragments. This offers several benefits:

• You can easily track and organize where your fragments are.

• You can easily move, copy, or back up your fragments when they are stored in your own fragment library.

• You will not inadvertently alter a fragment created by another designer, which affects the Web sites currently using that fragment.

• If you create a fragment from an existing fragment, you can easily revert to the original fragment, if need be.

See Working With Fragments for more information.