Browse Prior Art Database

Allow drag-and-drop of web content onto portal pages

IP.com Disclosure Number: IPCOM000177411D
Original Publication Date: 2008-Dec-12
Included in the Prior Art Database: 2008-Dec-12
Document File: 2 page(s) / 45K

Publishing Venue

IBM

Abstract

Allowing drag-and-drop of web content onto portal pages enhances the flexibility of content creation as well as usability for end-users.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 72% of the total text.

Page 1 of 2

Allow drag-and-drop of web content onto portal pages

Web Content Systems are typically the most important source of information to be displayed in end-user facing Portals. The figure below shows the architecture of IBM's WebSphere Portal Web Content Management System.

In current portal systems web content is integrated into portal pages via a web content rendering portlet. This portlet needs to be either configured or in the more advanced case takes up a context defined for the whole page. This means that it is always unnatural for business users or content authors to put new web content on a portal page as they need to select either for the portlet or the page a specific web content folder to render.

A solution for this is to display the web content folders in the portal palette and allow users to drag and drop web content from this palette to the portal page. The portal page then renders this web content in addition to its current content.

A key part of the described approach is to provide a new type of content for the portlet palette that accesses the WCM repository via a REST call and provides the WCM folder structure to the end user. Once an end-user selects such a folder and drags it on the page a WCM rendering portlet is created automatically and configured to point to the selected WCM folder. For the end user it seems like she/he can in...