Today it is 5 years since I first signed up for a Wikidot account. It is still one of the best things I have ever done.
I had previous experience of Sharepoint but wanted an easier platform for my team spread around Scotland which didn't require servers, developers or any cost and which was good for managing a project, developing documentation and communicating between project members. Little did I realise that 5 years on I would be a Wikidot Admin, provide first line support on the platform, have developed a business (currently part-time) based on developing Wikidot-based websites, or that I get withdrawal symptoms if I'm away from my Wikidot activity dashboard for more than a couple of hours.
But as with any platform, application or interest, there are things about Wikidot that I like and things that I think could be improved. I'd like to share a few of these with you. It is purely personal, others will have different likes and dislikes and different experiences with Wikidot.
First the things that I like about Wikidot. It is an easy platform to get started with. You can have a site up and running in a few minutes and there is no big learning curve for a basic site. Yes there are things to learn, particularly as you start to develop more complex sites, but that is half the fun! And you don't need to learn it all immediately. Most days I am still learning new things or new ways of doing things.
An aspect I really like about the platform is that it is very flexible: you can build everything from a standard wiki to a knowledgebase to a commercial website or intranet. You can make it as complex or as simple as you want without the platform dictating what the result must look like (as Sharepoint does).
The features that Wikidot provides out-of-the-box are superior to those of its competitors. Features like the ListPages module, live templates and dataforms are incredibly powerful. These and other features like selecting and sorting on dataform values are not available in heavyweight competitor products like Confluence, or if they are they are plugins that can cost a lot of money and often cannot be used together. We get these for free, ready to go, out-of-the-box with Wikidot. And they work together beautifully. There are many powerful features with Wikidot that you just don't find in other products.
Strangely another feature which I think is a good thing is the absence of a WYSIWYG editor. There has been a lot of talk about this on the forums over the years but Wikidot has, quite rightly in my opinion, kept to a wiki syntax. Other platforms like Confluence (which I use most days in a corporate environment) have moved away from this in favour of wysiwyg but it reduces the flexibility of the platform and also seems to reduce what you can do. So I am pleased that Wikidot has resisted the tempation to replace the powerful and flexible wiki syntax with wysiwyg.
The support forum and the community admins are one of Wikidot's great strengths. A user with a question or a problem can get an answer very quickly 24 hours a day. We have admins in the USA, UK, Belgium, Austria and Australia so most timezones are covered. The speed, friendliness and quality of the support is better than any other platform I have dealt with.
The Admins and gurus themselves are first class and are always willing to help with answering questions, providing code solutions and giving suggestions. It is a real team and one that I am proud to be part of. And the snippets and applications that they have developed, for example the recent Android app, have made Wikidot even more accessible and powerful.
But there are things that I would like to see and that could be improved with Wikidot.
I hate the fact that in common with other free platforms Wikidot is seen as an easy target for webspammers and SEO backlink merchants. It is too easy for an automated program to create an account and webspam site in a few seconds. Currently there are many hundreds of webspam sites created every day and we spend too many hours deleting them. I would like to see a robust captcha system or other security so that it is much harder to create these sites which devalue Wikidot's reputation.
The lack of communication with Wikidot users and admins is also a source of frustration. We really have no idea what Wikidot is working on or what the overall roadmap is. This is not just confined to ordinary users, we admins have no idea either and certainly get no better communication than anyone else.
This poor communication also extends to not giving us any idea what the progress is on wishes that are submitted on the feedback site. Wikidot users and admins don't just create wishes because they're bored, it is because there is a perceived need for a new feature. There might be a very good reason why a feature can't be worked on or implemented, but too often a wish is rejected with no reason given which is a) unhelpful and b) very demoralising for the person who has made it. More often though a wish just hangs in the air with no response at all from the developers. And if they do give a response, like accepting a wish, a user has no idea when this might be worked on, let alone delivered. As an example I have a wish that was accepted in June 2011 and there has not been a single bit of communication (or development it would appear) since then. That is not good enough. I would not get away with that in my current dayjob as Intranet/KM/Wiki Manager for a very big European company and Wikidot needs to improve its performance and communication in this area.
Wikidot is, without doubt, one of the best, most powerful wiki platforms currently available and it beats Confluence, Sharepoint, Wikimedia, Wetpaint and other platforms in most areas. It's not yet a platform which corporate IT departments like due to the fact that it is hosted and can't have Active Directory integration. If this could be achieved it would be a world-beater. But I would be happy to see more modest improvement: responses to wishes, more systematic development of features and definitely more communication from the development team.
I have really enjoyed the last 5 years with Wikidot and am proud that I have been able to contribute. I look forward to the next 5 years. As a flexible wiki, website, intranet, knowledgebase platform ….you name it… it is hard to find something that is better or more enjoyable to use.
Rob Elliott
Wikidot First-Line Support and Community Admin Team
Hi Rob!
Thanks for your work of writing these "reflections"! I can only fully acknowledge your statements!
Best regards
Helmut
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
Rob, thanks for your guest blog post! Congratulations on your 5th anniversary with us!
Thanks for making your review of Wikidot honest — running a project as large as Wikidot is not an easy thing but I believe we do our best to keep Wikidot a stable, reliable and future-proof wiki platform!
Michał Frąckowiak @ Wikidot Inc.
Visit my blog at michalf.me
Thanks for posting this, Rob. I couldn't agree with you more. The lack of communication has been really bothering me more and more lately. Wikidot needs a kick in the ass and I think you have just done that in a very diplomatic way.
Thanks for taking the time to write this and for everything else you do to keep our slowly dying community alive.
Community Admin
As for my case, i am still starting with wikidot, and i hope that somehow, i will learn a lot from this site and will benefit from the colloquiums here much as you have.
Kudos Wikidot!!!
Traffic Ticket Miami
Great post Rob,
I think the points you make, especially about no WYSIWYG are excellent. I have to use SharePoint at work, and the flaky formatting drives me insane. It is great to be able to type in a particular bit of syntax and get a consistent result.
My 5th anniversary comes up in October. I've been a bit slack at contributing to the community of late, but I'm speaking about wikis at a big conference at the end of May, and I hope I can convince a few people of the benefits of wikis in general and Wikidot in particular.
http://www.mav.asn.au/events/Pages/2013-lg-infrastructure-asset-management-conference-29052013.aspx
Wayne Eddy
Melbourne, Australia
LGAM Knowledge Base
Contact via Google+
Great post, Rob!
I worry that the lack of communication is dampening the growth of the community. I'm guessing 90% of Wikidot's active gurus joined in 2009 or before. Community engagement (such as Pieter provided) to show that the project is under active development and responsive to its users is, I think, essential to attracting super-fans who greatly enhance the experience of using Wikidot (especially if they are active on community.wikidot, answering questions; or building tools and businesses around it).
Personally, I haven't been pushing the platform to its limits and so don't feel much urgency about the wishes on feedback.wikidot, but it would be nice to see a roadmap and hear about new features every once in a while.
Also, kudos to Wikidot for letting Rob post his honest thoughts here.
:) I must confess I didn't ask, I just did it.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
It was great to hear your perspective Rob from 5 very active years on Wikidot. Most interesting!
Ye Olde - Creator and Chief Admin of www.music-industrapedia.com (Global Music Industry Directory & Encyclopedia) hosted on Wikidot.
I am not sure if this really happening… after the creation of important "documentation wikis" ( for my business partners) and some interesting and challenging creating of applikations - like the "Calendar", or my growing "genealogy template" - I have the feeling that we are all "living with wikidot as it is" - and have now reached the point where 95% works well and only some new little wishes are missed which would make our live easier (of course for us important :) ) .
I know the phrase "only some new little wishes" is not the reality now with the big numbers of waiting wishes, but I try to describe my feeling about the quote above.
The new applications built (like Amazones Storage Cloud or Kenneth's Mobile App ) were more the reaction of the changing environment in the world around us.
And my partners are till today a little bit "unwilling" to use our wikidot documentation wikis - but with less technical but more philosophical arguments like: why should I write my knowledge in a "Knowledge Base" only to make me unneccessary in my business dept?"
But that is another story.
I detect now that i started 6 years ago on 1. May… it is a long way together!
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
I understand this point.
However, having to explain a concept actually benefits the teacher just as much (if not more) than the student, as it reinforces that concept for them and ensures that they completely understand it.
Adding documentation for Wikidot to a collaborate Knowledge Base challenges the contributor to think about how to best explain the concept.
Of course, their name is also listed alongside the contribution (in the History), so they get the recognition as well.
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
Yes I hit this problem as well in my current Intranet/KM/Wiki position and so I spend a lot of time telling people that providing access for staff to knowledge across the company is a good thing for that member of staff as well as for all staff. It can show you are an expert and therefore someone to go to to answer follow-on questions. But keeping it private and "personal" is a very bad situation that helps no-one.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
WYSIWYG is a must today - especially if you look at Confluence you can see that it's possible to get it right.
The only reason I have not yet moved away from Wikidot is that all the alternative sites have some other issues.