I need one function in a wiki platform that I haven't seen so far. When I write text, in its WYSIWYG editor, I need an ability to paste in an image (a screenshot that I just grabbed, let's say) and for it to automatically upload it and embed it into text. Does this support something like that?
It seems like they actually support it in Wiki.js however it requires you to first click "insert assets" and once that modal displays [0], you can actually paste into the page and it will be uploaded.
Not too different than JIRA really. But I feel like this feature would be improved if pasting into the editor itself yielded the same result.
"You can upload images from a tab in the media dialog, or by dragging and dropping a file into the editor, or by pasting an image from your clipboard. [...] The image will be inserted into the page when you are done."
Now, it is fair to complain that VisualEditor is difficult to get running on your own local Mediawiki instance, as it requires the suite of local node.js microservers (RestBase and Parsoid) that aren't part of the core PHP platform.
That said, this is about to change! The upcoming Mediawiki 1.35 is supposed to move Parsoid into core PHP, and so VisualEditor is going to become a lot more default-accessible. :D
I have been waiting for an online wiki with the usability of Apple Notes that I use locally on all my Apple devices. It works like a charm except that I cannot make it public.
This is why I often take notes rather than write blog posts on my website. If the wiki software was as easy drag and drop as Apple Notes, I’d just take notes and they turn into publicly available wikis!
I am yet to find that tool. I would happily pay for such a tool with one braking condition that it must be self-hostable. I will not write my content into something like Medium or Notion where I don’t own my content.
This is technically feasible. The latest html5 api (quite well adopted) allow copy paste from the OS and drag and drop. There is quite a bit of server side / javascript to implement, but it is feasible.
- ui: joplin.
- agpl, fully self-hostable.
- you own your content (because joplin).
- choose among free templates, or create your own.
- templates will be similar or compatible to hugo, still tbd.
Optional for paying customers:
- sync via webdav to my service.
- custom domain.
- backups, etc.
Once this starts generating money, I am planning to spend some of it to fund e2e per-folder encryption in joplin.
I've deployed this for the internal documentation inside a company I worked for (MediaWiki was a no-go even with a visual editor).
For each new feature, I was developing inside a clean new wiki, than I exported the changes once I was sure everything was okay. It is way more easy then to upgrade to the new XWiki version.
Note that Outline's definition of "open source" diverges quite a bit from the one that most people have in mind when they hear the words "open source".
From the text of Outline's license [1]:
Notice
The Business Source License (this document, or the “License”) is not an Open
Source license. However, the Licensed Work will eventually be made available
under an Open Source License, as stated in this License.
I think it is more accurate to say that Outline will be open source, rather than Outline is Open Source.
Since you can write arbitrary JS in extensions, no reason why that couldn't be implemented by a library.
Since I just got into MediaWiki and write my first extension (finally a dark-mode that works), I'll see if this can be implemented. Perhaps with https://www.mediawiki.org/wiki/API:Upload.
