Many sites have a page (usually prominent and easy to find) featuring a comparison table between their product and a that of a competitor, making the differences clear and encouraging a call-to-action.
The Bisq website could probably use something like this too, given how different Bisq is from other options, and how unclear those differences may be to a first-time visitor. It's a shame because the seemingly small differences make a gigantic practical difference in user privacy, security, freedom, etc.
The page should:
outline what these differences are—practically (i.e., sure Bisq software is locally-installed and peer-to-peer, but what benefits do these points actually provide to the user?).
do so graphically, or at least in some visual way (a nicely-formatted table should be sufficient) so that the page is not a big wall of text
perhaps include testimonials / user feedback about use cases or other benefits they get from using the software
This item can either be delivered as a finished pull request to the bisq-website repository or as a mockup (thorough plan including text, layout, etc) for someone else to implement in the website code.
If you're interested in taking this on, please post a little bit about how you would approach doing such a thing.
See the Growth Handbook for more ideas and approaches for growing Bisq.
Many sites have a page (usually prominent and easy to find) featuring a comparison table between their product and a that of a competitor, making the differences clear and encouraging a call-to-action.
The Bisq website could probably use something like this too, given how different Bisq is from other options, and how unclear those differences may be to a first-time visitor. It's a shame because the seemingly small differences make a gigantic practical difference in user privacy, security, freedom, etc.
The page should:
This item can either be delivered as a finished pull request to the bisq-website repository or as a mockup (thorough plan including text, layout, etc) for someone else to implement in the website code.
If you're interested in taking this on, please post a little bit about how you would approach doing such a thing.
See the Growth Handbook for more ideas and approaches for growing Bisq.