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

[Ken McCall]

@Bayernatoor @cbeams @m52go 

I think/hope this is appropriate here. If not please advise me otherwise.

To start from a bit bigger picture, information (almost any technical information) falls into three broad types, a 1) concept, 2) reference,  or 3) procedure, and some may consider troubleshooting another type. This is the fundamental guide to the structure of use cases.

Documents get confusing when these types of information are intermingled. The "Getting Started with Bisq" section is an example of mixing these types of information - with the addition of troubleshooting information, marketing info, notes, warnings, background information and more. 

I understand what's trying to be accomplished, and it's a great work! Obviously the author(s) put a lot of thought and work into it and should be commended. But, it can be improved. It's a complex process with several procedures, and a background in many of the areas is necessary to complete a transaction.

Granted, this section is attempting to be a tutorial, and tutorials will in fact have instructional material in them, but the instructional and background information needs to be minimal. In short,  this section needs to be a bit more structured and the information types segregated. A conceptual introduction, with an overview of the process followed by a succinct, non-verbose procedure.

It may, at some point, become individual use cases, but I wouldn't try to accomplish that initially. We just want to create a guide to get a user successfully through a transaction. AND THEN through other non Zelle methods. 


-- 
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-599356974
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200315/6dfd180e/attachment.html>