On 23.08.2006, at 00:15, Thomas wrote:
Why make it so complex? Why not have the basic unit being a Page, with all Pages having an optional parent, thus making a navigable hierarchy as deep as you want to go? Each Page has its own HTMLcontent, and Apache rewrite rules can be used to access them using URLs like
http://my.wonderful.site/site/newsletters/august/fun.html
other than not being fond of rewrite rules i agree. but it can be solved without rewrite rules just building some rest niceness into webobjects.
where "/site/" gets rewritten to /cgi-bin/WebObjects/MyCMS.woa/wa/showpage?path=
and "fun" has the parent "august" which has the parent "newsletters" which has no parent.
And since Pages are hierarchical, any intelligence applied to them (access by group membership, version control, etc) becomes hierarchical too.
If you are saying you want content to be accessed in multiple ways, that is a navigation issue rather than a membership issue. From my experience, your average CMS user would get very confused if you tried to tell them that a particular page "lived in" more than one part of their site. However they are very comfortable with the idea of "page aliases," which appear the same to site visitors, but the site admins see there is only one page.
i like the idea of making pagelets or pageitems, etc, that can be embedded in different ways in other pages. doesn't have to be restricted to simple layouts but can encompass functionality also. like a shopping cart component or wizard of some sort.
Or maybe I don't understand your schema. Perhaps you could explain it a little?
you caught it very well. i'm overdoing it i guess. send your schema in. i'm just trying to get the ball rolling ;-)
many greets
Cornelius