Nethereum documentation
- One pull request per document at a time, this way they can be reviewed and edited for corrections.
- Any code sample, interaction, should be created as a workbook.
- Any general introduction and when workbooks do not make any sense obviously NOT, for example Azure BaaS interaction, Code generation, Service structure, Getting started with Unity3d, BUT ideally the aim is to have everything in Worbooks and unit tested.
- Any modificactions should be pushed on the Nethereum.Workbooks repository
- Any new workbooks need to have a unit test associated with it, or changes unit tested before hand. For an introduction on unit testing workbooks Check this blog post
- All the workbooks need to be in the same folder and indexed in the index.md file. See previous entry on how to format links.
- To update the workbooks submodule run
git submodule update --rebase --remote