The documentation we have right now is not bad, but it’s not really comprehensive.
It could be added some topics like certain workflows, i.e., setting up a new type, or how to organize different types to a knowledge system.
Also a list of known problems of missing functions on different operation systems which help a lot to find the reason for certain issues faster.
On the other hand, there’s a lot of people who use Anytype and have first-hand experience. They have problems, solve them and aggregate knowledge.
We have the forum, which is really good, but the information there is not easy to find, since it is chat-based and not only structured by topics but follows the flow of threads.
HOW COULD IT BE DONE?
Complementing the existing documentation by a Wiki on anytype.io that is written by the team and the community (sort of open access like Wikipedia).
Of course, the team would have the last word, what is really published, because of quality assurance reasons. But like that, I’m sure, we would get much more information organized and not just chats like in the forum.
You could also connect the wiki to the help system in anytype. So there could be an entrance for every function in the menu plus functions that are revealed by right-click mouse, etc.
And I’m sure that there are a lot of people who are happy to help to support anytype by building up the best possible documentation. It could be possible to have a documentation according to each main version. So everybody finds his way around.
So this could be help from the community for the community.
REAL WORLD USE CASES
There could be a table with all functions of anytype listed and every column shows different operating systems supported and if this function is functional in this OS at the moment or not.
We could have different workflows that show how to do stuff on desktop or mobile.
If you press on “Help” within the app, it could link to the respective wiki page.
RECOMMENDED ALTERNATIVES
ᅟ Don’t know which one.
Waiting for professional authors or developers to write the documentation could take too long.
ADDITIONAL CONTEXT
ᅟLike this there could be an even stronger bonding to the community and it could help to spread the word about Anytype.