Requirements for Native Documents

A native document can be assigned to a contribution region in the same way that a contributor data file can. Native documents are added to the site in the same way that contributor data files are added to the site (create a link to the file, add the file to a dynamic list, or check the file in so that its metadata matches a dynamic list or a query performed on the site).

Unlike contributor data files, however, native documents require additional configuration steps on the server so that they appear on the Web site as intended. These steps include the following:

• You must have Dynamic Converter installed and running on the content server so that it can convert native documents into web pages.

• You must have Check Out and Open installed and running on the content server so that contributors can check out and edit a native document directly from the Web site using the menu on the contribution graphic.

• The native documents must be a supported file format of Dynamic Converter.

• By default, a blank Dynamic Converter template (one with minimal settings) is used to convert the document so that it looks similar to the original. To further customize the appearance of the web page so that it matches the site, you should fine tune the template (or templates) used to convert the document (see Using a Conversion Definition with Native Documents).

• You, or the contributors, must have the associated third-party application installed on the computer that is being used to edit the file.

• If you, or contributors, plan to add native documents to the site using a method outside of Site Studio (for example, using the Content Server check-in form, WebDAV Client, or Web Folders), then you must check those files in with the same metadata used by the site, and if necessary, a section of the site.