I really applaud the fact that you're doing this, Mark! I think it's
an awesome idea and can have a major impact.
I agree with Bruce. I have a few additional tips to share.
You may want to decide on an audience. If 50% of your attendees have
never written a for-loop, and 50% people of your audience is using Git
on a daily basis, it will be very challenging to run a class that's
effective for everyone. Perhaps you can either market it to pure
beginners (i.e. no coding experience), or coders who have never done
web development, or experienced web developers who have never used
Rails.
I will say that among the first two groups (non-coders and coders who
have never done web development) the learning curve for Rails is
extremely steep. In my web-app development class, I decided against
using Rails despite the fact that all of the students are required to
have some experience programming. My feeling is that the mental model
for Rails is really hard for beginners to wrap their heads around,
particularly if they've also never really seen HTML, CSS, JavaScript
or worked in a client-server model, or done real OOP. So you might
gear it towards people who have done web development, but have never
used Rails.
I'm not familiar with Schneem's approach, so he may have solved some
of these issues. But I have seen someone try Hartl's approach in a
free community class, and it had a high attrition rate. I'd be *very*
interested in hearing more about the Railsbridge approach, Bruce, and
how it worked out for you.
These are just my thoughts, so people may disagree! I'm happy to offer
any other advice based on my experience if you're interested.
Cheers,
-Semmy