Using the Portal Manager for content development
The Content Development area of the Portal Manager application is used primarily for portal customization tasks. Select to access the tree view of all customizable components. This table briefly explains each component type:
| Component | Description |
|---|---|
| Assets | Assets are the image, video, and JavaScript files used when creating portal pages. |
| Collection Definitions | Similar to back office IDOs, collection definitions identify where data is located, so it can be retrieved for access on the portal. |
| Component Sets | A component set is a grouping of portal components, which can include pages, assets, and help assets. You assign appropriate access permissions to individual component sets in the Portal Manager. |
| Feature Dependencies | Feature dependencies are used to specify feature activation conditions that must be met before other portal features can be activated. For example, you could create a feature dependency that requires the Customer Portal feature to be activated before the Reseller Portal feature can be activated. If you try to activate the Reseller Portal and the Customer Portal is not set to be activated, you would get a message about the error. |
| Field Display Formats | Field display formats (FDFs) control the format of data; for example, whether data should be displayed as text, an image, or a date. |
| Help Assets | These are the help files provided for existing portal pages. |
| Layouts | Layouts control the positioning, or arrangement, of data. |
| Managed Level-Based Schemas | This is content that specifies database schema in a progressive way. This is the type of schema that is normally used for tables. This content that can be locked, edited, and activated. See About managed schema in MSSQL databases. |
| Managed Revision-Based Schemas | This is content that specifies database schema as replaceable units. This is the type of schema that is normally used for code components such as stored procedures and functions. This content that can be locked, edited, and activated. |
| Pages | These are the portal pages. |
| Style Families | Style families, and the styles included in them, control the appearance of data, such as its color, font, or spacing. |
In the tree view, you can edit component properties and copy and organize components. There are also separate tabs for each component type, where you can add and remove components, copy components, and access the various component editors.
You can also select to work with custom content versions and to work with level-based and revision-based schema.