When you build content, you create, edit, and link various documents that are stored in the Library folders. The Developer provides the various document types that allow you to: 

• create an outline to facilitate content presentation and navigation
   
• record application simulations for playback
   
• construct conceptual and introductory content that link to outlines and recorded frames
   
• develop glossary terms
  
• define roles for document filtering
   
• create questions and assessments to evaluate skills, competency, and learning
   
• apply consistent formatting to web pages
   
• customize publishing style output

The following describes each document type:

 Module: A module (purple book) is used to organize a specific unit of learning. It can contain other documents such as sections, topics, or even other modules to form a component of an outline.

A module can also have conceptual content linked to it that provides a general description of the content that is contained within it.

 Section: A section (blue book) is very similar to a module in that it also can contain other documents such as sections, topics, or other modules. The main difference between a section and module is its visual representation that can help you differentiate between the components of your outline and locate areas in the structure faster.

A section can also have conceptual content linked to it that provides a general description of the content that is contained within it.

Important Note about Module and Section Documents: A module or section document appears as a purple or blue book only when the document has at least one linked child document such as a topic or another module or section. However, a module or section document with no linked child documents appears as a page icon such as for module and for section. When you create a new module or section, it automatically appears as a page icon until you link at least one additional child document. It then appears with a purple or blue book icon. 

 Topic: A topic represents a series of recorded steps that complete a task in an application. Topics are where you record application-specific transactional content; whereas modules and sections provide the structural components of your outline.

 Package: A package is a collection of one or more files that can be imported and attached to documents as additional content. For example, a package can be as simple as a document that contains an image file or more complex where it contains multiple files that comprise an entire web site.

 Web Page: A web page is an HTML page that can contain text, audio, images, and hyperlinks to other content. It can be linked to modules and sections or frames and bubble text within a topic.

Question: A question tests student knowledge on a piece of content. There are seven types of questions including Fill in, Hot Spot, Matching, Multiple Choice (single answer) Multiple Choice (many answers), True/False, and User-Defined. 

Assessment: An assessment is collection of questions and topics used to test a student's knowledge of larger portions of content. 

 Glossary: A glossary is a list of specialized terms unique to your company, or terms that require further clarification for your users.

 Role: A role generally represents the actions and activities assigned to or required or expected of a person or group. A role is used to filter topics in the Player.

 Template: A template controls the bubble text that is automatically populated when you record a topic.

 Publishing Project: A publishing project contains all of the files that are used in a publishing style. For example, the Training Guide publishing project has various Microsoft Word documents and XML files that control the output format of this style. You can customize a delivered style by copying the relevant publishing project document and editing the files to define your custom style.

 Style Sheet: A style sheet is a collection of styles that can be used to apply formatting to text and objects in web pages.

 Skin: A package, similar to the Player publishing project, that contains all of the customized settings and images for publishing a customized Player. You can select a skin when publishing a Player or set a default skin. Customizations made in a skin are preserved product upgrades.

 IAS Configuration: A document, used to configure content for SmartHelp or help integration, which contains options that allow you to associate the configuration with specific content, control launch behavior, and set up rules for the context search.

Table of Contents  Back