Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite /dao copy #2

Closed
cbeams opened this issue Jul 25, 2017 · 1 comment
Closed

Rewrite /dao copy #2

cbeams opened this issue Jul 25, 2017 · 1 comment
Assignees

Comments

@cbeams
Copy link
Member

cbeams commented Jul 25, 2017

The copy at https://bisq.io/dao should be updated to provide a better overview of what we're up to with the Bisq DAO. The overview and detailed Google Docs contain most of what folks need to know, but expecting them to click through and read those docs in their entirety (even the overview) is too much.

@cbeams cbeams self-assigned this Jul 25, 2017
@cbeams cbeams modified the milestones: 2017.30, 2017.31 Jul 26, 2017
@cbeams
Copy link
Member Author

cbeams commented Sep 7, 2017

Closing as superseded by the work being done in the bisq-network/docs repository. DAO papers will be moved there and links on the website will be updated. Existing copy on /dao page will be removed or overhauled then.

@cbeams cbeams closed this as completed Sep 7, 2017
cbeams added a commit that referenced this issue Sep 9, 2017
Problem #1: we were linking to outdated arbitration-system and
risk-assessment PDFs.

Solution #1: introduce /docs/exchange/arbitration-system and
/docs/exchange/risk-analysis redirects pointing to more up-to-date GDoc
versions

Problem #2: we were linking to newly transcribed exchange and dao docs with
full GitHub URLs, which are long and hard to read at a glance when
mousing over.

Solution #2: introduce /docs/exchange/whitepaper, /docs/dao/overview,
/docs/dao/specification redirects pointing to correct URL for these
docs in GitHub (and in GDocs for the latter).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant