Hi leiger,
Thanks for your answer! In the future I will take a look in these wish lists before posting something new here.
If I were building an exclusively private Wiki, all the present wikidot capabilities would be more than acceptable as they are. However, my problems started when I began to look for ways to hide code from potential collaborators. After all, Wikis are all about collaboration. And the easier this collaboration turns out to be, the more popular the Wiki will be.
So, let me try to explain better what I meant:
Editor Buttons for the wiki field
Ok, so it seems to be an old wish. At least from may 2010… I second the following observations made by scottplan here
Data forms have made our site so much more approachable, except that almost no-one uses wiki syntax. I think there are two reasons for that:
- No editor buttons available
- No preview available.
I foresee that my future collaborators will act in the same way… This will result in an ugly and unattractive unformatted Wiki. The only way around being me to go after every new page created by others and edit them thereafter.
These Editor Buttons would be a nice improvement, but better yet would be to integrate the preview capability and do not show wikidot syntax whatsoever. So if for example you selected a word and pressed the bold button, the word would automatically show in bold type, without those ** from syntax… I won´t cite names here, but I have tested other wiki farms that allow exactly that…
Other desirable capabilities for data forms would be conditional questions and nested fields…
And
Also, the way images are dealt with in data forms is a bit convoluted, to say the least…
The way I envisioned the use of conditional questions would be the data forms allow for a real-time change in the page being edited, depending of the answer entered for a specific question. For example, let´s say you have a structure with two fields, one wiki field for the main text, and other file field for uploading images. The question could be: How many images do you want to upload? And the answer would determine how many times a new edit data form, for the upload of a single image, would display. As far as I understand the present implementation does not allow this kind of flexibility. In the example, I don´t know previously how many images my collaborator will want to upload. So I have to setup an arbitrary number of file data fields and the ones not used will show up as error icons or a default image. Neither is very elegant…
Furthermore, the possibility of nested fields would allow for more complex "live templates" using data forms. For example, you could define a select field inside a wiki field.
Cheers