Week 1 - Kick-ass README + Intro

or how to submit your Week 1 update.

1) Write a kick-ass README

Your README is your project's front door, your hello world. It's how you invite contributors, users, and supporters into what you're building. If you're so excited about your project (we know you are), why not showcase it?

Also, we'll be using your project's README everywhere inside the program and hundreds (thousands?) of people will see it, so make sure it looks great!

We won't spend time here to teach you how to write a good README, though. There are TONS of great content on the internet showing you how to write great READMEs (here, here, a video here). Check them out, Google for more, see what works for you!

But include a bat-signal!

What we want to focus on, though, is on including what we call a bat-signal into your README. Your bat-signal should be up top in your file, and its goal is to hook someone in seconds after reading it, if they are indeed a great fit for what you need. The key property of a bat-signal is that it is very specific.

Here are some examples of great bat-signals:

  • "We're looking for Rust developers interested in diffusers, who can help us figure out some performance bottlenecks with our current implementation".

  • "We're looking for at least $2,000 in sponsorship so that our project lead can go full-time into building this project"

  • "We're looking for feedback on our consumer app, and ideas on how to expand this project into new use cases inside consumer crypto and towards blockchains beyond Ethereum"

  • "We're looking for app developers that might need an API for superfast video transcoding and will want to push those videos to Youtube, so that we can better test our early prototype"

These should be tailored to your project, of course. So, go on and spend a few minutes thinking "who would be an absolute game-changer for my project and how do I bat-signal to them?".

Once you have that bat-signal of what would be a game changer for you, we'd suggest putting it out there to others in the program and beyond via How to share to Twitter. See if someone can help you make it happen!

2) Make your intro

Let everybody in the program get to know you a little better! We've seen time and time again the magic of just showing up as yourself as the person behind what you're building. We guarantee that if you make a great intro, people in the program and outside will be way more likely to connect and support you along the way.

Our recommendation

The best way to introduce yourself is to record a short video (30 secs), using your phone or your webcam. No need to script anything or polish it, the more informal and spontaneous the better! Here are some tips:

  • Don't talk about your project, but about you. The README is for your project.

  • Tell people your name, where you live, what you love to build.

  • Don't be afraid to go off-topic and mention any hobby or passion outside of building!

Here's a good example of an intro video: https://drive.google.com/file/d/1_BXO7cUhdsmrCZ60_jurQry_SaKbFHTT/view?usp=sharing

If you don't want to record a video, feel free to submit a paragraph of text as your intro. For people participating in teams, every team member can submit their intros separately. All intros will be published on the program's directory here: https://app.100.builders/directory.

3) Submit update

You have until Sunday August 27th to submit your update through a form here: https://airtable.com/apphEEU2zIyK2h2TA/shruM3AlT8bQg8INq

Last updated