These guidelines are a community resource. They are meant to help guide and inform you through your development process and ensure the highest quality results in your smart contract system and your end product.
The Guidelines are constantly evolving with expert feedback. All suggestions made here are managed by expert members of our community, who have experience with the best practices and common pitfalls of secure smart contract development. Their wisdom is meant to help you on your journey
{% method %}
The first thing is to get the GitBook API client.
{% sample lang="js" %}
$ npm install gitbook-api{% sample lang="go" %}
$ go get github.com/GitbookIO/go-gitbook-api{% endmethod %}
Each article is designed to read on its own, with a consistent style (Who, What, Why, etc).
We encourage feedback. This is just getting started and we want to be sure we are meeting peoples needs. At a minimum, please hit one of the happy/sad faces.
For a more detailed response, please report an issue on our GitHub.
For the moment, if you wish to contribute, please submit an issue as above. We will add a more formal contribution section with a style guide, etc in the near future.