Hi Ernst Peter,

When I fork the DNNCommunity/home repo the Wiki does not come with it... only the code section. Therefore, I cannot seem to use the versioning system for maintaining the Wiki. It appears the Wiki only supports direct edits, along with a history of changes. Should I make the changes to the /home Wiki that I mentioned?

If the Wiki does not support forking, would the Wiki still be the best tool for documentation on the FAQ module? It would be simple.

GitHub wiki's are not part of a fork of a repo, essentially a wiki is a repo in itself, so you can clone it locally but you cannot fork it and use the pull possibilities. That is a limitation of the wiki of GitHub. I can limit the access to the wiki, but have decided not to do so. There are some workarounds to have pull strategy with wiki's, but for now, just go ahead. If things get out of hand I can always limit the access to the wiki 

I think the standard way for images in the wiki is to add the images to the repository of the module itself. See this GitHub docu link. 

We could a folder within the repo to hold wiki docu images, e.g. wiki.images/*.*.  I have not seen a standard in other repo's.