Communities are sites within a portal designed for a specific audience or task, such as collaborative projects. The pages, portlets, layout, community preferences, and subcommunities within a community are determined by the community administrator. Although the community administrators determine which portlets are displayed in a community, a portlet itself might allow community members to change the content within each portlet.
You might have communities based on departments in your company. For example, the Marketing department might have a community containing press information, leads volumes, a trade show calendar, and so on. The Engineering department might have a separate community containing project milestones, regulatory compliance requirements, and technical specifications.
You are automatically subscribed to communities based on your group membership. You can also join communities on your own. Some community subscriptions might be mandatory, but you can unsubscribe from those that are not. The communities you are subscribed to appear in the My Communities menu. Some mandatory communities might also appear as tabs in the menu area.
Related Communities displays any communities that are stored in the same administrative folder as the current community.
This menu only appears if you have access to related communities.
Each community is based on a community template. Community templates define the basic structure for the resulting communities, such as which page templates to include and, optionally, a header or footer for the community. A single community template can be used by many different communities, allowing you to keep similar types of communities looking analogous. For example, you might want all communities based on departments to look similar and contain similar content, but you might want communities based on projects to look different.
Each community page is based on a page template. Page templates define the basic structure for the resulting community pages, such as the column layout and which portlets to include. A single page template can be used by many different communities, allowing you to keep similar types of pages looking analogous. For example, you might want each department to create a community in which the first page lists the general duties of the group, the department members, and the current projects owned by the department.
When you create a community or a community page, you can decide whether to inherit the underlying community template or page template. Inheriting a template has several effects on the resulting communities and pages:
Subcommunities (along with community pages) allow you to create separately-secured subsections in a community, so it can have a more restrictive security than the main community. For example, you might have a Marketing Community that includes an Advertising Subcommunity. This subcommunity might have distinct owners or might be accessible to only a subset of the Marketing Community.
A subcommunity is just a community folder stored in another community folder. Therefore, the subcommunity inherits the security and design of the parent community, but you can then change these settings to suit the needs of the subcommunity. You can also change the relationships of communities and subcommunities just by rearranging the folder structure.
The Community Knowledge Directory, if enabled, displays community resources in an organizational structure that is relevant to the community (as opposed to the broader portal audience). It includes a list of community members, displayed in the Members folder, and a list of subcommunities, displayed in the Subcommunities folder. Community administrators can also create folders that contain links to relevant web pages, community experts, portal documents, or community pages.
A community links portlet displays a snapshot of the links in a single Community Knowledge Directory folder. You can then add the portlet to a page in the community or invite users to add the portlet to their My Pages to provide quick access to the community resources. With the proper access privileges, you can also use the portlet to add or delete content from the associated Community Knowledge Directory folder.