We have tried to use inheritance for this kind of thing before but ended up confusing users - they don't always know where the actual data is, and don't always realize that the change they make on a sub-page is only valid for its children, not the whole site.
Our typical solution looks like this: [@cms.area name="menulinks" content=gf.getOrCreateArea(homepage, 'menulinks') editable=isHomePage /] Where 'homepage' is a ContentMap of the level 1 page (our system is divided into sites at level 1), isHomePage is a boolean, gf is our custom templating functions library, and getOrCreateArea does what its name suggests. We also have an invisible node called "global-data" in our root for containing areas that are truly system-wide. As long as "global-data" is not a mgnl:page, it will be invisible in Pages. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=91ad009b-d9c3-4197-9918-ed9722b47167 ---------------------------------------------------------------- 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> ----------------------------------------------------------------
