documentation: what does it do, and what not?

[henzeb]

I have been looking at this documentation for a while now, but I am still not sure what it does, and what it fixes. 'domain' is usually used for 'example.com', 'api.example.com', so I expected it to be some sort of Tenancy (https://tenancyforlaravel.com/) like package. But it looks more like something that gives you (more) control on what file to store where and what to execute.

Could you explain a bit more in the documentation on what problem it should solve?

[allysonsilva]

Hi, thanks for asking, so here goes:

• Added a new "Concepts" section, to explain the terms of "Domain" and "Contexts".
• I believe you don't know some of the concepts of DDD, and that's why it caused you this confusion, more basically, what I'm trying to do is simplify the project organization, dividing the different "groups" of the business in the application, and in this division of folders/architecture, the question remains: "How do I perform migrations for a certain group/context?" or "How do I execute or create the seeders only in a certain context/folder?", in this case, this package proposes to answer these questions taking into account the "Custom" structure of the application.
• To create a structure based on business interests in the application, I recommend seeing the following article and see also