├── CONTRIBUTING.md ├── README.md ├── events ├── hosts.md └── onboarding.md ├── presentation-stash.md └── rails_guide.md /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to this repository 2 | 3 | Women Who Code DC gladly accepts additions to this repository! Here are the steps on how to get started with contributions: 4 | 5 | 1. Clone the repository: `git clone git@github.com:womenwhocodedc/ruby-on-rails-community.git` 6 | 7 | 2. From the cloned repository on your local machine, create a feature branch using `git checkout -b` with your *last name* and the name of your feature in this format: `lastName_myFeature` 8 | 9 | 3. Add your changes to your repo using the regular Git commands (`git add/rm` and `git commit`), then push to *your feature branch* `git push origin lastName_myFeature`. 10 | 11 | 4. Your feature branch will be visible on the main repository page, like so (example is from front end repository): 12 | ![alt text](https://github.com/womenwhocodedc/front-end-community/raw/master/assets/wwcpr.png "pull request view") 13 | 14 | 5. Create a pull request (PR) by clicking on "Compare & pull request", and be sure to reference @womenwhocodedc/ruby-on-rails-leads in your PR comment. Also be sure to reference the issue number in your PR if you are trying to fix an issue. 15 | 16 | 6. If everything looks good, the reviewer will merge your PR into the master branch and delete your feature branch. And then your changes will be in the main repository! However... 17 | 18 | 7. If you need to make changes before your PR has been merged (whether you want to or you've been requested by the reviewer to make more changes), you can continue pushing the changes to your feature branch; the pull request will be updated with your subsequent commits. 19 | 20 | And that's all there is to it! 21 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Welcome to Ruby on Rails 2 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 3 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 4 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 5 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 6 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 7 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 8 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 9 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 10 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 11 | 12 | ## What is this community for? 13 | 14 | This is a space where women (including trans and nonbinary folks) can come together and help each other learn and understand web development. We welcome devs of all levels and encourage those with more experience to help out those that are just starting. There's always at least one mentor/leader present to help you with best practices or to guide you through if you are stuck with a nasty problem! 15 | 16 | Every regular meetup will have the following format: 17 | 18 | * 6:30pm - Setup and start working 19 | * 7:00pm - Quick Introductions 20 | * 7:15pm - Talk (if scheduled) 21 | * 8:15 - 8:30pm - Wrap Up 22 | 23 | We want a majority of the night to be open for people to code and learn. If you are a first timer to coding or ROR we have suggested courses you can follow and encourage you to ask lots and lots of questions. Note that the first week of the month is especially for "first-timers". We will focus on providing extra support to those new to coding. 24 | 25 | For those who are more familiar with the language we encourage you to bring in projects that you are working on and also ask questions. I want to emphasize ASKING QUESTIONS! We want to build a community of awesome Rails devs and that requires sharing ideas and knowledge! We ask that you pleaaaaasee do not bring in or ask questions about work because they can be domain specific and not always constructive. 26 | 27 | Anyone should feel free to suggest talk topics or volunteer to deliver one. 28 | 29 | All events for Women Who Code DC are scheduled on our [Meetup page](http://www.meetup.com/Women-Who-Code-DC/). 30 | 31 | ## What if I'm a first timer that's never coded before? 32 | Check out our [Rails guide](rails_guide.md) for first timers, that contains information on Ruby, Rails, text editors, and more! Go through the recommended resources and feel free to ask lots of questions. 33 | 34 | You can also ask questions in the Women Who Code DC `#ruby-on-rails` Slack channel, or chat about topics like git and mentorship (among others) in our other channels. [Sign up](bit.ly/wwcdcslack) to request access. 35 | 36 | ## What if I'm a web development pro? 37 | 38 | We encourage you to attend the group, particularly on open lab or hack nights. You could work on a personal project, take one of the recommended courses to further your skills, help others with questions they might have, consider doing a lighting/tech talk, or consider being a lead! Women Who Code DC is also a great place to try out a conference talk you're giving for the first time. 39 | 40 | ### Lightning Talk Possible Topics 41 | 42 | * Present an app you're working on 43 | * MVC 44 | * Rails vs. Django (or any other framework) 45 | * Ruby vs. any other language 46 | * Networking/Internet Technologies 47 | 48 | ## What resources do you suggest? 49 | 50 | We've got a list of resources in our [Rails guide](rails_guide.md), but you can [jump right to the resources](https://github.com/womenwhocodedc/ruby-on-rails-community/blob/master/rails_guide.md#suggested-learning-tools) if you like. We check periodically to make sure the links work and things are up to date, but if you have something to add, feel free to submit a PR or open an issue. 51 | 52 | ## What do leads do? 53 | 54 | Leads are present to facilitate the study group. They communicate with hosts, schedule meetups, come up with curriculum, and are also available to ask questions. 55 | 56 | ## Can I be a lead? 57 | 58 | YES! We are always looking for more leads and if you're interested in getting involved in Women Who Code in any capacity talk to one of the leads present! 59 | 60 | ## How can I contribute without being a lead? 61 | 62 | We need lots of help coordinating events. If you want to help out please let us know :) 63 | 64 | ## Slack 65 | The WWC-DC community uses Slack to keep in touch, share resources, and chat about all things tech. You can use Slack to ask troubleshooting questions or general questions about coding (in any language) and the tech industry. We encourage you to sign up here: http://bitly.com/womenwhocodedcslack (and read our guide if you're new to Slack: http://bit.ly/slackguide) 66 | 67 | ## Building Access 68 | 69 | Certain building managements requires meetup hosts to let people in and do not encourage them being contacted. Please respect the policy, in case the location requires access to the building contact the group lead if information is provided, or drop a comment on the meetup page. We'll come and get you. 70 | -------------------------------------------------------------------------------- /events/hosts.md: -------------------------------------------------------------------------------- 1 | # Hosts 2 | 3 | Info about hosts (addresses, contacts, etc.) will be added here. They should be contacted to confirm a few days before and sent the RSVP list the day of. 4 | 5 | -------------------------------------------------------------------------------- /events/onboarding.md: -------------------------------------------------------------------------------- 1 | # Ruby/Rails Lab Lead Onboarding 2 | 3 | ## Steps For a Prospective Lead 4 | * Welcome email sent to prospective lead (usually by Education Director) 5 | * Welcome, ____________! I'll start by sharing a couple of our resources with you so that you can get a sense of our structure. The [WWCDC Ruby/Rails Community](https://github.com/womenwhocodedc/ruby-on-rails-community) repository is where we store important public facing documents, like Ruby/Rails resource lists and guides for first timers. The [WWCDC Ruby/Rails Leadership Resources](https://github.com/womenwhocodedc/organization/blob/master/leadership-resources/Education/Ruby-Rails/README.md) is a README that goes over some of the logistics of hosting a meetup and retaining attendees. [WWCDC Ruby/Rails Onboarding](https://github.com/womenwhocodedc/ruby-on-rails-community/blob/master/events/onboarding.md) lists some of the steps of becoming a lead, as well as a checklist of what we need to make sure you get access to. If that all looks good to you, let me know and we'll start the ball rolling by adding you to the [#ruby-on-rails_leads]() channel on our Slack group so that you can start coordinating with other leads. 6 | * Invite prospective lead to [#ruby-on-rails_leads]() on Slack to start coordination with other leads 7 | * For the prospective lead's first few meetups, they should shadow a current lead in at least the following ways: 8 | * creating the event on Meetup.com 9 | * leading the meetup 10 | * greeting attendees 11 | * helping with any code alongs 12 | * giving talks, especially regular talks like beginner's night 13 | * checking in with attendees after the meetup so they feel connected and involved 14 | * Once the prospective lead is comfortable, they should occasionally take the lead on the above tasks (either for the month or an individual meetup), and they should be given access to the second set of bullet points in the **Access** section below 15 | * More experienced leads should encourage this as it makes newer volunteers feel that they are valued and that they're putting their free time to good use volunteering for WWCDC 16 | * Experienced leads can and should still take the lead sometimes, but all leads should share responsibilities at this point 17 | 18 | ## Access 19 | * First 20 | * Slack - grant access to the following channels 21 | * All Leads 22 | * Language Leads 23 | * Ruby on Rails Leads 24 | * Hosts 25 | * Later, once committment is confirmed: 26 | * Make admin on Slack 27 | * Google Drive 28 | * Welcome email to hosts for logistics 29 | * Add as attendee for Google Calendar events 30 | * Make an organizer on Meetup 31 | * Add to this repo's team 32 | 33 | ## Publicity 34 | Announce on: 35 | * Twitter (have WWCDC tweet about it) 36 | * Slack 37 | * In Person 38 | * Blog Post on Medium? 39 | 40 | ## Operations 41 | * Always CC the women who code dc email address when corresponding with hosts (for Su) 42 | * Email the host a few days before + the day of the event 43 | * Double check on meetup comment 44 | * Email number of RSVPs/names for security 45 | * Day of the event 46 | * Post a comment in meetup for everybody about logistics (who/how to contact if you can't get in, any slides you have prepared, etc.) 47 | * Important Documents 48 | * [Rails Guide](https://github.com/womenwhocodedc/ruby-on-rails-community/blob/master/rails_guide.md) 49 | * [Presentation Stash](https://github.com/womenwhocodedc/ruby-on-rails-community/blob/master/presentation-stash.md) 50 | -------------------------------------------------------------------------------- /presentation-stash.md: -------------------------------------------------------------------------------- 1 | # List of ready presentations by speaker 2 | 3 | ## Katherine 4 | * [MVC in Rails](https://www.slideshare.net/secret/lk33Pi8rBgz8Pz) 5 | * [Databases and Active Record](http://www.katherine.tech/active-record/#/) 6 | * Getting Value Out of Conferences (needs adjustment) 7 | * Faking Data in Ruby (lightning talk) 8 | * Rails 3 vs Rails 4 9 | * Using Enums: A Case Study 10 | 11 | ## Erin 12 | * Ruby Fundamentals 13 | 14 | ## Mary-Katherine 15 | * [Intro to Git](https://drive.google.com/open?id=1FD-vzUPdxwnrJ06Mu69GfjZooCJePpjjq-ZEEnl35vs) 16 | * [Write Now, Abstract Later: POODR in Real Life](https://drive.google.com/open?id=18T3sZcrdnIho5_CsnILesjDIndNshY-ImnZGC57CVZA) 17 | * [Using NASA's APOD API to Build a Rails App](https://emkaydeum.wordpress.com/2016/04/28/tutorial-build-a-rails-app-using-the-nasa-astronomy-photo-of-the-day-api/) 18 | * [RailsConf 2017 Recap: Highlights, Talks, and How to Get the Most Out of Tech Confs](https://docs.google.com/presentation/d/1T7JJgEsKK2TnwKs9lNpbCA_r3uUfyUqR5h7KWw3j-IY/edit?usp=sharing) 19 | 20 | ## Tingting 21 | * [CRUD in Rails](http://slides.com/tingtingwang/crud-rails#/) 22 | 23 | ## All 24 | * Intro to Ruby/Rails 25 | -------------------------------------------------------------------------------- /rails_guide.md: -------------------------------------------------------------------------------- 1 | # Women Who Code DC Ruby on Rails Guide 2 | 3 | [Jump straight to the tools and resources](#tools) 4 | 5 | ## First Timers Section 6 | **(But we won't judge if this helps others too)** 7 | 8 | ![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png)![Ruby On Rails Icon](http://files.softicons.com/download/application-icons/ruby-programming-icons-by-ahmad-galal/png/48/RubyOnRails.png) 9 | 10 | *If you are brand new to Ruby or Rails, we recommend coming to the first meeting of the month which is First-Timers Night. You are welcome to come any week, but that first week will be the one we cater to beginners.* 11 | 12 | ### What is Ruby on Rails? 13 | Ruby on Rails, (ROR) is an open source web application framework written in the Ruby language. Technically, it is a package library (specifically, a RubyGem) that is installed. 14 | 15 | Rails establishes conventions for easier collaboration and maintenance. These conventions are codified as the Rails API (the application programming interface, or directives that control the code). The Rails API is documented [online](http://api.rubyonrails.org/) and described in books, articles, and blog posts. Learning Rails means learning how to use the Rails conventions and its API. Rails combines the Ruby programming language with HTML, CSS, and JavaScript to create a web application that runs on a web server. Because it runs on a web server, Rails is considered a server-side, or “back end,” web application development platform (the web browser is the “front end”). 16 | 17 | Rails is more than a software library and an API. Rails is the central project of a vast community that produces software libraries that simplify the task of building complex websites. Members of the Rails community share many core values, often use the same tools, and support each other with an informal network that is built on volunteerism. Overlapping the informal community is an economic network that includes jobs, recruiters, consulting firms, conferences, businesses that build websites with Rails, and investors that fund startups. Rails is popular among web startups, significantly because the pool of open source software libraries (RubyGems, or “gems”) makes it possible to build complex sites quickly. 18 | 19 | [source](http://railsapps.github.io/what-is-ruby-rails.html) 20 | 21 | ### What is Ruby? 22 | Ruby is a programming language. It was created 20 years ago by Yukihiro “Matz” Matsumoto. By most measures of programming language popularity, Ruby ranks among the top ten, though usually as tenth (or so) in popularity, and largely due to the popularity of Rails. Like Java or the C language, Ruby is a general-purpose programming language, though it is best known for its use in web programming. 23 | 24 | Ruby is known among programmers for a terse, uncluttered syntax that doesn’t require a lot of extra punctuation. Compared to Java, Ruby is streamlined, with less code required to create basic structures such as data fields. 25 | 26 | Ruby’s key advantage is RubyGems, the package manager that makes it easy to create and share software libraries (gems) that extend Ruby. RubyGems provides a simple system to install gems. Anyone can upload a gem to the central [RubyGems website](https://rubygems.org/), making the gem immediately available for installation by anyone. The RubyGems website is where you’ll obtain the most recent version of Rails. And it is where you will obtain all the gems that help you build complex websites. 27 | 28 | [source](http://railsapps.github.io/what-is-ruby-rails.html) 29 | 30 | ### What’s the difference between Ruby and Rails? 31 | 32 | Remember that Rails is a web framework built using the Ruby language. Ruby is like the raw ingredients for a cake, the flour and sugar and so forth. Rails is like the boxed cake mix. It still has the same ingredients underneath, but it's packaged up to be quicker and easier to use. 33 | 34 | *What’s a framework?* 35 | 36 | A framework is a set of rules, conventions, tools to help you from reinventing the wheel. Frameworks make it so you don’t have to do common, tedious things that anyone making a website would have to do again. One of the core problems a website tries to solve is how to turn whatever the user requests (in the form of a URL) into code that accesses a database and returns something. Rails has developed a methodology and created an API that standardizes these interactions so you can focus on actually creating your app. 37 | 38 | *What’s MVC?* 39 | 40 | The interactions between what a user sees on the webpage and what happens in the backend is complicated and can get very very large and intertwined. Rails uses an architecture called MVC to design the framework. MVC (model-view-controller) separates each part of that interaction into separate layers. It also help organize your code so that if any one new joins the project they know exactly where specific functions of the app will rest. MVC is pretty important to Rails and a lot of the intro courses will go over it but feel free to dive deeper into it. 41 | 42 | ### What is Ruby on Rails used for? 43 | 44 | Twitter was initially built on Rails. It’s since moved off of the platform for scalability reasons. You’ll see a lot of Rails introductory classes use a Twitter-like application to explain the framework. Here are other sites that use ROR: 45 | 46 | 1. Groupon 47 | 2. Bloomberg 48 | 3. Airbnb 49 | 4. SoundCloud 50 | 5. Square 51 | 52 | [source](https://thecoderfactory.com/posts/top-15-sites-built-with-ruby-on-rails) 53 | 54 | ### Should I learn Ruby first or Rails first? 55 | There are differing opinions on this but I like this approach from http://railsapps.github.io/what-is-ruby-rails.html: 56 | 57 | Do you need to study Ruby to learn Rails? The short answer is “no,” with one caveat. To avoid feeling overwhelmed when you first begin learning Rails, it is advisable to spend at least an hour with an introduction to Ruby so you are comfortable with the syntax of the language. You should be prepared to recognize correct formatting when you type Ruby code in your text editor. 58 | 59 | Be assured that you will indeed learn Ruby as you develop proficiency with Rails. Whether you study Ruby or not, you’ll develop Ruby skills as you learn Rails. Rails is largely a “domain specific language” that has its own set of directives distinct from the Ruby core. As you learn the Rails “language” you’ll be using the Ruby language syntax. 60 | Your hardest challenge will be to learn the names of the structures you see in code examples. This is why it is helpful to work your way through a short introduction to Ruby. You’ll need to be able to recognize when you are looking at an array or a hash. You should recognize when you are looking at an iterator or the Ruby block syntax. Eventually, you’ll recognize more exotic Ruby formulations such as the lambda. It is okay if you can’t write a lambda function or even know when to use one; many Rails developers start work before learning Ruby thoroughly. 61 | 62 | ### How do I install Ruby? 63 | If you use the link below to install Rails, it will also install a recent version of Ruby. 64 | 65 | ### How do I install Rails? 66 | Rails used to be quite difficult to install but recent tools have made it a lot easier. On Macs you can use homebrew and RVM to install rails. Then install the Rails gem. On PCs railsinstaller makes it easy to install all the components. 67 | 68 | This website offers guidance on how to install Rails on Macs, PCs and Linux systems: http://installrails.com/ 69 | 70 | You can also use tools like Nitrious.io and c9.io to build Rails apps in a virtual machine. This doesn’t require you to install anything on your local machine. Most of the basic functionality is free from these websites but if you want to do more you can pay. 71 | 72 | ### What other tools do I need? 73 | * Laptop: You can use a PC, Mac, or Linux. There's an even mix of PC users and Mac users in this group who can share their perspectives, but if you're just starting out your operating system doesn't matter. 74 | * Text Editor: We do not and should not code in regular word processors. You need a user-friendly text editor that does syntax highlighting. These are some that we recommend: 75 | * [Sublime Text](http://www.sublimetext.com/) *Note: You can pay to stop seeing the occasional suggestion to buy it, but you do not have to.* 76 | * [TextWrangler](http://www.barebones.com/products/textwrangler/) - MAC only 77 | * [Notepad++](http://notepad-plus-plus.org/) 78 | * Terminal/Console/Command Prompt(CMD) 79 | *It's a good idea to get comfortable using command prompt, most tutorials have an introductory lesson covering this. If you want more information covering this check out [Command Line Crash Course](http://cli.learncodethehardway.org/book/) 80 | * Git and GitHub: Version control is a really important part of any professional developer's toolkit. It helps with backing up your work, collaboration, and managing changes through iterative versions. You would need Git installed on your computer, and an account on [Github](https://github.com). For an introduction to Git and Github, refer to our [Intro to Git presentation](http://nupurkapoor.github.io/intro-to-git/#/) or [Github's Suggested Resources](https://help.github.com/articles/good-resources-for-learning-git-and-github/). 81 | 82 | ### How do I run my ROR website? 83 | Rails comes with a built web server called WEBrick that you can run to test out your apps locally (cool!). When you are ready to deploy online there are several popular hosting services like Heroku that make it easy to run your app live. 84 | 85 | 86 | ## Suggested Learning Tools 87 | 88 | You will get the most out of our meetups if you follow one of our suggested resources. These are the classes/books/resources that our members know the best and can offer the most support for. 89 | 90 | We will not assist with work problems. We are here to help you learn the skills that will help you solve work problems, but asking about work related problems derails the productivity of everyone at the event. Repeated requests for solutions to work problems will result in our leaders asking you to leave. 91 | 92 | #### CS Beginner 93 | 94 | If you want a great introdution to Computer Science and what programming is watch: [Harvard's CS50 Intro to CS class](https://courses.edx.org/courses/HarvardX/CS50x3/2015/info). The first 3 weeks are essential but if you get into it...keep watching :) . 95 | 96 | ### Ruby Beginner 97 | 98 | * [Try Ruby](http://tryruby.org/levels/1/challenges/0) 99 | * Short Interactive, Intro to the Ruby Programming Language 100 | * [Code School](https://www.codeschool.com/paths/ruby) 101 | * Take the Ruby Language Path to get a deeper introduction to the language 102 | * [Codecademy](http://www.codecademy.com/en/tracks/ruby) 103 | * An introduction to Ruby that runs from the basic all the way up through object-oriented programming. 104 | * [Ruby Koans](http://rubykoans.com/) 105 | * Testing based approach to learning Ruby (I really like this guide because it teaches you test based development). Works best if you do not look to closely at the error messages because they give away the answer. 106 | * [Learn Ruby the Hard Way](http://learnrubythehardway.org/book/) 107 | * Go through the exercises 108 | * [Ruby in 100 Minutes](http://tutorials.jumpstartlab.com/projects/ruby_in_100_minutes.html) 109 | * This takes you from introductory concepts like creating variables all the way to objects and attributes in 100 minutes. 110 | * [Ruby Algorithms](https://github.com/kdmcclin/ruby-algorithms) 111 | * This repository is a work in progress but contains a range of algorithms that you might find helpful. 112 | 113 | ### Rails Beginner 114 | * [Rails for Zombies](https://www.codeschool.com/courses/rails-for-zombies-redux) 115 | * a intro to the Ruby on Rails platform 116 | * [Jumpstart Blogger](http://tutorials.jumpstartlab.com/projects/blogger.html) 117 | * Introductory Rails app tutorial, building a blog 118 | * [Rails Tutorial](https://www.railstutorial.org/book) 119 | * a pretty in-depth but excellent intro to building an app in Rails 120 | * [One Month Rails](http://onemonthrails.com/) 121 | * a more visual, interactive version of the guide above but it costs money 122 | * [Codecademy](https://www.codecademy.com/courses/learn-rails) 123 | * In addition to Ruby Codecademy also has Rails app tutorials and tutorials on several APIs. 124 | 125 | ### Intermediate Projects 126 | 127 | * [Codecademy](https://www.codecademy.com/apis) 128 | * In addition to Ruby and Rails tutorials, they also have several tutorials on working with various APIs 129 | * [Build 12 apps in 12 weeks!](https://mackenziechild.me/12-in-12/) *Note: If using Devise with these, you will probably need to use the most recent version of the gem to avoid incompatability issues, not the version he specifies.* 130 | * You can work on either of these projects together: 131 | * https://github.com/LizAkins/TicTacToeSkeleton 132 | * https://github.com/WomenWhoCode/RubyTuesdays-ConnectFour 133 | 134 | ### Ruby/Rails Advanced 135 | *Ready to contribute to larger projects? Check out the following:* 136 | * [Assembly](https://assembly.com/) 137 | * [Contributing to Open Source](https://github.com/womenwhocodedc/organization/blob/master/learning-resources/awesome-coding-resources.md#open-source) 138 | 139 | ### Other Resources 140 | * [Hacker Collective Resource List](https://github.com/HackerCollective/resources/blob/gh-pages/Programming/Web%20Development/Backend/RubyOnRails.md) 141 | * [Facebook group for RoR](https://www.facebook.com/groups/HHRuby/) 142 | * [RailsCasts](http://railscasts.com/) 143 | * These are great screencasts of tips, tricks, and tutorials. For pro episodes you have to subscribe but there are many great free ones. 144 | * [Rails Documentation](http://guides.rubyonrails.org/) 145 | --------------------------------------------------------------------------------