Forum:Locking wiki to sysop only

We would like to know how to lock our wiki so only people with sysop can access it during construction as we learn and add more. Appreciate any help on this. Smeds 19:40, 6 August 2009 (UTC)


 * This currently is not a feasible request. Please see Help:Page protection and Help:Ownership. -- 19:58, 6 August 2009 (UTC)
 * It's usually best to learn about managing a wiki before requesting one. --Michaeldsuarez (Talk) (Deeds) 20:03, 6 August 2009 (UTC)
 * No it's not, many people learn best if they can have hands-on experience as they learn. -- ◄mendel► 22:23, 6 August 2009 (UTC)


 * I wouldn't describe it as "not a feasible request", I would more accurately describe as something that Smeds doesn't really need at this point. Smeds, if you simply create your wiki (you probably have already), you can learn quite a lot about wiki-editing and sysop access. I don't think you need to worry about people ruining work; in any case, that's quite an opportunity for you to learn more! :) And Mendel's quite right, hands-on experience is a good way to learn. Wjxhuang,  the 888th Avatar  {Talk} 22:39, 6 August 2009 (UTC)
 * It's not feasible because Wikia does not host this type of wiki, not because of what he needs. Smeds, this is something that would be simple to do if you hosted your own wiki, but that's usually not the best solution. ~Joey~  ^Talk^  23:31, 6 August 2009 (UTC)

Yes, but that doesn't really explain to him why Wikia will not do these type of requests. However, I'm quite sure Smeds has enough info to be going along with now. :) Wjxhuang,  the 888th Avatar  {Talk} 12:07, 7 August 2009 (UTC)
 * I was talking about how some users say "I'm going to start the greatest wiki ever, and it's going to owned by me!" But then they go, "Oh no, I don't what the hell I'm doing. I quit." Then they leave the new wiki to die; I see this sort of thing happen here all the time. These people try to start things that they can't handle. The best way to start a wiki is to develop a plan ahead of time with the support of a dedicated community. --Michaeldsuarez (Talk) (Deeds) 17:05, 7 August 2009 (UTC)
 * If they have a game plan, then they don't need to lock a wiki. Really, if you just want to test sysop rights, then Admin Tools is a good place to go. You don't start an entire wiki without any idea what you're doing. --Michaeldsuarez (Talk) (Deeds) 17:09, 7 August 2009 (UTC)


 * People don't quit primarily because of the code hurdles, but because of the work a wiki turns out to be; I also reckon most of them don't expect to be on their own.--AB 17:56, 7 August 2009 (UTC)


 * Anne is exactly right. They don't expect to have to do as much as they need to do. I rarely see founders, even founders of large wikis, stick around for a long time as an active admin. Maybe it's just a disagreement in philosophy, but I find that mucking around doing all this planning for a wiki a waste of time, because you're not giving your idea a chance to see daylight and get contributors if it's all stuck in your mind, if you know what I mean. Wjxhuang,  the 888th Avatar  {Talk} 23:31, 7 August 2009 (UTC)
 * Yeah, the as we learn definitely includes learning to build a community. ;) -- ◄mendel► 19:27, 8 August 2009 (UTC)