|
< resource-directory >
HyperContent can be set up to work with any kind of file that has a MIME type - see thee chapter on Content Types for global configuration information. At the project level, any kind of file that is not XML can be configured in a resource-directory tag.
label =
The label of a resource directory should be a short, descriptive text describing a file which would go here. For example, if you were specifying a resource-directory for news images, you could label it "News Image".
path =
The path of a resource-directory describes a possible rather than literal location. Possibilities are expressed using wildcards: e.g. '/*/portrait.jpg indicates a jpeg file in a directory beneath the repository root; '/*/*' indicates a file one level down in the repository. Wildcards are replaced with actual names by authors at the time they create a new file matching this pattern. The file extension will be based on the content type of the file created. For a more complete explanation and examples, see the chapter on path patterns.
publish = (true | false)
Indicates whether the resources should be published or not. For example, you would normally want image files to be published, while you may not find it necessary to publish DTDs.
< content >
A resource directory is configured to accept one or more type of content with content tags.
type =
The MIME type of an allowed type of file for this directory.
Overriding Default Editors By default, files will be configured to use the default editors for their MIME type as configured in the Content Types file. You can override the defaults for files in a resource directory by adding editor elements inside it. You must specify all the editors that you want to be used; once you add an editor element, the defaults are ignored. The editors appear in the order you specify them: thus, the first editor element will be the opening screen for an author who chooses to edit a file corresponding to this resource-directory.
< editor >
The editor element has a single attribute:
key = (see the chapter on Editors)
|
| |