Implicit personalization - Content that is implicitly personalized to a user based on pre-defined variables. For example content shown to a paid subscriber to a website may be different from the one shown to an unpaid subscriber. In an intranet your own emails are implicitly personalized based on your credentials. There are many aspects of implicit personalization including behavior based personalization to personalization capabilities based on common wisdom of the crowd. Explicit personalization - ability for an end-user to personalize the content based on the privileges assigned to the user. For example capability of iGoogle or netvibes where you can explicitly drag and place content within a webpage, change color and font settings etc. Roles based personalization - this is especially relevant in intranets and extranets where users get to access content based on their role in an organization. For example a users belonging to a Financial Role may be see content that is not visible to Sales and Marketing. Rules based personalization - This is personalization of content based on explicit rules that may be based on several content attributes and user attributes. For example users in San-Francisco may see local news from their region and users in New York my access the same site but would be seeing content that is local to New York. There are several ways of accomplishing this capability such as profile based personalization to automatic geographic detection thorough a user's ip address.
5. Globalization, Internationalization (I18N) and Localization (L10N) - This is the ability of the content management system to support multiple international languages and their local formats. The system must be able to support "left to right" (example English) and "right to left" (example Arabic) content editing and rendering capabilities.
6. Collaborative Content Management - allow geographically dispersed users to collectively participate in the content management process.
7. Content Baking – Is usually associated with delivery of static content pages. In this case, the Content Management Application creates the page at the pre-publishing stage and serves them up through a WebServer. Thus every user is served the same static page. Traditionally baking was considered to be good for high performance sites, but with cost of resources going down this may not be the case now. Also this is useful if entire sites have to be archived and versioned for compliance reasons. Some sort of pseudo dynamism could be made possible in Baked Content using intelligent Templating and JavaScript capabilities such as through the “dojo toolkit”. Also Content Caching strategies for Baked Content can be usually straightforward, without the need for dynamic dependency management.
8. Content Frying - This is equivalent to serving up dynamic pages. Multiple variations of the same content item may be served up by dynamically assembling content at run-time. This strategy is used for personalization of content such that users get to see something that is personalized for them. Many of the high end content management systems provide this capability.