[bisq-network/support] Decide on scope and style of use case articles (#352)

[Bayer]

Hey @kemccall 

I've been mostly trying to migrate any information from https://docs.bisq.network/index.html to the wiki. However, the docs tend to be very detailed and the sections contain a wide range of information, from basic BISQ concepts to use cases and more. 

Therefore, what @cbeams has been trying to do is implement a complete different approach to the wiki and i think you seem to be on the same page in regards to format as him. Short, succinct articles which can then be referenced and linked to. Do away with the flare and just provide accurate information. I hope I am correct in my assumption, otherwise please let me know.

Here are a few examples of pages  that I've created. in my mind #1 is probably the closest to what were going for. #2's intro may too long and may include too many details and #3 was just a quick explanation of how trading fees work in Bisq. 2 and 3 were essentially copied over from the original bisq docs. 

1. https://bisq.wiki/Delete_and_resync_SPV_file
2. https://bisq.wiki/Payment_methods
3. https://bisq.wiki/Trading_fees

What are your thoughts on this. Bisq seems to have very specific steps to get from install to purchasing Bitcoin. Therefore, i am concerned that creating guides with too little detail may leave the user looking for answers. However, i am new to this whole wiki business and am here to learn. Personally i prefer articles that are to the point and concise.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/support/issues/352#issuecomment-602094442
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200321/162ece31/attachment.html>