Overview of the Community Template
This section contains the following:
What Is A Community Template?
A community template is comprised of a set of services (channels) and the visual layout. However, the layout is not always dictated by the community template as in the case with wiki community template where the layout is dictated by the wiki itself. Community templates define (in the role display profile document) the type of services available for the community, the default settings for each service, and the containers that bind the services.
Physically, a community template is a properties file, and image, plus one or more display profile documents. There are display profile documents, one per community role (such as OWNER, VISITOR, MEMBER). Each role template defines services and the layout associated with the particular role (see Managing Membership for more information on these roles). The content of the role template is represented in a display profile document. In essence, a community template contains the logic for handling different roles (one display profile document per role) and depending on the one or more roles, you get a different set of services and a different layout. There are also display profile documents to customize the content when communities are marked for deletion (deleted.xml) or disabled (disable.xml).
Communities are created from a community template. The system may have any number of community templates. In the Enterprise Sample, end users choose a community template when they create a community.
How Are The Templates Stored?
The community templates are stored on filesystem. Community templates are stored in PortalServer-DataDir/portals/portal-URI/communitytemplates directory (referred to as communityTemplateBaseDir). Note that this means that each Portal (in a multi-portal deployment environment) will and must have its own set of community templates. The resource bundle in communityTemplateBaseDir defines the meta data associated with each template. In addition, each template has its own directory where the role templates are stored.
Example 9–1 Sample communityTemplateBaseDir
communityTemplateBaseDir -+-- template1 -+-- deleted.xml
| |
| +-- disabled.xml
| |
| +-- member.xml
| |
| +-- owner.xml
| |
| +-- visitor.xml
|
-+-- template2 -+-- deleted.xml
| |
| +-- disabled.xml
| |
| +-- member.xml
| |
| +-- owner.xml
| |
| +-- visitor.xml
|
-+-- template3 -+-- deleted.xml
| |
| +-- disabled.xml
| |
| +-- member.xml
| |
| +-- owner.xml
| |
| +-- visitor.xml
|
+-- template1.properties
|
+-- template1_en.properties
|
+-- template1_fr.properties
|
+-- template2.properties
|
+-- template3.properties
|
+-- template3_en_US.properties
|
+-- ...
The display profile disabled.xml and deleted.xml files control the content when the community is disabled or marked for deletion. See Managing a community status for more information.
How Are The Templates Managed?
The portal administrator can add a new community template, update an existing community template, archive and restore community templates on the system, and export community templates from one portal instance to others and/or keep them in sync.
- © 2010, Oracle Corporation and/or its affiliates