Hi Alexander, we have google and other excellent search engines. I don't think that the way we search our content should result in many mediawiki instances. This sounds to me like an attempt to solve a problem with a very wrong approach. Besides that, the issue of broken cross-wiki links outweighs this by a large factor.
Best regards Dominik On Thu, Aug 8, 2019 at 1:05 AM Alexander Potashev <aspotas...@gmail.com> wrote: > > On Tue, Apr 2, 2019 at 4:21 PM Juan Carlos Torres <juc...@kdemail.net> > wrote: > >> OPTION 1: Sunset TechBase, put everything in Community Wiki > >> > >> PROS: > >> - All-inclusive, all-welcoming place for any kind and any level of > developer > >> - Everything is one place, easier to search, easier to see duplicates, > no jumping back and forth > >> > >> CONS: > >> - Could make the Community Wiki crowded > >> - Lose search ranking, lose a catchy name > > Using one Wiki for everything has another little drawback: you can't > limit search to a subsection of the wiki. > > Let's say a user searches for "kblocks". If it was a search on > UserBase, it gives 0 results and that's it - there is no user > documentation for it on UserBase. However if it was a single Wiki for > everything, you would see about 20 results, all of them are technical, > and the user would need to go through all of them just to find that > none of those are relevant. > > On the other hand, I can't imagine a person who uses MediaWiki search > function in 2019, other than me. > > -- > Alexander Potashev >
