These pages contain documentation from users, for users. Become part of the project and contribute new documentation wherever you can. Don't forget to check out the official tutorial and guides if you haven't already - they may answer most of your questions!
You should also take a look at the wonderful Mojocasts, which, while dated, still contain a lot of valuable information. Just watch out for a few things that have changed since the screencasts have been produced.
$self->render(text => ...)
http://mojolicio.us/mojolicious-black.pnghas been moved to
$ua->post_form(...)has been replaced with the form generator
$ua->post(... => form => ...)
app->secret(...)has been replaced with
Mojolicious is database agnostic. You are free to choose the way you want to store your data.
Mojolicious has a built-in non-blocking I/O web server, supporting multiple event loops. If it appears that your app isn't performing well, it's probably because it's blocking somewhere, and this doesn't scale well -- or at all. For example, a single process daemon that blocks doesn't scale past supporting a single connection and a multi-process preforking server that blocks doesn't scale past n connections. But make your app not block, and a single process daemon will scale to thousands... imagine what a multi-process preforking server will scale to. Are you ready to redesign your app to be scalable?
There is documented support for Mojolicious for Atom, TextMate, Vim, Sublime Text 2, jEdit, Padre (The Perl IDE), Emacs Web Mode , and Perl::Tidy. And here is a tiny project for extending Exuberant Ctags support for Mojolicious.
If you are interested in helping out with the Mojolicious project, please take some time to review the contribution guidelines. You can submit bug reports, patches, and feature requests through the project's GitHub repository. If you are planning to contribute a new feature, it's a good idea to discuss it in the IRC channel before you start coding!