== Requirements

Must have:

- Standardized format for storage in the backend like markdown or rst.
- A WYSIWYG editor

Nice to have:

- Using Git as the storage backend
- Online collaborative editor

Conclusions from testing:

- Finding a WYSIWYG solution often means it stores it as HTML, and not markdown.


**Otterwiki:**\\
Markdown with a Git backend. No simultaneous editing. Supports user registrations, which can require approval, or be disable altogether. Seems clean, usable and simple.

* https://github.com/redimp/otterwiki
* https://demo.otterwiki.com/

Written in Python using the Flash framework.

MIT license.

**Bookstack:**\\
WYSIWYG (HTML) or markdown, but you must choose one or the other and stick to it. Seems to store HTML if you use WYSIWYG.\\
No simultaneous editing - one user overwrites the other.\\
'looks nice'.\\
MIT license.\\

**DokuWiki:**\\
markdown.\\
No simultaneous editing - one user locks out another.\\
GPL2 license.\\

**MediaWiki:**\\
WYSIWYG editor stores a type of markup language underwater. Can switch back and forth.\\
No simultaneous editing - however, if has a fairly nice 'conflict resolve' solution built in, so nobody's changes are just 'lost'.\\
GPL2 license.\\

**Documize:**\\
Seems to have gone to the dark side (paid enterprise solution).\\
Free for up to 10 users only.\\

**!BlueSpice (mediawiki based):**\\
Paid solution.\\
Free version extremely limited.\\

**!AppFlowy**\\
Primarily note-taking software, includes ability to add kanban boards, calendars.\\
Extremely nice editor (type markdown, see WYSIWYG instantly on screen).\\
Collaborate editing is a no if you self-host, but on cloud-hosted it is possible. Since we want self-hosted this won't work for us.\\
Supports dark mode. omg.\\
AGPL3 license.\\

**Affine**\\
MIT license.\\