[Typo3-dev] Less features, more future

[Kraft Bernhard]

Kasper Skårhøj wrote:
> Thanks Ernesto,
> 
> I found it very interesting to read your suggestions. I think your basic ideas 
> are contained in the direction v5.0 will be heading. I will save your mail 
> for later reference.

My abadoned CMS "WebWiz" (devleoped till 2001, some sites still runnig) used the approach to
have "administrator defined" page types.

In my concept there where "ITEMS" (comparable to pages, but also to conent elements) and
"GROUPS" (which in reality also where ITEMS). Each Item must be assigned one group. As GROUPS
where made out of ITEMS (just Group-refernce field set to 0) and ITEMS had a hierarchial structure
also GROUPS were structured hierarchically.

So I could build up a Tree of GROUPS in the BE and defined by doing this how ITEMS (Pages) could
get nested. So I defined for example that a "Site-Root" Container (Page) could contain "Menu-Container" Pages
and those could contain "Simple Pages" and "News pages". "Simple Pages" could just contain "Simple Pages" again
and so you get the recursion which is required for putting Pages into Pages.


Maybe a similar concept where each "Page Type" (or flags of the Page) decides which subitems (table records)
a page can contain would improve T3. The default must of course be something to behave like today but with a
few modifications of some PHP Configuration Arrays it would be possible to ease the work of Editors by letting
them only insert CE's or tt_news records, etc. into pages on which they are valid.


greets,
Bernhard
-- 
Kraft Bernhard
MOKKA Medienagentur <http://www.mokka.at>
T: +43 - 1 - 895 33 33 - 50