Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • WebSphere Portal Family wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 6.0
  • 6.1
  • 6.1.0.1
  • 6.1.5
  • 7.0
  • 7.0.0.2
  • 8.0
  • actions
  • administrator
  • authoring
  • Banking template
  • best practices
  • blogs
  • builder
  • building a site
  • caching
  • catalog
  • Clickstream Engine
  • clusters
  • ConfigEngine tasks
  • content
  • customizing
  • databases
  • demo
  • deployment
  • deployment scenario
  • developer
  • developing
  • device class
  • elements
  • examples
  • Express
  • feature set
  • fix pack 2
  • Government to Business template
  • info center
  • information center
  • installation
  • installing
  • LDAP
  • Learning
  • libraries
  • LikeMinds Recommendation Engines
  • logging
  • mentors
  • message catalog
  • messages
  • migration
  • mobile
  • mobile devices
  • mobile experience
  • mobile experience 8.0
  • mobile theme
  • mobile webkit
  • MPA
  • multiplatform
  • pages
  • performance
  • personalization
  • planning
  • portal
  • Portal 6.1
  • Portal 8 theme
  • portlets
  • product doc
  • product documentation
  • projects
  • properties
  • Redbooks
  • Redbooks Wiki
  • remember me cookie
  • resources
  • REST
  • Retail Vendor template
  • rules
  • samples
  • search
  • security
  • sifters
  • sites
  • solutions catalog
  • syndication
  • test infrastructure
  • theme
  • theme optimization
  • topologies
  • troubleshooting
  • tutorials on personalization
  • video
  • wcm
  • web content
  • webkit
  • WebSphere Portal
  • WebSphere Portlet Factory
  • wikis
  • workflows
  • worksheet
  • XML configuration interface
  • z/os
  • zos
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > IBM Redbooks: Building a Web site using Lotus Web Content Management 6.1 > 3.1.1 Separating content and presentation
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

3.1.1 Separating content and presentation 

expanded Abstract
collapsed Abstract
No abstract provided.
Table of contents Next Previous

Separating content and presentation


In Lotus Web Content Management, the creation of content is separated from the presentation of content. This concept is a very important concept and is implemented consistently. Thus, you can create content once and then display that content with different presentations. For example, the presentation can depend on:
  • The area of the Web site through which the user is navigating
  • The user's personalization settings (for example, preferred color)
  • Predefined presentation settings (for example, print layout)
  • The online device which accesses the content
This approach also guarantees that a Web site has a consistent look and feel. If the design changes, the content parts are unaffected. Additionally, content creators do not need to worry about the presentation of content, which can be beneficial when the content creators do not have specific HTML knowledge. Content can be displayed using different presentations.
For example, the River Bend Web site contains a Promotions list section and a Promotion section. All content documents in this section are displayed as a list showing only the titles and a link (see Figure 2).

Figure 2 Promotions list (31_2)

The link opens the document so that the user can read the entire text. In this case, the title, summary, and body are displayed (see Figure 3). These are two different presentations of the same content document and illustrate the separation of content and design.

Figure 3 Promotions document open for reading (31_3)

Content editing considerations


Content authors frequently demand a one-click option to edit a published content page. Additionally, they request an in-place-editing and WYSIWYG editing solution. Each of these requirements are based on the same desire -- the ability to edit text and content for a Web page while retaining the display format of the page as the edits are being made.

Challenge of editing separate content and presentation


Keep in mind that only some fields of a content document might be displayed on a Web site while others are not displayed. How does this impact the request for in-place WYSIWYG editing solution? Only the fields displayed on that particular Web page are available for in-place or WSIWYG editing. The other fields stay unchanged.
For example, if we apply this approach to the River Bend site, the following are true:
  • A page displays the title and summary. When an author edits these fields with an in-place or WSIWYG editor, only these fields are available for editing.
  • With the body field, no change is made unless the editor moves to a page where the contents of body field are also displayed. At this point, the editor has access to the body field. This approach requires editing the same content twice from two different access points.
You can imagine how this approach leads to inconsistency in content. Therefore, when content has to be changed, the ability to open the whole content document in an editor allows you to change fields consistently. In this way, you can achieve the separation of content and presentation.

In-place editing with the Customizable Template Portlet


Lotus Web Content Management follows strictly the concept of separation between content and presentation and provides functions to add an edit-link in a Web page to open the displayed document in the Authoring Portlet or the Customizable Template Portlet . See Figure 4 illustrates the edit link.

Figure 4 Edit link for one of the promotions in the Promotion page (31_4)

Clicking Edit opens the document in the Authoring Porlet, as shown in Figure 5


Figure 5 Document opened in the Authoring Portlet (31_5)

Future releases of Lotus Web Content Management are expected to provide enhanced editing functionality for this feature.

expanded Article information
collapsed Article information
Category:
IBM Redbooks: Building a Web site using Lotus Web Content Management 6.1
Tags:
wcm

This Version: Version 12 June 23, 2010 4:51:57 PM by Craig Lordan  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (3)
collapsed Versions (3)
Version Comparison     
Version Date Changed by               Summary of changes
This version (12) Jun 23, 2010 4:51:57 PM Craig Lordan  
11 Oct 21, 2009 4:51:06 PM Amanda J Bauman  
9 Oct 19, 2008 8:47:03 PM John Bergland  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use