You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tooling / gno.land node / TM2 (need improvements to the GBE environment to support this)
Using different types of Gno.land messages (call, addpkg, run, etc)
Qeval, Qrender, query, etc
Possible CTF/wargame section, like Ethernaut (larger effort).
Any suggestions are welcome.
I see a possible issue with this - I think we need to define what type of content goes in GBE, what goes in the docs, and what goes on other content platforms (ie gno.me). I don't think we need to be suuuuper strict about it - there can be overlap, as long as there is a clear reason for it to exist.
gno-by-example should mainly contain short-form content, and should always point to the docs for further reading. That being said, some of the things mentioned above do not exist in the docs yet.
The text was updated successfully, but these errors were encountered:
Another possible direction we can take this in, which might be cooler than what I suggested above, is to split the tutorials based on the previous knowledge of the user:
Blockchain devs > introduce them to Gno, how to do blockchain things in Gno
Go devs > introduce them to blockchain concepts, how Gno differs from Go
This would be reflected in the UI/UX of the website as well - with two distinct learning paths for each user group.
Description
Here is proposal for GBE. Here are the new sections & their tutorials I would like to introduce:
init
functiongno.mod
(Maybe not suited too well for this environment, probably going to need some DevOps help for this)panic
for revertingAny suggestions are welcome.
I see a possible issue with this - I think we need to define what type of content goes in GBE, what goes in the docs, and what goes on other content platforms (ie gno.me). I don't think we need to be suuuuper strict about it - there can be overlap, as long as there is a clear reason for it to exist.
gno-by-example
should mainly contain short-form content, and should always point to the docs for further reading. That being said, some of the things mentioned above do not exist in the docs yet.The text was updated successfully, but these errors were encountered: