Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Tree: d664928d6c
Fetching contributors…

Cannot retrieve contributors at this time

313 lines (193 sloc) 20.926 kB
layout title permalink

The How to Guide

Hosting your first Rails Girls event

Our aim is to give tools for women to understand technology. The Rails Girls events do this by providing a great first experience on building the Internet.

Rails Girls was founded in end of 2010 in Helsinki. Originally intended as a onetime event, we never thought to see so many local chapters all around the world! This guide has been put together to help you get started.

Please contact us at if you want to organise a local chapter. The roadmap for future events can be seen at

The Basics

Rails Girls events are non-profit. We don’t charge the participants and do not pay for coaches or speakers. Participants don’t need any previous knowledge about programming and there are no age-limitations. All the participants need is a laptop and some curiosity.

The two-day event includes a lot of small group working and short focused talks on programming, design and web. No panel discussions or podium-talks - the spirit should be informal and hands-on. The more you can remove abstractions and add inclusivity the better.

Rails Girls philosophy

  • Show sparks, personality and keep in mind the big picture. Explain, repeat and always tie what you're telling into a larger context.
  • Internet was made by people and it doesn’t break by a little tinkering. Continuously show the human side: encourage coaches to talk about open source communities, their programming idols and their aspirations.
  • Copy-pasting rules. Programming per ce isn’t central - you can't really learn to speak chinese in one day, in a similar manner you can only learn the basic vocabulary and expressions in coding. The goal of every event is to make something visible!
  • Girls run this world! But also women, ladies, even boys are allowed in. More than semantics we're interested in a mindset. Both founders we're born in the Spice Girls era, they don't see the word girl as condescending or cutesy-cute.


Every Rails Girls event starts with an installation fest where the setup is pre-installed to the girls computers. See for readymade instructions. The installation fest can include short talks, but the main point is to offer some sparkling wine, get everything set for the next day and the girls to know each other. The timeframe is tentative - you know your audience and what suits them best. We've hosted events both during weekend and weekdays. Also, doing two evenings (4PM - 22 PM) might be a more suitable solution for your community needs.

Learning objectives of the workshop:

  • Understanding what is the difference between dynamic and static web page.
  • Vocabulary of the web: developing a basic understanding of what components make a web application. Understanding the ABCs of coding: strings, methods, variables, arrays, exclamations, chaining, hashed, symbols, blocks.. as well as the tools (terminal, browser, text editor). Creating a conceptual understanding of webs building blocks: programming languages, frameworks, databases, infrastructure.
  • Have an idea of how to move forward in the programming world: both online and offline.

Example programme

Every Rails Girls event starts with an installation fest where the setup is pre-installed to the girls computers.

The installation fest can include short talks, but the main point is to offer some sparkling wine, get everything set for the next day and the girls to know each other. The timeframe is tentative - you know your audience and what suits them best. We've hosted events both during weekend and weekdays.

Friday evening: Installation

19:00 - 21:00 Installations and getting to know each other Hint: Have a coach-table where problematic computers can be brought to.

Some installations will fail: be prepared to set girls in pairs, don't use endless amounts of time.

Decorate the place with balloons and posters. Make together a fun playlists for the evening.

Come up with activities to break the ice: ask the girls to write why they are attending the event on post-its or to draw and describe their dream web app.

21 -> Coach dinner Go through the application with the coaches on a dinner.

Saturday: Workshop

09:00 - 10:00 Registration and coffee Hint Reserve enough time for people to mingle and to solve any problems there might be with installations. Give out workbooks, collect acronyms for the Bento exercise.

10:00 - 10:10 Welcoming words Hint Mention sponsors, show what we'll build, tell what programming is.

10:30 - 11:00 UX workshop

11:00 - 11:30 Introduction to programming Hint Ask one of the coaches to do this. Explain why learning Ruby basics is important even though they'll be using Rails.

Themes to cover:

  • The difference between dynamic and static websites: what are web apps?
  • What are programming languages? What is Rails?
  • The tools we’ll be using: browser, terminal, code editor, folder structure

Show & tell with, first three-four exercises all together.

11:30 - 13:00 Workshop time Going through (slowly!) the curriculum at Stop to explain what you’re doing and what the different concepts mean.

Try to aim for simple explanations even with the cost of accuracy. You don’t need to talk about all underlining concepts. Just try to answer questions when they arise, or move on if they’re too hard or out of scope. You are not here to teach perfect coding skills but to show how to get stuff done. One has to learn how to build web apps before learning how to do it well.

Concepts to cover:

  • Rails Generators
  • Scaffolds: Rails App Structure
  • Gem Management
  • MVC, REST/Resources
  • Models and Active Record
  • Controllers and ActionController
  • Views and ERB

Tips: Coaches are people too. They are doing this for the first time too. Teaching might be hard and intimidating, so remember to be available to help coaches or groups with difficult situations or just provide support and encouragement.

13:00 - 14:00 Lunch

14:00 - 14:30 Bentobox exercise Putting technical jargon into a context with a conceptual model called Bentobox.

Two exercises: 1) Going through the 10 technical concepts with the physical Bentobox boards. 2) Going through the words the girls have themselves submitted with the coaches.

14:30 - 18:00 Workshop time.

Time to continue working on the applications. Monitor the situation: when it seems like people have a hard time concentrating, have the coaches or other speakers give quick lightning talks.

Example topics for lighting talks:

  • Real (female) programmers telling what their career has been like.
  • Design: UX & UI. Making mockups together either with paper or computer.
  • Fun ways of explaining technical concepts and recent frameworks: what is CoffeeScript explained in 80s pop songs? How would you describe GitHub? What coding and creative writing have in common?
  • Show us something real: don’t speak in abstractions, be spesific and tell stories.

Once everyone has finished their app, there is time to extend the application by modifying the CSS, implementing commenting systems etc. Allow enough time for experimentation.

19:00 After party Hint: Invite everyone, also the local developers, boys, those who weren't accepted, to join!

Fork this project on GitHub, add yourself, and send us a pull request.


  • Programming 101 slides
  • Bentobox exercise

Promotion of Rails Girls

Every Rails Girls workshop will get a custom website at where the information is collected and then stored. For past cities, see

While the event is underway, remember to take pictures, collect tweets and ask questions from the participants. We love to write blog posts about the speaker and participant experiences. Also a list of the coaches is required.

How to find local developers?

  • Google. Almost every country has some sort of a Rails or Ruby community (sometimes called Ruby Brigade or Ruby Tuesday). Look for Hackernews meetups, GitHub contributors or Dribbble draftees. Find the local open source scene. Surf the technology conferences (here's a list of Rubythemed ones, but others are cool too) and meetups at Call software development houses, big and small. Don't forget IRC and podcasts!

  • Check out hashtags like #rails #ruby and #opensource from Twitter search. To find people from say close to NYC, use the following search operators "near:NYC within:15mi". Some countries have specific hashtags like #Rubysur and #RubyArg they use, remember to ask!

  • Startup community. Startup Digest is a good beginning point for events and communities.

  • Often there are one or two key persons who will be able to introduce you further, the technology world is surprisingly connected.

How to find participants?

  • Use social media: Facebook, Twitter & local networks such as Weibo. Friends, girlfriends, co-workers!

  • Local Girls in Tech, DevChix, Geek Girl chapters etc. Check out also Twitter lists like @anitaborg's Tech Women Programs and similar.

  • Think outside the box: universities, book clubs, music stores, design agencies, Etsy. We want girls who are interested in technology, but they can still have very varied backgrounds.

How to get press?

One of the big aims of Rails Girls is to make it more mainstream for girls to build the web. That’s why we like to engage the local press and bring front the participants and their enthusiasm. We’d be happy to help prepare a press-release for the media. Check out for more.


Rails Girls talks to a demographic that might be hard to reach other ways: women who have an interest in technology, who are possible users, employees or partners of the sponsoring company.

We are looking for sponsors who are active participants in the local technology scene, whether it’s a startup or a big corporation, a non-profit or a government organization.

Also non-traditional technology companies can be approached: kids stores, universities, women's magazines, beverage brands etc. They all should however have some affiliation or interest in technology.

Rails Girls should always be kept non-profit: if there's money left, it should be used to support the future activities of the attendees.

How much does it cost?

The costs approximated below for 30 participants, 10 coaches - but they may vary a lot. It's easiest to try to get a local sponsor to pay the bills directly or partner with someone who has a set account to handle money. These calculations are done in Finland, in €, where food & alchol is very expensive, but spaces are often free. All in all you should be able to organise an event easily for a little over a thousand euros.

  • Sparkling wine + cups for the installation festival. 6 bottles, 6 euros a bottle. 36 euros.

  • Breakfast Coffee, a bun. 40 times around 5 euros. 200 euros

  • Lunch. Catered lunch can be around 15 euros, but you can do with a lot less by cooking yourself. Add some water and coffee (50 euros). 650 euros.

  • Marketing materials. Printing workbooks, ordering stickers, posters and other swag. Again, varies a lot, maybe you can use someones printer, but at least around 200 should be reserved.

  • Coach dinner. At a restaurant or homemade. A way to say thank you to the coaches for their volunteer work. Around 20 euros per head. 200 euros.

  • Space. Try to get this one sponsored/free, they can be really expensive. Often startups are co-operative and can offer their space for use (esp. on weekends). 0 - XXXX euros.

  • Afterparty. It's nice if you can throw a good party with free beverages, but can also be done low-key in a local bar or on set/ in the park! 0 - XXXX euros.

  • Travel expenses. If you don't have any RG-team members in your country, consider inviting us over. We don't do fancy hotels, promise! Same if you want to invite speakers to your event. 0 - XXX

  • Total 1286 euros.

What do sponsors get?

  • Logo on event website
  • Rollup space at event, opportunity to distribute handouts and/or swag
  • Possibility to speak for 5 minutes
  • In most events there are official pictures taken that the sponsors can use afterwards

Don’t give out the participant info, but sponsors are free to hang out at the event and be sure to include a short message to the thank you -note. Sponsor swag may be included in the goodie bag to an extent: however it should be something tasteful, not trashy and related to girls.


Who can organise a Rails Girls workshop?

Anyone. What we look for is a group of people dedicated in making this a stellar first experience in the world of web making for girls. What we hope to see is some (not all) of the following:

  • Contacts to the local developer scene. We are pretty technology agnostic, so it doesn’t have to be purely Ruby & Rails people. In practice every event needs 5 or more coaches that have basic knowledge of Rails and two days to contribute. In general the events have been around 25 - 40 people strong.
  • Event organisation know-how. Nt heaps, but some practicalities under the belt.
  • An inkling of an idea where to look for girls interested in technology. University, literature, arts, sports - we try to look for people who are interested in Internet, but do not have experience in coding.
  • Willingness to guide the girls in the future if they have questions or want to organize their own events or find local developer gatherings.

Start by filling out and someone from our team will be in contact

What kind of venue is needed?

We recommend choosing a venue with a built-in infrastructure for around 30-50 persons. For a programming event, this means:

  • High-speed, tested Internet. There’s going to be over 30 computers online all the time. Add to that mobilephones, streaming music, funny videos and you get the picture!
  • Space for 4-6 person groups to gather together: chairs and tables, sometimes big pillows will do! This doesn’t have to be in the same room.
  • Possibility to set up extension chords and a projector.
  • Location for food and beverage setup - lunch space for catering or a nearby lunch venue.
  • External monitors for teams are encouraged but not mandatory, helps the coaches show what is happening in the code.

Ask where local developer meetings are usually hosted. Often co-working spaces are also willing to negotiate deals to gain some visibility among new people.

What is expected from the coaches?

Rails Girls events are organized around small groups, ideally maximum of 4-5 persons per one coach. The coaches don’t need to be hardcore experts on Rails - basic knowledge and willingness to explain trumps expertise. We are looking for people who like answering questions and can keep an upbeat and positive atmosphere through a period of 8 hours!

You can get to know the curriculum by checking out There is also always a pre-event coach dinner where we’ll go through some pedagogical suggestions and check everyone knows what is happening. Avoid jargon, tie examples to what your doing, encourage asking questions. The installation instructions can be found at

We hope the coaches are ok with having their name and twitter-id/github/some mean of contact on so the girls always have a local face to answer their questions.

In addition, we encourage coaches to come up with additional exercises for the group. After completing the ideation app many girls will want to try tweaking the look & feel of the site, implementing commenting, Facebook sharing, pushing the app to Heroku etc. We have some plans to include these coach-planned mini-lectures in the site as well.

  • Want to become a Rails Girls coach?
  • Letter for the coaches

What materials do I get?

Each Rails Girls event gets a specific webpage.

In addition we’ll help you out with the goodie bags, poster templates, workbooks and other swag like stickers, reflectors and so forward. All of the materials can be found on this site. You can also ask the sponsors to include some sponsor materials if they wish. We are always looking for creative outlets for the Rails Girls brand, if you have ideas, let us know!

So far we've had

  • Stickers
  • Reflectors
  • Tattoos

How do I choose attendees?

In the form we ask only two questions: do you have any previous background in coding and why would you be a good participant for Rails Girls

Rails Girls is intended for anyone and we want to keep it flexible enough for learners any age. However, make clear to the attendees what to expect: Rails Girls won’t make anyone into a coder, so people looking for i.e career change will be disappointed. On the other hand we like people with very diverse backgrounds and loads of enthusiasm.

After selecting participants we generally split them into three groups:

  1. people with no previous programming experience
  2. people with some front-end experience (HTML, CSS, Javascript) and
  3. people with a little experience in programming or a background in computer sciences. You can use the different name-tags for each group if you want to (rubies, foxes, octocats, rails..)

What happens after the event?

Inviting real developers to coach is Rails Girls sessions not only gives the participants a chance for hands-on education, but also makes the barrier to enter the technology world lower. How to keep the girls coding?

  • Encourage them to continue practicing by trying different exercises like Codecademy and such.
  • Mention at least two forthcoming developer events where the local coaches will be. Try to get the girls to attend actual developer meetups
  • Invite everyone to the Facebook Group where they can ask questions.
  • Invite the girls together again within a month. You can host these meetups at the Rails Girls global meetup page - we’ll be happy to promote events. However, it doesn't matter under which brand you want to continue meeting - the important thing'


This is a small checklist for your event. Rails Girls can be thrown together in a matter of weeks, but to truly have time to make a good event, prepare at least two months. Not all of these steps are of course mandatory and they are here just to help you remember.

Before the event:

  • Fill in the application and the team will contact you!
  • Start working with the project plan template on Google Docs
  • Decide dates and set a venue
  • Reach out for the local coaches - try finding five people who commit to taking part
  • Release the website: write the copy and suggest a theme

    1. Dates and location.
    2. Application deadlines.
    3. Short introductory text, around 200 characters. Check out the past events for inspiration!
    4. Speakers of the day
    5. Partners - a two parapgraph sentence and a logo (100 x 100px or 250 x 90px and in png format)
    6. Coaches with twitter-handle
  • Start marketing the event

  • Start looking for sponsors
  • Reach out for press and write a pre-event story
  • E-mail accepted participants and non-accepted applicants
  • E-mail installation instructions and last minute event details
  • Set a date for coach dinner and send them instructions

During the event

  • Tweet!
  • Remember to take photos
  • Interview participants and speakers about their experiences

After the event

  • Update website to include pictures and possible blogposts
  • Invite participants to Facebook group
  • Send a thank you note to participants
  • Send a thank you note for organizers
Jump to Line
Something went wrong with that request. Please try again.