I just took a look to it and I would recommend you to stay away from it: wicked is a very old project (more than 10 years old) and it could be more complicated to fix it than to write a complete new version Dexterity only, and Plone 5 compatible.
follow @tkimnguyen advice and try to find funding for that before; I think this could take around 40-80 hours of work for sure.
look for developers outside US and Europe if your budget is limited.
other than a markdown editor, the only other think a wiki does is the method to create a page via unknown link... but is that really the best way? It has problems with CSRF protection due to it's write on click approach.
@vangheem I like the idea of an add form on broken links, but instead of the transform for wiiki links we can just support markdown and a generic feature which gave more options for broken links. ie drop the Wiki link transform... does any modern wiki support the wiki link convention of ThisIsALink?
For example, if the editor types [mylink] or [mylink](mydoc) and saves it and clicks on that link they get a link to a plone 404 page. Instead of saying the normal plone 404 page, if the user is logged in with enough permission we replace it with a 'do you want to add a page called "mydoc"? or add a redirect to another page?'.
That means there is no need for a special wiki link syntax or a special behaviour in a folder that needs to be turned on like wicked did. Instead its a UI enhancement for all users of Plone.
No, please! The main Wiki feature is who did what at which hour, with a complete history. Simple text editor (no html!) and a clear way to see who did the modification, where and when.
I'm assuming this is different from text/x-web-markdown right?
Reading the Wikipedia entry, would "Markdown Extra" be closer to wiki style text markdown than the current default included list?
Is there a reason it is disable? Security? Stability? Other?
I see that I do have the file markdown_to_html.py in my /opt/plone/buildout-cache/eggs/Products.PortalTransforms-2.2.1-py2.7.egg/Products/PortalTransforms/transforms
Frankly, I dont know much about 'wiki', but seeing what markdown extra has (which can easily be enabled in Plone), it would fit every need I 'ever need' if it was possible to enable 'add link' (which should be possible by making a a browser view to add new content.
yes, as soon as your content grows or you add different levels you'll start seeing more issues.
a Wiki is a completely different beast and, in Plone, neither ID nor titles are unique; you have to use the whole path or the UUID, but that's not user-friendly.
so, collective.simplewiki could work fine in small, flat sites, and could not scale very well; only time and use will tell.
anyway, is so simple that making it better will be easy.
The basic wiki in Pone 4.3, works just fine by Title [[Title Name Here]] to find it. Is there something in 5 that makes this more difficult? Or did the older wiki software have a lot more coded to make it more user friendly?
We've had to reevaluate using 5.5 just isn't there yet, and the integration of so many best of breed products isn't workable. So we're trying to work it from the 4.3 base, with far more options in one platform. But, hopefully the efforts started with SimpleWiki for 5, will be built upon and improved, so that when 5 is ready as a migration path from 4, the remaining wiki features will be worked out by then.
Many thanks & cheers!