If you want the right framework for your productivity, choose the one that uses the language you have most experience with.
If you want the one that is fastest, re-evaluate your choices, none of these are "fast".
If you want the one that gives you the most maintainable code, I think that might be Django, but highly dependent on the first point, and I'm biased on this.
If you want the one where the code looks nicest, go for Rails, it's again subjective, but Ruby code is often very pretty (debatable whether thats useful).
If you want the one that is easiest to deploy, go for Laravel, you can stick a bunch of files in a webroot on shared hosting and it might work.
I don't prefer any one of these, each is better for different people, teams, requirements and restrictions, but none of these is a clear winner.
It's also very easy to take in any developer and have them learn ruby. Rails is a bit more strict but if there's a "mentor" available I'd say it's a quick process to get new devs up and running.
About the mentor.. I think Jeffrey Way is the only mentor you need when you're developing with Laravel :D
Your ideal way of doing things as in MVC structure or what do you mean exactly?
Just kidding, rewrite everything in Go.
Something like twig maybe?
I come from rails and trying to develop for Wordpress caused a lot of wtf and disgust.
You will need to write absolute minimum for your templates using standard PHP. Here is a link to their latest beta version which uses webpack and all the new goodies: https://github.com/roots/sage
However, if you're more comfortable with using Twig, there is a fork of Sage that uses Twig: https://github.com/studiorabota/sage-twig-theme (but it uses gulp and older tech).
It's easy to learn, there are lots of good resources, and it's growing in popularity.
Ruby tries to force you to do things in a certain way, and quite often people just end up programming their way around the framework instead of using it the way it was intended. This is probably true for any framework, but anecdotally I see this happen more in ruby.
I think the big factors are where your skills lie, and whether or not you are going to have other people working on the project. If you are, I would choose Laravel, as it's much easier to find php developers than it is to find ruby developers and even the php developers that don't know Laravel can usually pick it up quickly.
Again, this is just my own experience.
Django doesn't force you to do things it's own way but when you do go for the Django way everything else is so much easier. Class Based Views, for example are a bit difficult at first, but once you get the hang of them its fast to produce nice maintainable code.
The very first time I watched into to Laravel (version 4 I think) on Laracasts I understood everything.
Watching Ruby on Rails videos... I had mixed feelings, wanting to stop as soon as I started. Don't know why.
I like both, I prefer Laravel.
Great community, easy to reach out and connect with people.
I like the frequent releases, always great new features coming out.
Amazing packages.
LaravelShift.com is a great tool to updating repos to the next release.
Deployment is a breeze with forge and envoyer.
It's fun to develop in.
Laravel is great, and I find PHP a lot prettier and easier than Ruby. Just wondering why all the big start ups are using Ruby on Rails? Twitter, AirBnB, BrainTree, Shopify. Literally no big startup uses Laravel, other than Slack, which is just PHP.