reinink/classes.md

Created April 11, 2016 10:11

Star () You must be signed in to star a gist
Fork () You must be signed in to fork a gist

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/reinink/504a9654c4348dbc0dc81ff4313fb588.js"></script>
Save reinink/504a9654c4348dbc0dc81ff4313fb588 to your computer and use it in GitHub Desktop.

Download ZIP

How do you typically organize your classes?

Raw

classes.md

By type

/Controllers
/Events
/Models

By topic

/Comments
/Posts
/Users

By topic, then type

/Comments
- /Controllers
- /Events
- /Models
/Posts
- /Controllers
- /Events
- /Models
/Users
- /Controllers
- /Events
- /Models

Mixed

/Comments
/Controllers
/Events
/Models
/Posts
/Users

aminemat commented Apr 11, 2016

By topic (sub-domain), entities in the sub-domain root folder, then by type
example with 2 topics, Shifts and Employees:

frankdejonge commented Apr 11, 2016

@shochdoerfer I'm still toying with the 1 dir 2 dirs X dirs setup. One thing I don't like is to have to group the domain in an arbitrary namespace. I often see the Web/Http namespacing, but then it comes with a "Domain" namespace too which pretty much always puts me off.

stefanbauer commented Apr 4, 2020

Even this is a really, really old gist, I'd still just wanted to share my thoughts on it, which I wrote a blog post about it: https://stefanbauer.me/articles/an-alternative-way-to-organize-the-laravel-directory-structure - I think it's basically what @frankdejonge is doing. Do it for several years now and still happy with it – at least if we're talking about larger projects.