Re: WebObjects Foundation
Re: WebObjects Foundation
- Subject: Re: WebObjects Foundation
- From: Thomas <email@hidden>
- Date: Wed, 23 Aug 2006 08:15:38 +1000
Just my 2c worth.
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
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.
Or maybe I don't understand your schema. Perhaps you could explain it
a little?
Regards
Thomas
On 23/08/2006, at 7:51, Cornelius Jaeger wrote:
Hi All
opensource wo cms.
so whose gonna send in the first schema?
heck here goes:
ContentFolder (Hierarchical) <-->> ContentFolder2Content <<->
Content <->> ContentItems <->> ContentItems2Assets <<-> Asset <->
AssetData
AssetFolder (Hierarchical) <->> AssetFolder2Asset <<-> Asset <->
AssetData
basic Asset Management and Content Management. No Privs or user
rights.
l8r
cornelius
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden