...
External integration could assume that the web-CMS supports CMIS (or proprietary similar) protocol able to browse sitemap or content repository.
Re-usable Portlet Publishing Type
To expedite the publishing of content within the portal itself, it might be helpful to include a content authoring portlet type in uPortal meeting the following use cases:
1. A sufficiently-permissioned administrator would like to create a new portlet configuration with brand new content.
2. An administrator would like to create a new portlet configuration pointing to an already-existing content item in the configured CMS.
3. An administrator would like to edit an already-existing content item in the CMS through the portlet publishing type's configuration interface, either as a new portlet or by editing an existing portlet registration.
...
The new Jasig Simple Content Portlet might provide a useful starting point for such a publishing type. This portlet allows administrative users to display HTML content to end users via a WYSIWYG interface. While HTML content is currently persisted via the portlet preferences, an alternate persistence service could be created to persist data to a CMS via CMIS. This enhanced portlet would need to offer administrative users the ability to select existing content items, as well as potentially fork/duplicate items as they are edited.
Such a portlet should enable institutions to configure uPortal to use an external third-party CMS, provided that the CMS supports the CMIS standard. uPortal might also consider embedding a JCR store such as JackRabbit within the portal and exposing a CMIS interface via the JCR-CMIS connector project. This strategy would enable institutions to use the CMS portlet without needing to adopt and install a third-party CMS server.
CMS Administration Portlet
The publishing type described above would allow administrators to easily create portal content and to administer content for already-configured portlets. It would not allow administrators to easily edit CMS documents that were not associated with a portlet or allow institutions to manage non-portal CMS content through the portal. For example, some institutions have expressed a desire to use the portal to administer CMS content that might later be displayed in some other, more static institution website.
To meet the above use cases, and to generally provide more powerful CMS interactions, it would be desirable to offer a CMS Administration Portlet. Such a portlet might provide the following features:
- List and view existing CMS content
- Edit, delete, and otherwise administer existing content
- Create new content not to be immediately associated with a portlet registration
(still need to integrate this content)
A Contributer/administrator would add content in uPortal then select a Portlet dedicated to CMS content.
...