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

Restructure aragonAPI section so that the relationships are more clear #102

Closed
sohkai opened this issue Mar 4, 2019 · 0 comments · Fixed by #127
Closed

Restructure aragonAPI section so that the relationships are more clear #102

sohkai opened this issue Mar 4, 2019 · 0 comments · Fixed by #127
Assignees
Labels
bug Something isn't working

Comments

@sohkai
Copy link
Contributor

sohkai commented Mar 4, 2019

See https://forum.aragon.org/t/on-aragon-naming/203/12:

Currently, when clicking on aragonAPI in the developer portal, one is redirected to the aragonJS root page. The first package mentioned is @aragon/client, all the while the repository is aragon.js.

We should create a different landing page for aragonAPI itself, that points to aragon.js and @aragon/app as being the JavaScript implementations of aragonAPI.

@sohkai sohkai added the bug Something isn't working label Mar 4, 2019
@0xGabi 0xGabi added this to To do in Aragon Mesh Team via automation Mar 25, 2019
@0xGabi 0xGabi moved this from To do to Sprint (2-week) in Aragon Mesh Team Mar 25, 2019
Aragon Mesh Team automation moved this from Sprint (2-week) to Done Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants