(Re)introducing the Colony Starter

This summer, Colony’s distributed hackathon saw over 50 participants join in from 15 countries over the course of about 3 weeks. It was tons of fun, and we got a little sample of the creativity and ingenuity out there in the Ethereum ecosystem.

We at Colony also learned a lot about our own tools and products. We suddenly had *real* people out there using our tools to tackle some pretty ambitious challenges, and were bombarded with questions we got about exactly how to use things like colonyJS, trufflePig, and the colonyNetwork contracts.

To help people get to building with Colony rapidly, James and Chris had a sudden flash of inspiration, and created the hackathonStarter: a standalone gitHub repo that contained, among other things, all the tools a developer needs to set up with the Colony stack. It was a huge success, and most of the winning projects used the hackathon starter as a base for their projects.

So we have decided to roll with that success, and improve it:

(Re)introducing: The colonyStarter kit!

This is a toolkit for hackathons, side-projects, proof-of-concept builds, and integrations testing — it contains *everything* one needs to set up a project using the Colony stack, including Ganache, Truffle, TrufflePig, and more than a few snippets of example code.

colonyStarter makes setting up a new project that integrates with Colony a simple 3-step process:

Step 1

Globally install the colony-starter package:

yarn global add @colony/colony-starter

Step 2

Move to your working directory and unpack the colony-starter-basic package:

colony-starter colony-starter-basic

Step 3

Move to your new project directory and checkout the colony-starter-basic readme:

cd colony-starter-basic

That’s it! Using the included scripts, you can quickly and easily stop/start Ganache, serve your app fresh ABIs with TrufflePig, re-deploy your contracts (or the colonyNetwork contracts), and even run your tests. Wowzers!

If you’ve got any questions about how to get started, how to keep going, or just want to bounce ideas around with others, you can also head to the *brand new* build.colony.io developer forums, or read the documentation at docs.colony.io.

Now go forth and #BUIDL!

P.S. If you’re reading this at ETHBerlin, come say hai to the Colony team, add your input to our collaborative mural, and grab some swag!


If you have any feedback or stories to share, reach out to us on Twitter.

Colony is a platform for open organizations.

Join the discussion on Discourse, follow us on Twitter, sign up for (occasional) email updates, or if you’re feeling old-skool, drop us an email.