Hi Tobias I can not agree with you. Just imagine such example, i made some framework and pack it in jar. Some one makes his own area and what he shoud do to use it? My page do not "know" enytinhg about his areas. Another example, i have some pages that have areas inherited from parent pages. But on some level they must have differnt layout, or i msut allow access to only one component. It's not possible to make such pages with components. I must extend pages and change areas rules.
How you can make such structure with "components" approach: Page: home Navigation Area Content Area - here some components Footer Area Page: form Navigation Area (inherited) Content Area - Nested Form area or component restrictions Footer Area (inherited) Page: Two Column Navigation Area (inherited) Content Area - 1-column: Navigetion tree 2-column: Must extends by child Footer Area (inherited) Page: Tree Node Page Navigation Area (inherited) Content Area - 1-column: Navigetion tree (inherited) 2-column: Some data from tree Footer Area (inherited) -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=38881ed0-75ac-420e-9fca-0327a98786a5 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
