If I understand it right, you have multi-directory application with many scripts in them. If that is so, then every directory that your CGI application have will become Mojolicious::Controller, every script will become URL, and all logic will go to appropriate Controller.

If you have something like this in your application directory:

.. 
index.pl
dir1/somescript1
dir1/somescript2
dir2/somescript3
dir3/somescript4
[download]

then your Mojolicious application will have something like this inside:

script/app.pl
lib/App.pm
lib/App/Controller/Main.pm
lib/App/Controller/Dir1.pm
lib/App/Controller/Dir2.pm
templates/layouts/default.html.ep
templates/main/index.html.ep
[download]

script/app.pl:

#!perl

use strict;
use warnings;
use FindBin;
BEGIN { unshift @INC, "$FindBin::Bin/../lib" }
use Mojolicious::Commands;
Mojolicious::Commands->start_app('App');
[download]

lib/App.pm:

package App;
use Mojo::Base 'Mojolicious';

sub startup {
   my $self = shift;
   my $r = $self->routes;
   $r->get('/')->to('main#index');
   $r->get('/dir1/somescript1')->to('dir1#somescript1');
   $r->get('/dir1/somescript2')->to('dir1#somescript2');
   $r->get('/dir2/somescript3')->to('dir2#somescript3');
   $r->get('/dir2/somescript4')->to('dir2#somescript4');
}
1;
[download]

lib/App/Controller/Main.pm:

package App::Controller::Main;
use Mojo::Base 'Mojolicious::Controller';

sub index {
  my $self = shift;
  # will render templates/main/index.html.ep
  # logic from index.pl  
  $self->render();
}
1;
[download]

lib/App/Controller/Dir1.pm:

package App::Controller::Dir1;
use Mojo::Base 'Mojolicious::Controller';

sub somescript1 {
  my $self = shift;
  my $params = $self->req->params->to_hash;
  # logic from dir1/somescript1.pl
  # all HTML goes to templates/dir1/somescript1.html.ep
  $self->render();
}
# etc...
1;
[download]

Then you run it from root of your application like this:

perl script/app.pl
[download]

update: I thought that you might want to read the docs: Mojolicious Tutorial, Growing Guide

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.