New wiki - should I use 1.0 or 2.0 for public release this August?
Also, I don't want to convert it in the middle of a semester (unless there's some kind of security/serious problem).
Thanks,
Kelly B.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hi Kelly - there's one big question that will help you determine what option is best. Do all of your users have email addresses?
-
Inappropriate?Rachel, some do and some don't. I anticipate that most people who will do updating will have email. But if they sign up as updaters, it's very important that they do not receive any marketing from Pbwiki as a company. They need to be signing up with our wiki, not our host wiki company. Does that make sense?
So, I guess that's a long way of saying, we don't have to use the "invite key" method of allowing updates, but I'm not sure about making people register if it means more unwanted email. -
Inappropriate?Hi Kelly,
Your users will not get any marketing from PBwiki - and they can opt-out of notifications of wiki changes as well.
Just keep in mind that if any of your users don't have email addresses they won't be able to view a private wiki, but they will be able to access a public wiki just fine. -
Inappropriate?Thanks for your answer Rachel.
What about using the widgets used by pbwiki 1.0? For example, I want to hide the footer, move the sidewar and might want to use some javascript here and there. Is this possible in 2.0? Also, is 2.0 "production" code yet or is it still being beta tested? If it's not production, what is the expected release date?
Thanks -
Inappropriate?Hi Kelly,
2.0 is out of beta mode, however there are some features not available (For example, we have javascript currently disabled). The widgets in 1.0 may not work in 2.0 because the design is different, but some of our hacker users still have widgets available. -
Inappropriate?And how long will 1.0 be supported?
-
Inappropriate?We don't have any plans to stop allowing users to create 1.0 wikis now or in the near future, however we are not continuing to develop it.
Loading Profile...




EMPLOYEE