On Sat, Oct 13, 2012 at 4:09 PM, Petko Yotov <[email protected]> wrote: > I feel that most visitors either search, or browse the Cookbook categories > to find what they need or might use.
When I initially voted for this PITS entry it was after I had done a couple searches for some topic and the results kept getting littered with Skins. So that might be the "problem" we're speaking of wrt the current setup. If I am pleased with my current skin but I'm trying to search for some non-skin recipe, how can I exclude skins from the search results? (Maybe some permutation of link=!Category.Skins which I couldn't find?) Of course if we change the naming convention then you can just ignore anything that ends with the prefix "*Skin". Using a (somewhat contrived) example I searched for this: CSS and then I searched for CSS name=!*Skin and ended up with a difference of over 50 skin results that I would theoretically have to process. (Yes, it's a bad example because "CSS" is way too broad of a search in any event. But this is the idea - making searches effective.) Since I'm aware of the capability of using name=!*Skin I would be able to take advantage of the potential new naming convention. (I would also have to get rid of *Skin-Talk and *Skin-Users which gets to be a bit of a hassle.) However I *think* that's not a normally used feature and so would probably be used by a relatively small number of administrators. So having the Skins moved into their own group would result in a more focused search. I don't know if I am typical or not as an administrator. I decide the skin up front, install and configure it, and then I never think about my skin again -- I focus exclusively on functionality after that. So after my initial skin configuration I would rather not have skins ever appear in my search results. I *think* that if someone is searching for a skin they aren't interested in other recipes and if they are searching for something not related to a skin then they won't want to see a skin -- in other words, the sets should be mutually exclusive from a searching perspective. In terms of the difficulty of figuring out what goes in the Skins group and what doesn't go in the Skins group ... I think if it is an actual skin (would be used in the $Skin = "Xyz" line in config.php) then it belongs in the Skins group and otherwise it stays in the Cookbook group, even if it is skin related. -Peter
_______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
