I’m in the process of implementing a white-label application with the help of this guide (I’ve diverge somewhat with respect to handling of subdomain routing).

I want to implement some sort of nesting for contexts to separate the business logic in the same way that multi-tenancy isolates the data.

I’d appreciate some tips here. I plant to implement the business logic isolation after the multi-tenancy is implemented.

I have already implemented a router per-subdomain approach for routing, so each subdomain is going to have custom layouts, core-components, controllers, views, and components.

What rules am I breaking so far (with respect to best practices)?

How important are those rules for security, performance and extensibility?

How can I address potential security concerns?

What surprises may I encounter when nesting the contexts so as to organise and isolate distinguish business logic?

I’ve seen the mix phx.new apps/<app_name> approach here.

Does the approach I’m using offer limitations and obstacles overcome by the above approach? (btw I’m not requesting that one read the entire guide linked above, however, I would appreciate perusal of the section that shows use of mix phx.new within an existing project)

Please let me know if clarity is required.