|
|
|
|
|
The Project Directory
The project directory contains the project (.wrp) file and the manifest file as well as the directories that make up your project - such as the Data, Files, Targets, Formats, Logs and Output folders.
Figure 5-2 illustrates a sample project directory. Each folder in the project directory contains the files associated with your project. See Table 1 for more information on the contents within each folder.
Figure 4-2: Sample Project Directory
|
Table 1: Folders in the Project Directory |
|
|---|---|
|
Contains information about how files in your project have been processed. The .wif files, which are located in the Data folder, contain style and content information from your source documents. |
|
|
The Files folder contains the user files that are used in your project. Typically, the Files folder will contain logo images, css files, custom bullet images, and custom background images. |
|
|
The generate.log file lives in the Logs folder. It contains the information from the Log window of your project. |
|
|
All generated output files live in the Output folder. Each target will have its own folder within the Output folder, and each target folder contains all topic pages, generated images, PDFs, entry-point files, and merged Help files generated for that output. |
|
|
The Formats folder contains format overrides and all of the necessary files to generate output for the desired format. Any time you want a format to inherit a specific override, place the override in the Formats folder. For example, if you would like to override Page.asp for all targets that use WebWorks Help 5.0, place the override in the Formats directory. |
|
|
The Targets folder contains target overrides. Anytime you want to override a file in a target, place the override in the Targets folder. ePublisher Express looks for overrides in this directory before looking in the Formats directory. If an override does not exist for a file, ePublisher Express will then look in the Formats folder. |
|
