Give a high-level overview of the tutorial. This helps the reader understand the scope of what they'll be doing end-to-end and potentially the basic architecture of what will speak to/interact with what.
If relevant, include what they'll have achieved or built by the end of this tutorial.
This can include:
- Recommended hardware/software/local setup
- Familiarity/experience with Rust, JavaScript, at a certain level
- Completion of a prior tutorial or process
- Accounts or logins
- Anything else that is relevant
Info here.
Info here.
Advice on common questions or specific error messages that might pop up, or the support route if the user needs help.
Further tutorials or docs to read once someone has successfully completed your tutorial.
Remember to add the language when including any code blocks. While not supported natively by markdown, many markdown engines (including the one used by GitHub) will support syntax highlighting, which is helpful for reviewers and future maintainers of your tutorial:
```rust
let (contract_hash, contract_version) =
storage::add_contract_version(contract_package_hash,
entry_points,
named_keys);
```
If your tutorial is long and you feel it would be easier to follow if split over multiple pages, create a folder and individual files, like this Counter tutorial.