Layouts

A layout decides where each file type goes. You choose one in config/mod.php, and every mod:* command writes to its folders.

Choosing a Layout

Six layouts are built in. The table shows where each one writes a Document model for a Knowledge module:

config/mod.php

'layout' => 'modules',

Layout	Organizes code as	mod:model Knowledge:Document writes
laravel	Laravel's own folders	app/Models/Document.php (no Knowledge:)
modules	a modular monolith: one folder per module	app/Modules/Knowledge/Models/Document.php
features	feature folders	app/Features/Knowledge/Models/Document.php
slices	vertical slices: features, each split into slices	app/Knowledge/Models/Document.php
type-first	Laravel's folders, with an optional sub-folder	app/Models/Knowledge/Document.php
ddd	domain-driven design, as in laravel-ddd	src/Domain/Knowledge/Models/Document.php

The default, laravel, places files exactly like make:*. Changing the layout changes where new files go; existing files stay where they are.

Comparing the Layouts

Each tree is the result of php artisan mod:model Knowledge:Document --all in a fresh app:

modules

app/Modules/Knowledge/
├── Database/
│   ├── Factories/
│   │   └── DocumentFactory.php
│   ├── Migrations/
│   │   └── 2026_10_08_120000_create_documents_table.php
│   └── Seeders/
│       └── DocumentSeeder.php
├── Http/
│   ├── Controllers/
│   │   └── DocumentController.php
│   └── Requests/
│       ├── StoreDocumentRequest.php
│       └── UpdateDocumentRequest.php
├── Models/
│   └── Document.php
└── Policies/
    └── DocumentPolicy.php

features

app/Features/Knowledge/
├── Database/
│   ├── Factories/
│   │   └── DocumentFactory.php
│   ├── Migrations/
│   │   └── 2026_10_08_120000_create_documents_table.php
│   └── Seeders/
│       └── DocumentSeeder.php
├── Http/
│   ├── Controllers/
│   │   └── DocumentController.php
│   └── Requests/
│       ├── StoreDocumentRequest.php
│       └── UpdateDocumentRequest.php
├── Models/
│   └── Document.php
└── Policies/
    └── DocumentPolicy.php

type-first

app/
├── Http/
│   ├── Controllers/
│   │   └── Knowledge/
│   │       └── DocumentController.php
│   └── Requests/
│       └── Knowledge/
│           ├── StoreDocumentRequest.php
│           └── UpdateDocumentRequest.php
├── Models/
│   └── Knowledge/
│       └── Document.php
└── Policies/
    └── Knowledge/
        └── DocumentPolicy.php
database/
├── factories/
│   └── Knowledge/
│       └── DocumentFactory.php
├── migrations/
│   └── Knowledge/
│       └── 2026_10_08_120000_create_documents_table.php
└── seeders/
    └── Knowledge/
        └── DocumentSeeder.php

ddd

app/Modules/Knowledge/
├── Controllers/
│   └── DocumentController.php
└── Requests/
    ├── StoreDocumentRequest.php
    └── UpdateDocumentRequest.php
src/Domain/Knowledge/
├── Database/
│   ├── Factories/
│   │   └── DocumentFactory.php
│   ├── Migrations/
│   │   └── 2026_10_08_120000_create_documents_table.php
│   └── Seeders/
│       └── DocumentSeeder.php
├── Models/
│   └── Document.php
└── Policies/
    └── DocumentPolicy.php

Commands lists the folder of every command in every layout.

The Slices Layout

slices groups code by feature, then splits each feature into slices: one folder per operation, such as IndexDocument. A slice's classes have fixed names, so the folder says what the operation is and the file says what part of it you're looking at. The commands for them take no name:

php artisan mod:model Knowledge:Document -mf
php artisan mod:handler --in=Knowledge/IndexDocument
php artisan mod:request --in=Knowledge/IndexDocument
php artisan mod:message --in=Knowledge/IndexDocument

app/Knowledge/
├── Database/
│   ├── Factories/
│   │   └── DocumentFactory.php
│   └── Migrations/
│       └── 2026_10_08_120000_create_documents_table.php
├── IndexDocument/
│   ├── Command.php
│   ├── Handler.php
│   └── Http/
│       └── Requests/
│           └── Request.php
└── Models/
    └── Document.php

mod:handler, mod:message, mod:request, mod:query and mod:validator write a slice's classes. Models, events, jobs and the other shared classes sit in the feature's own folders.

The Type-first Layout

type-first keeps Laravel's folders and adds an optional sub-folder below each one:

php artisan mod:job Knowledge:ExtractText
# -> app/Jobs/Knowledge/ExtractText.php

php artisan mod:job ExtractText
# -> app/Jobs/ExtractText.php

The DDD Layout

The ddd layout uses laravel-ddd's folders, so a laravel-ddd application keeps its structure:

Namespace	Folder	Holds
Domain\	src/Domain	models, DTOs, value objects, view models, actions and the other domain classes
App\Modules\	app/Modules	controllers, requests and middleware
Tests\	tests	tests, in tests/Feature/<Domain>

Autoloading the Domain Namespace

src/Domain is outside app/. Run php artisan mod:autoload to add its namespace to Composer and reload the autoloader. It adds this entry:

composer.json

"autoload": {
    "psr-4": {
        "App\\": "app/",
        "Domain\\": "src/Domain/"
    }
}

php artisan mod:autoload

Generating Domain Classes

Each class belongs to a domain, given as Knowledge:, --domain=Knowledge or --in=Knowledge:

php artisan mod:dto Knowledge:DocumentData
# -> src/Domain/Shared/Data/DataTransferObject.php (created once)
# -> src/Domain/Knowledge/Data/DocumentData.php

php artisan mod:action Knowledge:IndexDocument
# -> src/Domain/Knowledge/Actions/IndexDocument.php

A domain can be nested: Knowledge.Search (or Knowledge/Search) writes to src/Domain/Knowledge/Search.

mod:dto, mod:value-object, mod:view-model and mod:action start from starter stubs, and use spatie/laravel-data, spatie/laravel-view-models or lorisleiva/laravel-actions when they're installed. Their base classes go in src/Domain/Shared, where laravel-ddd puts them. Stubs covers each one.

The preset declares no frontend folders, view namespaces or routes root. mod:mail --markdown and mod:notification --markdown keep their views in Laravel's resources/views, with unqualified view names. mod:page explains how to declare ->frontend() and stops.

Opting In to Frontend and Routes

To opt in, extend the layout and declare the paths you need:

use Tey\Mod\Facades\Mod;

Mod::layout('web-ddd')->extends('ddd')
    ->frontend(pages: 'app/Modules/{domain}/ui/js/pages', views: 'app/Modules/{domain}/ui/views', pageName: '{domain}::{path}')
    ->mounts('routes', null, 'app/Modules/{domain}/routes');

Select web-ddd in config/mod.php. Its views register domain namespaces, and its pages and routes use the declared folders. Case-only folder collisions are still checked.

Laravel-ddd Command Names

The DDD commands also answer to laravel-ddd's names:

Command	Aliases
mod:dto	mod:data, mod:data-transfer-object, mod:datatransferobject
mod:value-object	mod:value, mod:valueobject
mod:view-model	mod:viewmodel

Every hyphenated command also works without the dash, in every layout. In the modules layout, mod:dto answers to mod:data and mod:value-object to mod:value as well.

Customizing a Layout

Every built-in layout can be customized from a service provider. One line adds a file type and its mod:* command. in: is relative to the layout's root, app/ in modules:

app/Providers/AppServiceProvider.phpboot()

use Tey\Mod\Facades\Mod;

Mod::layout('modules')->generates('validator', in: 'Modules/{module}/Validators', suffix: 'Validator');

php artisan mod:validator Knowledge:Upload
# -> app/Modules/Knowledge/Validators/UploadValidator.php

Custom Layouts covers customizing, extending and defining layouts.

Custom generators adds commands from generator templates or PHP declarations.

Module Resources

HTTP classes live under Http/; frontend files and routes live beside them. A module can contain:

app/Modules/Inventory/
├── Http/
│   ├── Controllers/WidgetController.php
│   ├── Requests/StoreWidgetRequest.php
│   ├── Resources/WidgetResource.php      # API resources: no clash with resources/
│   └── Routing/InventoryRoutes.php       # optional registrar
├── Models/Widget.php
├── Policies/WidgetPolicy.php
├── Database/{Factories,Migrations,Seeders}/
├── resources/
│   ├── js/
│   │   ├── pages/Widget/Index.vue        # Inertia: Inventory::Widget/Index
│   │   └── components/WidgetCard.vue
│   ├── css/inventory.css
│   └── views/mail/widget-restocked.blade.php   # view('inventory::mail.widget-restocked')
└── routes/
    ├── web.php
    └── api.php

The lowercase resources/ root holds plain files and is excluded from PHP class discovery. Frontend Files and Module Routes show how to create them.

Moving Existing Code

Before changing an existing application’s layout or model namespaces, follow Moving an existing app. Record the old and new model identities, review persisted polymorphic values and drain work that serializes classes before deployment. For Inertia’s page finder and root Blade view, see Frontend files.