The WebWorks Reverb and WebWorks Reverb 2.0 formats are treated as formats or targets, depending on how you use them. In the installation folder, the Formats folder contains plugin folders for each of the Reverb formats. These plugins are also called skins.

Initially, when you create a project that uses a Reverb format, ePublisher uses a default skin. In this case, it is considered a format. ePublisher uses the following skins as a basis for the default Reverb skins:

However, if you select a skin from the Targets Settings dialog box, then the output is considered to be a target.

Technically, the skins are built-in overrides to the default format. Each plugin folder has files that are overrides to the files in the installation folder. It is important to understand, however, that different plugin folders do not necessarily contain the same override files. For example, in the WebWorks Reverb 2.0 format, the Corporate skin has an override for the Connect.asp file, but the Classic skin does not.

When you create an override for a skin on the Manage Format Customizations tab, ePublisher copies the file from the installation folder.

When you create an override for a skin using the Manage Target Customizations tab (assuming that you have not created an override in the equivalent format file), the file is copied from the plugins folder providing that there is a matching file for that skin. If there is no matching file in the plugins folder, then the file is copied from the installation folder. So in our previous example, the Connect.asp file would be copied from the plugins folder for the Corporate skin, but from the installation folder for the Classic skin.

Your project might be more complicated and include format AND target overrides for a skin. The following table describes where the files are copied from depending on the type of override you create.

If you have multiple targets that use the same skin, it is good practice to make as many overrides as possible at the format-level. Any overrides that need to be made to the same files at the target-level should be made after all the format-level changes are made. This should help minimize the number of overrides that you need to maintain. However, if you must make overrides at the target-level that do not have overrides in a matching format-level file, you will have to make the same overrides for every target that you have.