Granted my above idea would sort of overlap you with railscasts or asciicasts, however the one issue is that thoses casts go out of date. If your site or another site focused on idioms only, and the best practice to use those idioms, peer-reviewed with comments and maybe versioning, then it would easily become a go-to reference for developers, that would always contain the most up-to-date method of implementing said idiom.
For instance, you want to implement authentication. Right now the best thing you can do is head to railscasts, see what the latest screencast is for authenticaiton. Ah, november 2010. Might as well be ancient history! Perhaps there's a newer, easier, more-accepted authentication gem out there. Or maybe not! You just don't know. So what's next, maybe check some blogs, github, do some date-specific searches on google, etc.
If you or someone else had a site that basically said, "here's the current accepted practice for implementing authentication, and here's why", then that saves so much time!
Yea - there’s a lot of overlap with different things. Ryan’s screencasts on one hand, which are amazing even when out of date, and things like http://ruby-toolbox.com/, which give you a list of gems to look at/choose from on the other. Plus github itself is the best place to find actual code, and is peer reviewed in the sense of watch counts, etc...
All I can hope for is that with some community involvement, ScaffoldHub might become something useful in the middle: not in depth tutorials, not a code repository, but a series of helpful working examples.
For instance, you want to implement authentication. Right now the best thing you can do is head to railscasts, see what the latest screencast is for authenticaiton. Ah, november 2010. Might as well be ancient history! Perhaps there's a newer, easier, more-accepted authentication gem out there. Or maybe not! You just don't know. So what's next, maybe check some blogs, github, do some date-specific searches on google, etc.
If you or someone else had a site that basically said, "here's the current accepted practice for implementing authentication, and here's why", then that saves so much time!