When cosmwasm 0.7 is release, this will mean a number of changes to contract development. There is also a new escrow contract release to start with as a basis. We should update the tutorial to match it.

This requires not only a tagged 0.7 cosmwasm for contract development, but a tagged wasmd that supports 0.7 contracts.

One of the barriers to entry is installing the editor and build environment. There is actually an online IDE to allow building wasm projects from rust, assemblyscript or C directly in your browser: https://webassembly.studio/

I would look at this to simplify the intro tutorial, but you would want a real editor if you go beyond the demo. Still, it may make the barrier to entry lower - consider this if the build system is a hinderance. If rust itself is the barrier to entry, comment here: https://github.com/confio/cosmwasm/issues/74

A step on the way to #22

I just merged cosmwasm 0.6.3 support into wasmd master (Jan 17, 11:00 UTC). We will make a wasmd tag when 0.38 cosmos-sdk is integrated.

We need to upgrade some docs. I will make a quick first pass to the obvious broken commands, but it would be good if someone goes through carefull to make sure all code samples and sample commands work properly. The rust code changes, but also the cli - notably the query commands.

Various items to improve text-wise

• "known vector attacks " -> "known attack vectors"
• when mentioning decimal and blake2b in the docs, it might make sense to mention why each is useful. By the way, blake3 is out now, which has significant parts written in rust
• early in the docs, on the Actor model page, the code is in Go. If this is for people writing Rust, it might be distracting or confusing. https://www.cosmwasm.com/docs/intro/actor
• on the canonical addresses page, the ?= operator may not be clear for some readers https://www.cosmwasm.com/docs/intro/addresses#canonical-addresses

I threw something together with rust/wasm and cosmos logos. Neither belong to me. Even ignoring trademark issues, the project should have it's own logo.

Also, this logo should be the same color as the title bar (change one or the other), and should have a favicon verion.

wasmcli suggests list-contract-by-code, which works.

Don't know where the repo for the docs is but the error is on first-demo

https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint works very well linting markdown. It helps you to organize headers correct way(indented) so the right bar will look correct.

Now that the nameservice contract is written and merged to cosmwasm-examples, we should really complete this section.

Right now it lands to http://docs.cosmwasm.com/ index page which contains sections like pictures and who uses. If you want this link directly into the docs(http://docs.cosmwasm.com/docs/intro/overview) take a look at this commit iov-one/docs@c5497e3.
you can make window.location.href = 'docs/intro/overview.html'; to land directly to the docs.

Let's throw a few more code samples early on. If nothing else, API definitions to go along with text. Here is some feedback from a reader to contextualize the issue:

• it would be nice to have more real code in the Intro section of the docs, ideally with some real usable code on the first page, Intro -> Overview.
• I definitely expected to see some real working code on the Getting Started -> First Contract page. It feels like things stay at 0 code for really long, then in the "Editing the Sample Contract" page it goes into fine-granularity code detail mode. If you can start introducing code much earlier, and at a higher-level, it might ease people into that section better.