Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

vsn-mostafa's avatar

Your Laravel Project Structure Tips?

Hi folks, I'm starting a new Laravel project and wanted to know — how do you usually structure your projects beyond the default Laravel structure? For example:

Do you separate services into a directory?Services

How do you organize Jobs, Actions, or DTOs?

Would love to hear your opinions and what worked best for you.

0 likes
1 reply
martinbean's avatar

@vsn-mostafa I’ve worked on Laravel projects of all sizes—from start-ups to Fortune 500s—for over 10 years. The projects that always fall apart are the ones where some team or developer has decided the project is a special snowflake that needs its own, unique directory structure.

My advice is to stick closely to the framework’s defaults. I’ll then create an app/Services directory containing classes for encapsulating business logic and interacting with third-party services (for example, I work a lot with Mux, so I’ll have an App\Services\Mux namespace with Mux-related classes inside that directory).

Please or to participate in this conversation.