Knowledge Base
We have two projects regarding user support, this public support and the private helpdesk. Irritatingly we once thought to put public conversation on Discourse. This project here may just hold more features, like an attached repository, these issues and a wiki?
Similarily, for building a knowledge base we would want to write wiki style as much as possible out in the public, hence sometimes also internal documentation seems advisable.
Now I feel devided between extensively building on GitLab to attach workflows here, and the mediocre writing experience it brings: It's markdown parser is very poor and the wiki utilises crude syntax.
For @gandhiano it is crucial to have copies locally available via git. Then a differrentiation is going to be made between markdown kept in the wiki, and markdown kept in the repository. It is confusing to think all these text locations as dispersed and disconnected.
In remixing paragraphs between https://lab.allmende.io/ispcoop/administration/wikis/home and https://lab.allmende.io/ispcoop/infrastructure/wikis/home I felt hindered by GitLab's editing interfaces and wished to have a Federated Wiki available.
Where and how is the knowledge base of the @support going to be built?