> So first I have to know that I should not search through the search box > I see, but to go on a certain page to search? Sorry, but this exactly > what I mean by "not user friendly".
It's an imperfect solution for an imperfect setup. We added the search box on the Documentation part of the Wiki to try and help a bit with the searching. > Are you really expecting an average user to perform that kind of > sophisticated Google search? I'm just presenting it as a possible alternative. Yes it is an advanced use of Google, and I agree, not many people have discovered that you can do this with Google (or would want to). >> Project leads are already using subpages to sort and group pages >> related to their projects as are contributors to virtually all >> projects. > > I did not talk about project community members, only about end users. My point with this was that Projects are attempting to do what they can to help chunk up what is there on the Wiki, by using subpages and Categories. > for me as end user, the mixed contents is contraproductive. I don't > know if there is an ideal solution, I just wanted to bring in a user's > needs. And if you don't want to hear what I'm trying to say, then let's > stop discussion here. I think you misunderstood what I was saying - comments such as yours are very valuable... if no one speaks up, nothing will change. I agree that what we have right now it not the best solution. I am doing what I can to improve the Wiki as it is with updating the engine, adding Extensions that are requested etc., assinign various project leads as SysOps on teh Wiki, but this does not address the fundamental underlying issues of usability. This is also one of the reasons I raised the original email in this thread.. new developers/project members and users are finding the Wiki harder and harder to use as time goes on. Will changing the search in the Wiki help? (this is something we can do in the current structure) We can change the default Wiki search into a general Google search of the Wiki (but not narrow it to a specific project - there are limitations to the search extension). The tradeoff on this is we loose one of other features that has been requested to be added back in (the Go button). If we need to break things out into different namespaces (one Wiki engine, but a clear split between developer and user info) that can be looked at. If we split into a developer and a user Namespace, there there are two unique place that people will need to search for info (was a reason Namespaces was not implemented in the first place). I think that we should be able to set up redirects across Namespaces so old page names lead people to the new location, but I'd have to research that (unless someone here knows more about this). As we have both said.. the solution to the problem is not clear. I hope others here can chip in with their thoughts and ideas. C. -- Clayton Cornell [email protected] StarOffice - Sun Microsystems, Inc. - Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
