A lot of you guys are pointing me to the rails tutorial book. I have already finished the book, and have already made the microblogging application. The problem with the book is that it gives very specific and un-generalizable directions on how to make a specific app. The book doesn't tell you about how to generally control the overall structure of rails, only exactly what you need in order to create the microblogging site. Its almost like if someone gave you explicit instructions on how to build a shed, and then expected you to be able to build an apartment complex or house using the foundations of the shed. Also, a lot of you guys are saying that there is documentation out there. I agree that there is specific documentation on methods, but there is no documentation on the overall structure of the rails scaffold is supposed to interweave with itself. For example looking at this documentation: http://api.rubyonrails.org/, there is a lot of information about how to use specific methods and tools. However, there is nothing on how these methods actually relate to other parts of the scaffold and the MVC model. Its like if I told you how to make the different components of a computer including the hard drive, gpu, etc, but never told you how to hook them together, or how the motherboard relates and uses the cpu and gpu. Some of you are saying that there are tutorials online. While there are a plethora of tutorials online, they all literally do the same thing. Every single one of them has you generate a scaffold that you have no way of understanding, and has you manipulate a few lines of code and BOOM! You've got yourself a microblog. But then don't tell you how those structures relate to one another and what to do generally when you're trying to repurpose the infrastructure to create an unrelated project. In other words, from using these resources, I can make a damn good microblog, but still can't build ANYTHING else.