I significantly underestimated how difficult going from my #SQL to static websites generated with that SQL data would be. It's overkill, but I'm wondering if I should get to work on learning #Rails to drop the SQL into that and have everything dynamically setup. >_< I'll move to Rails eventually anyway, but ugh.

What I've considered instead for the first run at this thing, to prove whether I should proceed with developing it at all, is pulling the SQL into #Ruby via a gem, then figuring out how to output the queried rows in a YAML format and/or CSV format for use with #Jekyll.

I'm having a hard time finding any resources online about doing something like this (and I imagine that there's a good reason for that), so if I do it and write it up as a blog post, it'll give me some cred. #webdev #programming

@bthall I'm not a #RoR person by any means, but I believe one of its selling points is that it handles (through ActiveRecord?) all the database gymnastics for you.

What you're describing sounds a lot more manual than what I used to see on #Railscasts. (BTW, even though there haven't been any episodes in a few years, you should check that out if you're interested in #Rails. It did pique my interest.)
I am interested in similar series, if they exist, for !Smalltalk or !Python frameworks, such as #Seaside, #Aida, #Django, #TurboGears. If someone knows of any, send me a link.