Mojolicious has its own templating language -ep- which is basically Perl itself.
I was also a big fan of Template Toolkit, and still use it on occasion. Yet I hardly ever use it for web templating anymore, because ep is so flexible. It is also nice to have one less dependency in the mix.
I highly recommend that you spec out the app as suggested, but would encourage you to favor building interfaces as collections of dynamically generated 'widgets' rather than monolithic pages. Having to work on a few such monstrosities I can tell you that the pain of 'just one change' becomes:
I won't even mention how bad it becomes when there are database changes as well.
Think of parts of your page as widgets (or boxes, cartons lol) whatever. Decompose the interface into many pieces that can be generated independently. Then the 'just one change' might actually be small enough to just require one of the steps above, and probably not the last one.
In reply to Re^2: Need generic advice on how to use modern perl for building webpage and which modules should be installed.
by Ravenhall
in thread Need generic advise on how to use modern perl for building webpage and which modules should be installed.
by Perl300
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |