<br><div class="gmail_quote">On Wed, Jan 21, 2009 at 2:29 AM, Petko Yotov <span dir="ltr"><<a href="mailto:5ko@5ko.fr">5ko@5ko.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
> Right now, the appropriate category to use is probably [[!recipe]]<br>
> or [[!skin]] for skin documentation.<br>
<br>
I prefer [[!PmWiki Recipe]] and/or [[!PmWiki Skin]]. Wikis could be used for<br>
other things like food recipes, or software packages and skins, we shouldn't<br>
occupy categories that might have other uses by the websites.<br>
<br>
<br>
> Does this seem like a reasonable approach? If so, I can add it to<br>
> the module guidelines page. And I suggest somewhere in the PmWiki<br>
> documentation (i.e. in wikilib.d/) there could be a page that lists<br>
> pages in the [[!recipe]] category, so readers can discover what's<br>
> installed above and beyond the standard pmwiki distribution.<br>
<br>
Excellent idea, but let's first hear what others think. OTOH, if you are the<br>
author of the only recipe that ships with documentation, you can probably do<br>
what you feel is correct and common sense. :-)<br>
<br>
Thanks for pushing for improvements of PmWiki !!<br>
<br></blockquote></div><br>It seems like using the CategoryGroup steps on the integrity of the wiki a bit, doesn't it? I mean, this presumes that *most* end users should be able to see what recipes and skins are installed on a wiki, which, even given authorization, still pollutes an otherwise untainted space.<br>
<br>As it is, there is already a confused mush in the SiteGroup and SiteAdminGroup. SiteAdmin/ has very little of importance in it, while Site/ has a mush of things that don't really go together. When would the SideBar, PageActions, and the popular SiteHeader/SiteFooter pages sit right with Preferences, PageNotFound, Search, etc?<br>
<br>I don't know if any of you see the ambivalence of pages that end users would or SHOULD EDIT with pages that end users should be BLIND to.<br><br>Now, if I could make a strong suggestion as to future organization, I might think it wise to put all of the set-and-forget stuff -- the pages that by default should be password protected -- to the SiteAdmin group... which includes .Recipes and .Skins ...and use the Site group only for those pages which by default should be editable... aka, low-level building blocks of the site. After all, we can easily envision countless sites that would allow for SideBar editing, and only see situations in which the EditForm or Recipes pages should be hidden.<br>
<br>To consider allowing administration to bleed into the category group... that's madness... <br>Or maybe this is like all those twilight zone episodes, and we're all supposed to have pig faces! ;)<br><br>Mike<br>