About a year ago we did two things which were very important for anyone using Wikidot. First, we sat down and designed a new way of showing pages, which became the ListPages module and the dynamic template system.
If you've not used this module, you need to try, because it gives you something like the power of a database in your wiki. In fact, I wanted to rename ListPages to Select, and may still get my wish. "Select from=category where=tags orderby=something"… it just feels properly familiar.
ListPages and (the new, improved) templates changed the way we make dynamic Wikidot projects. Before that, we depended on forums, and the FrontForum module. But forums are not really integrated into Wikidot - you can't tag forum posts, you can't attach files, you can't use templates - and though we're used to using forums for online discussion, they fit uncomfortably into the Wikidot world.
One of my ongoing projects is to build a package that imitates forums but does it using plain Wikidot categories and pages. When I can reimplement forums, Wikidot starts to look like a tool for building certain types of web application. More than just a wiki, indeed. And we're looking at how to implement web forms (oh yes, this is going to be fun!), so that your users won't have to learn wiki syntax at all, just enter data into fields. I want Wikidot to be a tool that we can use to build a new kind of application that brings people together at the lowest possible cost.
As we sketched the outlines of ListPages and dynamic templating, we also looked at where we'd been spending our effort over the year before that. You may have noticed, if you're a long time Wikidot user, that the product stagnated while we planned and worked on Wikidot 2. Wikidot 2 was meant to be the ultimate Wiki engine, but it got stuck in "version 2" syndrome. What starts as a crystal clear vision turns into a "change everything" project that goes nowhere, and slowly.
So the same day we designed ListPages and templates, we did that second important thing, and killed Wikidot 2.
I don't like massive changes. Michal will confirm that my mantra is "make small, simple changes, and then improve over time". I really like the way Wikidot has been moving towards becoming an ultimate communication platform for online projects. The code is not perfect, but it works really well, it's fast, and it's stable. Michal and his team are among the best programmers on the planet. You can, if you doubt this, download the open source version and look at it.
The goals of Wikidot 2 were honourable but we were failing to improve the tools people used and depended on every day. When the current product has no more bugs, and no more obvious things to improve, and when we have a stable and profitable business that gives us enough margin, we'll start on a fresh Wikidot 2.0 design.
Good to hear the target has changed, freeing the resources again. I was never waiting for wikidot 2.
PS. nobody is angry, if someone builds an interface code which uses SQL - mimic languages for the ListPages module. Parallel of course…
PPS: I can rebuild my database: category than on the community - long time ago i was asked if with wikidot someone can build a little databasse application for small towns in the poor countries - I think , with the forms module ( hope it will come one day) this is a real chance for the people.
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 ?
For me, one goal with the Wikidot product is that we can make almost any kind of web project using a set of generic tools: wiki syntax, templates, lists, notifications, membership management, and eventually forms. If we look at web applications, most are actually built out of such pieces, but each time, developed in an ad-hoc manner. Generic tools are better: faster, more robust, and overall cheaper.
There's no reason that applications made with Wikidot need to be 'little': they can grow to huge numbers of users, and thousands of pages of content.
At the same time, Wikidot must be simpler to learn and use, and we're looking carefully at every step from making a comment on a page, to starting a new site, to make it simpler and more obvious. A more powerful product can also be easier to use, if we do our job right.
Portfolio
I could almost taste the web app building concept when I was putting together a test/planning site for a Wii Community last year (they ended up settling elsewhere, but promised to look at wikidot again when they outgrew that site).
There's a lot you can do with listpages and templates, but I lacked meaningful user grouping, event scheduling, more diverse permissions, and form-based interaction, among other things I couldn't quite put my finger on. That experiment was the source of a lot of my wishlist requests.
Wiki-based foruming also gets a thumbs up from me, so long as it comes with site-specific settings and increases power and customizations when it comes to avatars and signatures. Hopefully, you'll also move "signature" ability from a user-by-user setting to a site-by-site setting, b/c while an admin might pay to make sure his users can have the bells and whistles, a lot of ordinary users wouldn't want to pay for such a tiny thing, but they also wouldn't want to use a forum that didn't provide such a basic amenity. Combine wiki foruming with web apps, and wikidot could do for forums when they are doing for blogs.
I wish wikidot luck on this. There are a lot of useful social networking applications coming together—for instance there was a site for readers that launched recently that allowed you to build your online library, befriend readers of similar books and share recommendations. I bet you there were tons of readers who had a similar idea long before that site launched, but they didn't have the programming expertise to be able to build it. A web-app builder wikidot could become the go-to site for all manner of niche functionalities thought up by people who don't want to devote their lives to programming.
Exactly. And a good blog post pieterh!
Wikidot-based forums and form entry are two of the major things I'm hoping to see sometime soon for my own website. Along with practically everything David Marseilles mentioned in his own post! :)
One major feature area I'd like to see improved is better membership integration with the wiki:
As for your SQL-like wishes for the ListPages module, I agree with Helmuti_pdorf. Both the SQL style and the currently-used style have their merits, and I believe the best way to implment your idea is to have two similar modules - ListPages and Select. Select could be made more powerful in time, whilst ListPages is just there for backwards-compatibility and for those that prefer to use the current syntax.
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)