New sections & tutorials in GBE

[leohhhn]

Description

Here is proposal for GBE. Here are the new sections & their tutorials I would like to introduce:

• Basics
  • Primitives, variables, loops, conditionals, etc.
  • Hello world, Render
  • init function
  • gno.mod (Maybe not suited too well for this environment, probably going to need some DevOps help for this)
  • Importing/using stdlibs
  • Importing/using on-chain packages
  • Importing/using on-chain realms
• Chain-related
  • Using panic for reverting
  • Emitting events
  • Manipulating call stack (PrevRealm, OrigPkgAddr, OrigSend, etc)
  • Using banker, sending & receiving native coins
• 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.

[leohhhn]

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.

[zivkovicmilos]

gno-by-example should mainly contain short-form content, and should always point to the docs for further reading

💯