--- "Patrick R. Michaud" <[EMAIL PROTECTED]> wrote: > Option 1: A page that acts as a "fallback > GroupHeader" when > a group doesn't have one. In this scenario, when > viewing a page, > we first look for a page named GroupHeader in the > current group, > if that exists we use it, otherwise we use the > "fallback" page > if it exists.
.... > ----- > > Option 2: A page that is automatically added to the > beginning > of every page's markup, regardless of any > group-specific GroupHeader > page -- i.e., a "site-wide header". Despite any preferences for naming, option 2 can always be used to create option 1, but option 1 cannot achieve option 2. This to me makes option 2 more valuable and a tremendous time saver. Option 1 seems more like a valuable customization easily implemented with conditionals in the Site.Header page of option 2. In fact, this approach would seem to me to be the more correct approach to site building, it could even eliminate some of the group specific ideas as core implementations in PmWiki and make them more of something built upon the larger more powerful building blocks of the engine. I would almost advocate changing the way the Sidebars work to be similar so that more (or all) of the group specific behavior was implemented as a simple defaults in the delivered Site.* files. Don't get me wrong, I like groups, but it often seems that they need customization (look at all the special site organizational recipes), why not just make them customizations in the first place? I realize that this is BIG change with many potential bad consequences, maybe something for another beta series? ;) -Martin ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/ _______________________________________________ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users