Intranet Process, Planning & Development

Written by Jeffrey Haas and excerpted from the book Practical Intranet Development

Personalization

Personalization cannot be introduced into a project's scope without some level of security (user authentication) either already in place or scheduled for development.

Once a security system is functioning and a user has been identified by it, matching categorized content with their corporate roles and responsibilities (or groupings) can be done by either

  • a general application server
  • a specialized one-to-one application server
  • a specific personalization engine.

The resulting personalized pages will also usually include some elements defined by the user as per their unique preferences. These elements will typically be limited to basic presentation-layer modifications such as color preferences and how content and functionality elements are organized.

See Chapter 10 for more information on Personalization.