Salesforce Sites

1. User Interface can be private (internal Salesforce users) or public. Public interfaces are provided to anonymous users using Sites - anyone could access a website built on Sites without having a Salesforce login.



2. If Sites is licensed, the functionality of Sites is available at Develop-->Sites.



3. A sites user has a unique domain name. One domain name can be used to support multiple websites. Example domain name could be - http://ap1.mydomain.salesforce.com/siteName . The domain name must be unique among all site users and can represent the organization's name.



4. Creation of sites requires specifying fields like Site label, Site Name, Site contact, Default web address, active site home page, inactive site home page.



5. Once an organization has registered a domain name with a domain name registrar, it can point the url to sites url.



6. Site template is a VisualForce page that defines the default look-and-feel of the sites page.



7. Force.com sites are
   1. Public, unauthenticated websites
   2. Accessed from branded domain names
   3. Build with VF pages
   4. From data and content in a Salesforce application



8. Creating a Force.com Site requires performing the following steps
   1. Build a Force.com App
   2. Design your web interface in visual force
   3. Create a Force.com site
   4. Activate the Force.com site



9. Key concepts about Force.com Sites security
   1. Security for your site is controlled through public Access Settings
   2. Access can also be restricted by specifying an IP range.