Developer relations & educational content
Ecosystems do not grow because the protocol is good. They grow when a developer can get from nothing to a running app in an afternoon. We build the material that makes that afternoon possible.
Tutorial series
A curriculum, not a pile of clips: a first environment, a first dApp, then the subjects a developer meets in the order they meet them. Peer Dev is the worked example — a channel of gno.land tutorials, produced end to end by the coop.
Technical writing
Documentation, guides and reference material written by people who read the code. The same engineers who audit and contribute upstream write the pages, which is why the pages stay true when the protocol moves.
The channel, run as a production
Scripting, filming, editing, motion and publishing schedule, by the film crew that does the rest of the coop’s work. This is where the two crews cross: engineers who can explain the subject, and a crew that can shoot it.
Who does it
David Gozlan is Project Lead & DevRel on Peer Dev. The engineers who appear in it are the ones building on the protocol the rest of the week.