Each community has one associated Force.com site that lets you make advanced customizations to your community. For example, with Force.com
Sites you can:
- Add public pages to your community that don’t require login.
- Use branded self-registration and login pages to enable users to register for or log into your community.
- Customize out-of-the-box error pages to reflect the branding of your community, including “Authorization Required (401)” and “Page Not Found (404)” pages.
- Leverage Visualforce pages to create private pages that only community members can access.
For detailed information about using Force.com
Sites, refer to the online help.
Tips and Considerations
Sites pages automatically include the branding styles you specify in the Create Community wizard. To disable these styles, set the standardStylesheets attribute on the <apex:page> tag to false.
- Consider these limitations when using Force.com Sites with Communities:
- Out-of-the-box RSS feeds, analytics tracking, and custom portal profile pages aren’t available.
- Custom change-password pages aren’t available.
- Login to custom domains is only available with HTTPS.
- Because Force.com sites are served directly from the Force.com organization, a site’s availability is directly related to the organization's availability. During your organization's maintenance window for major releases, your sites will be unavailable; users who try to access a site will see a Force.com-branded maintenance page or your custom Service Not Available Page.
- You can redirect a community home page to its companion Site.com home page. To do this, set a URL Redirect on the Force.com site detail page. Set the Source URL to /, which represents the home page for the community, and set the Target URL to s, which represents the home page for the Site.com site.