Ok, my other doubts are:

protected $moduleName = 'projects'; - I created a new project, is it anyway that this can be loaded from database

so I maintain modules table... name, route_path, is_enabled, etc... then I can dynamically load in the controller... and pass it on to the views...

Because then I can enable a specific module for specific sites; Secondly, If I add project_types controller or categories controller... do I have to use [ php artisan twill:module categories] - I want to package all controllers related to projects as one package...

On the frontend (ie. the public pages of your site), you can simply query your models as in standard Laravel, eg.

Project::where(['priority' => 1])->get()

etc.

Okay

Yeah, my preference is to lean on modules a lot and "model" my solutions around multiple modules. I would totally go for "projects" and "categories" as modules.

I created the projects - but it is not showing on the Admin Menu

so I added this in twill-navigation => 'projects' => [ 'title' => 'Projects', 'module' => true, ],

Route::module('projects'); - in admin.php

Looks good, still not working? Also, did you run your migrations?

and created index.blade.php under views/admin folder

Shouldn't be necessary for now

Ooops.. I forgot to run migrate... did now

But still got this error: Symfony\Component\Routing\Exception\RouteNotFoundException Route [admin.projects.index] not defined.

double-check your

routes/admin.php

... eg. did you save it?

This is admin.php

<?php use Illuminate\Support\Facades\Route; // Register Twill routes here eg. // Route::module('posts'); Route::module('projects');

Strange... what if you

dd

something from this file, eg.

dd("HELLO");
Route::module('projects');

Do you see the message when you refresh?

No i don't see any message

What is the full path to this

admin.php

file you are editing?

But if I remove the code from twill-navigation, then it is okay

This is from twill-navigation.php

<?php return [ 'projects' => [ 'title' => 'Projects', 'module' => true, ], ];

routes/admin.php - this is the full path

Hmmmmm. Are you using

'support_subdomain_admin_routing' => true,

?

where is this ... in .env file?

http://townhouse.test:8080/admin - my admin url is not sub-domain based...

This would be in your

config/twill.php

. Sorry, let's scratch this one, I thought you wanted to setup multiple subdomains.

config/twill.php is blank now