[jboss-dev-forums] [Design of JBoss Portal] - Re: WANTED: Input from administrators & developers

[dhartford]

anonymous wrote : 2) CMS control - it would be cool if you could deploy a single (or clustered) CMS "server" and deploy content links as required to all instances of portal via ON. this might be a bit bloated, not sure of implications and whether portal could fully handle it. 

Seperating out the CMS "server"/repo would definately help, not only for jboss portal but also as a seperate file-repository to develop against (aka WebDAV/JCR repo for other than just portal-CMS).

It would be great to deploy a 'Jboss Repo' that stores the CMS content and have the jboss-portal upgrades be seperated/less dependent of the repo. Could also setup CMS-bundles that are added to the repo and point to them from jboss-portal.

As another item, would be nice to have seperate administration/backup functionality that is domain-knowledge-specific to the repository versus the portal (i.e. portal admins deal with portal stuff, storage admins deal with storage stuff).

my two coppers,
-D

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972715#3972715

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972715