The following diagram shows how repositories are used in a content development environment.
A content development environment has three types of repositories:
Versioned Repositories store an application’s repository assets
A single Versioned Content Repository (the
PublishingFileRepository) stores metadata for application file assets.Standard Repositories store data required by ATG Content Administration.
Asset Types
Project assets are of two types: repository assets or file assets. The following table briefly describes how repository and file assets are maintained in content development and production environments:
Asset type | Content development environment | Production environment | Examples |
|---|---|---|---|
Repository asset | Stored in a versioned repository or versioned content repository , an instance of a | Stored in a standard repository (instance of | news articles, press releases, and other custom item types; ATG Commerce assets, such as product catalogs |
File asset | Metadata is stored in a versioned content repository, an instance of Exposed via a ContentRepositoryVFSService virtual file system for use in various contexts, such as deployment. | Stored in a virtual file system. | ATG personalization and scenario assets, namely, targeters, content and profile groups, user segments, scenarios, and slots; JSPs and JSP fragments; static text files, such as HTML and ReadMe files; and binary files, such as Microsoft Word files and PDFs |
