Displaying and Configuring the Community tab

About the Community tab

The Community tab is an optional component that you typically configure to provide users with a description of the purpose of a site and to provide helpful information, for example, site policies. When it is configured, the Community tab appears between the Project and Administration tabs.

When you configure the Community tab you can use the www directory in the version control repository of the www project to build out the Community home page. The HTML content in the www directory can be built out so that the Community tab is the home page of an entire web site. For example, on open source sites, such as www.tigris.org and www.openoffice.org, the Community tab is the location for the entire community-built web site. 

When you enable the Community tab it becomes the landing page for users when they enter www.domainname.com where domainname is the name of your local domain.

Structure of the Community tab

The Community tab consists of a set of files that are located in the version control repository of the www project, in a directory named www. These files consist of the following:

A complete listing of Community tab files is as follows:

File Name Description
DomainFAQ.html.html This page is displayed when you click the Site FAQ link at the bottom of every page. CollabNet provides an example page that you can extend or replace.
DomainFAQ.html.ja A localized version of the Domain FAQ (Japanese).
DomainFAQ.html.ko A localized version of the Domain FAQ (Korean).
DomainFAQ.html.zh-cn A localized version of the Domain FAQ (Simplified Chinese).
DomainFeedback.html.html This page is displayed when you click on the Feedback link at the bottom of every page. CollabNet provides an example page that you can extend or replace.
DomainFeedback.html.ja A localized version of the feedback page (Japanese).
DomainFeedback.html.zh-cn A localized version of the feedback page.
DomainHome.html.html The Community home page.
DomainHome.html.ja A localized version of the Community home page.
DomainTermsOfUse.html.html A template for your own terms of use.
custom_404.html.html Default text for the 404 error page. You can edit or replace this page.
custom_404.html.ja A localized 404 page.
robots.txt A file that is used to exclude files or directories from being searched by web crawlers. This file is used in domain-wide searches with external crawlers.
CommunityNewsRightColumn.html.html A template that you can use to lay out your Community News section on the Community home page and user start page. If this page is removed from the project, the Community News column is not displayed.

Configuring the Community tab

You must activate the display of the Community tab. By default, it is hidden. The tab has a number of configurable options, including:

To activate the display of the Community tab:

  1. Log in as a domain administrator.
  2. Click the Administration tab, and click Configure > Domain.
  3. Check the check box for Enable community section under the Site content heading.
  4. Click Save settings.
  5. Log in from another browser window and see if the Community tab exists.

To direct the user to the Community home page after login:

  1. Log in as a domain administrator.
  2. Click the Administration tab, and click Configure > Domain.
  3. In the Destination on login drop-down list, select Community home.
  4. Click Save settings.

To build out the Community home page:

  1. Log in as a domain administrator.
  2. Click the Projects tab.
  3. Click the www project.
  4. Click Version control in the left-hand navigation pane.
  5. Click the www top-level folder.
  6. View DomainHome.html.html.
  7. Using your version control tool, edit DomainHome.html.html and add other pages that link to this page.

To edit the Community News column on the Community home page:

  1. Log in as a domain administrator.
  2. Click the Projects tab.
  3. Click the www project.
  4. Click Version control in the left-hand navigation pane.
  5. Click the www top-level folder.
  6. View CommunityNewsRightColumn.html.html.
  7. Using your version control tool, edit CommunityNewsRightColumn.html.html.
    Note: If you do not wish to display community news, you can delete the contents of this file.

To activate the display of Categories and Site Announcements on the Community tab:

  1. Log in as a domain administrator.
  2. Click the Administration tab, and click Configure > Domain.
  3. Under the Site content heading, check the check boxes for Show site announcements on user's start page and Community home and Show top-level categories on user's start page and Community home.
  4. Click Save Settings.
  5. Log in from another browser window and see if the Community tab exists.

To add entries to the Categories list on the Community tab:

  1. Log in as a domain administrator.
  2. Click the Projects tab.
  3. On the main Projects page, click the Categories sub-tab.
  4. Click the Create new category link.
  5. Add information for a new top-level category and click Create category.
  6. Click the Community tab.
    The new category appears under the Top-level categories heading.

To add entries for the Site Announcements list on the Community tab:

  1. Log in as a domain administrator.
  2. Click the Projects tab.
  3. Click the link for the www project.
  4. Click Announcements and add a few announcements.
  5. Click the Community tab.
    The announcement appears under the Site announcements heading on the tab. If the tab has been extended to multiple pages, the announcements appear on the landing page, or home page, for the tab.
    Note: For any announcement (created from www or another project) click the Announcements link in the left-hand pane.
    The announcement is added to the announcements area of the project. The announcement is also displayed on the user's start page.

HTML conventions for the Community tab

The CollabNet environment applies filters to some HTML files but not others. HTML files that are not subject to the cross-site scripting (XSS) filter can be passed to the browser from specific areas of the application.

Pages that you check directly into the version control repository are not filtered in this manner.  As a result, Community and Project home pages and content are not filtered.  The assumption is that users who have the rights to commit files to the repository are going to use XSS scripting tags appropriately.

See the help on HTML coding conventions for information on HTML coding conventions for areas of the application that use an XSS filter.