Also Rails has a much more mature community with screen casts and blog posts being produced constantly. That is probably difficult to 'create' short of DHH style evangelism.
Also Rails has a much more mature community with screen casts and blog posts being produced constantly. That is probably difficult to 'create' short of DHH style evangelism.
As Florian touches on, Padrino is fundamentally about embracing the power of modularity. Understanding Rack, Rack Middleware, Sinatra, Padrino and a suite of chosen tools does ultimately become necessary. However, like Sinatra you can also learn the basics within 15 minutes. I like to think that Sinatra/Padrino can grow with you as you need it.
If anyone reading this has any interest in helping us with documentation, please let us know. Especially if you are a beginner. We are a very open community and would love some help or even suggestions on how to make our framework more inviting.
On my Padrino stack, I usually have to switch between roughly 20 documentation stacks (Padrino, Sinatra, Rack, DataMapper, Warden, 2-3 template languages and a lot of other Rack Middleware), so "one more" doesn't really matter to me.
Maybe some documentation on how to work with or to learn Padrino would be wise. Well, more work for us. :)