portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weaver, Scott" <Swea...@rippe.com>
Subject RE: [J2] RE: Page Aggregation Design
Date Mon, 01 Dec 2003 16:53:45 GMT
> -----Original Message-----
> From: Tim Reilly [mailto:tim.reilly@consultant.com]
> Sent: Thursday, November 27, 2003 8:08 PM
> To: Jetspeed Developers List
> Subject: [J2] RE: Page Aggregation Design
...

> > Im wondering if we should force any structure on pages.
> > I have modeled pages so that they are all contained in a big page
> > bucket.
> 
> The big page bucket sounds good. I wrote a CMS system a couple of years
> ago
> that is still in use, but in retrospect I wish I'd decoupled the content
> more like you mention - along these lines:
> - content in a big bucket
> - an administrative tree/heirarchy to manage what's in the bucket (the
> administrator's view to the contents of the bucket for organizing -
> content
> only allowed in one node of the tree.)
> - another tree/heirarchy that is the site map (same content can appear in
> multiple nodes of this tree)
> 
> I'm not suggesting for J2 or maybe? Just commenting on the low coupling is
> probably better.

I am also a +1 on using the BPB (Big Page Bucket) for decoupling content from the final hierarchy.
 Wow!  Look everybody we have a brand new acronym!

Regards,
*================================* 
| Scott T Weaver                 |
| <weaver@apache.org>            | 
| Apache Jetspeed Portal Project |
| Apache Pluto Portlet Container |
*================================*


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message