[META] repo ideas #2
Description
Foundations
- configure gitpod (feat: add initial gitpod file #1)
- reference on awesome-gno (feat: add gnolang/getting-started gnoverse/awesome-gno#43)
- share ownership between coreteam and devrels (chore: create CODEOWNERS #4)
- readme should explain the goals (workshop content, later=gno ide, can be useful for fork) (chore: improve README.md #3, chore: improve README.md #9)
- learn to run/test a contract with
gno(feat: 001-gno-cli #5) - Makefile with convenient commands (feat: use go.mod to manage gno dep #6)
- reference from gnolang/workshops repo (https://github.com/gnolang/workshops/tree/main/presentations/2023-07-23--workshop-nebular--manfred-morgan)
Suggested Curriculum V1
- 1. Explore the Gno CLI and learn how to write contracts without relying on the blockchain. (feat: 001-gno-cli #5)
- 2. Master the usage of gnokey for efficient account management and performing transactions. (feat: add 002-gnokey #12)
- 3. Gain proficiency in debugging and completing contracts. (Gno debugging section #14)
- 4. Publish your contracts on a devnet and various testnets for thorough testing. (feat: add 004-publishing-contracts #13)
- 5. Bonus: Create a microblog/forum/foobar application with multiple contracts.
Bonuses
- configure vscode (chore: setup vscode extension #10)
- setup CI/CD, especially for people who fork the repo
- reduce boilerplate to make the repo as clean as possible, especially the root dir
- replicate / set up sync if it makes sense with the main repo, I.e the gitpod.yml file, or the .gno files (to have single source of truth + CI)