|
Size: 1156
Comment:
|
← Revision 5 as of 2009-09-20 23:46:25 ⇥
Size: 1162
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
| 1. [http://onehippo.org/ Hippo] 2. [http://code.google.com/p/brix-cms/ Brix] |
1. [[http://onehippo.org/|Hippo]] 2. [[http://code.google.com/p/brix-cms/|Brix]] |
| Line 27: | Line 27: |
| We could develop those administrative portlets at Apache. I would recommend putting the code in either the j2-admin project, or creating a new CMS project at [http://portals.apache.org/applications/ Apache Portals] | We could develop those administrative portlets at Apache. I would recommend putting the code in either the j2-admin project, or creating a new CMS project at [[http://portals.apache.org/applications/|Apache Portals]] |
Proposal: Content Management System (CMS)
An integrated CMS is planned for Jetspeed 2.2.1.
On this page the functionality and implementation of the solution is discussed.
Proposed areas of Jetspeed core development:
- Site and PSML persisted in JCR (Jackrabbit) Repository
- Navigation integration with repository: portal can navigate directly to bookmarked content
- Automatic publishing of content from repository, immediately accessible in portal
- Security synchronized with JCR security
I believe a true CMS is a large development effort. People can choose to integrate with Apache-licensed CMS projects. There are two project I know of:
Both of these CMS implementations are based on Wicket.
Regarding your proposal to create the following portlets:
- CMS View Portlet
- CMS Admin Portlet
- CMS Menu Portlet
We could develop those administrative portlets at Apache. I would recommend putting the code in either the j2-admin project, or creating a new CMS project at Apache Portals