Good & Bad Use Cases for Sites
Good & Bad Use Cases for Sites

Good & Bad Use Cases for Sites

11/11/2010 by Jason M. Atwood (he/him)
Taking a look at different uses for Sites and some of the decisions as to whether to use the feature or not.

Almost two years ago released a new piece to their cloud computing platform, Sites. This new functionality allows for Salesforce customers to build externally facing websites on the platform using VisualForce for the design and APEX for the logic. The unique thing about Sites is that it allows customers to expose parts of their instance. Both data and logic can be exposed as part of the website and then distributed over the content delivery network (CDN).

The question is, what is the right use case to use sites? These are just some of the good and bad uses cases.

Good Uses

Small Landings: One of the first and most common uses is small landing pages for marketing campaigns. These can be easily connected to a web-to-lead form and Google Adwords tracking. This allows companies to measure the success of their online campaigns without dual entry of data.

Low Function: Sites are great for low functioning websites, meaning mostly serving up templated content and tracking that use. Things like images and documents benefit from the content delivery network built in and is something that most small to medium website never get to take advantage of.

Salesforce Connected: There is no better way to expose the data housed in a Salesforce instance to the web then through Sites. With some small bits of code, objects and fields that are tracked in Salesforce can be built into content rich pages and seen by anonymous visitors. It is also a good choice if you are extending the portal.

Out of the Box: Using products such as Ideas and Knowledge or exposing data to social networks is a great use case for Sites. The Dell Ideastorm and Starbucks My Ideas are great examples.

Bad Uses

Highly Complex: Websites that range from hundreds to thousands of pages with highly dynamic features are not really well suited for Sites. While the platform allows for tools such as Eclipse, it is bound by functions of Visualforce and APEX and the hosting parameters of such as the complexities in sourcing certain types of data. This could limit both development resources and complex functionality that could be had in other systems and languages.

Content Management: While content can be surfaced through Sites from Salesforce and can inherit workflow and approval processes, it would require a lot of development work to do so. For websites that are creating boat loads of content with a variety of different users, a traditional (if not Open Source) CMS would be a better bet.

Community Based Widgets: The creation of websites with high functionality including such features such as polls, social networking, forums and chat is still best left to the mature market of website creation software where adding in that type of functionality is just a click away.


Overall Sites offer a great new way to publish anything from landing pages to full websites and the product continues to grow as the platform evolves. Also keep an eye on the AppExchange as partners develop new Sites products to catch up to the rest of the website market.