two extra points: *) think about bookmarkability/ nice URLs. *) try to make the user-facing side (so the result of what people did with the CMS/ anything that can be accessed without logging in) stateless if you can.
Eelco On 8/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > 1) It will use Jackrabbit to store CMS-related data > > 2) To create a page, the administrator starts by selecting a layout, and > > then select the appropriate panels to fill the layout. The configuration can > > be stored in an OODB like db40. The page are virtual, but the CMS will use > > reflection to create the page when the user accesses it. > > 3) The administrator can set any page as the default homepage. > > 4) Different panels that can be assigned by the administrator for each page, > > like > > a) Velocity Panel for writing blog-like contents; > > b) Menu Panel for user-built menus; > > c) User sign-in panel > > d) Events calendar panel that uses joda-time library etc > > 5) Administrator can set the user roles to each page for acess content > > 6) Integrating a workflow engine for publishing. > > Yeah, that sounds pretty good to me. Keep us informed! > > Eelco > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
