-
Notifications
You must be signed in to change notification settings - Fork 399
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
Document gnoland, gnokey and gnodev commands #1987
Comments
FWIW, documentation should go on docs.gno.land, but there should be enough self-help also in the |
Hey, about this issue - right now we already have docs on all of the tools (Gno Tooling section), albeit:
What exactly do you think should be added? |
@thehowl just to be clear: your proposed improvement is enabling you to hit |
@leohhhn I updated the description to be more specific. Let me know if you need additional clarification. |
As discussed with @Kouteki, the action steps on this issue will be as follows:
And update missing/outdated things accordingly.
|
The task is not just to review the existing pages, but to generate completely new documentation on how these tools are used, and under which circumstances they are used. |
To clarify: Our objective in this issue is to build learning oriented, tutorial style documentation. This documentation is part of the Getting Started section.
|
I've split the issue into more manageable pieces, closing this one. |
As a Gno.land user ISBAT see all the available commands in the documentation and how I can utilize them so that I could accomplish my objective.
Acceptance criteria:
gnoland start
#1985 to understand the format needed for the documentation. Use it as a template for this taskgnoland
commandsgnoland
commands OR help Onbloc document them on their owngnokey
commandsgnodev
commandsThe text was updated successfully, but these errors were encountered: