3 ms·
I'm a long time user of Dokuwiki. I ran across wiki.js a while back and it showed potential. My main issues with it at the time were: * Had an overall half-bak
by bityard 6y ago
I'm a long time user of Dokuwiki. I ran across wiki.js a while back and it showed potential. My main issues with it at the time were:
* Had an overall half-bakedness about it. Like, there are features in the UI that sound cool but when you click on them it says "sorry, not implemented yet." ...Then why even have the button?
* Using it, the UI felt "heavy" and a bit sluggish in a way that I can't quite quantify.
* Having to set the page title and URL separately is weird. I think this is an artifact of designing it more like a document repository than a wiki. Because in a wiki, the URL _is_ the title of the page. I remember linking between pages being a little obnoxious somehow, but I don't remember the details.
* You can have WYSIWYG HTML pages or Markdown pages. You cannot switch a page between the two. Which is totally and completely crazy. Either design your WYSIWYG editor to handle Markdown so that you _can_ switch between them or settle on one or the other.
- oefrha 6y agoIt’s a big undertaking for a one man open source project, especially considering v2 is a rewrite. I believe all necessary functionality is already implemented in v2 so it makes sense to push it out of the door UI-wise and fill in additional features later. Conversion between Markdown and WYSIWYG is planned[1] although I couldn’t care less. It’s not like the Markdown editor doesn’t have buttons for non-technical users to push; they’ve been pushing buttons to generate BBCode just fine for two decades. [1] https://wiki.js.org/feedback/p/switching-from-an-editor-to-another-on-an-existing-page https://wiki.js.org/feedback/p/switching-from-an-editor-to-a...
- rhizome 6y ago>v2 is a rewrite I've got half a mind to make an "our incredible journey" blog with all of the software that has uttered these famous last words.