I often organize the web directory by feature as opposed to by type, but I strong prefer to draw a hard line between the domain and web layers. Contexts are not always 1-to-1 with web sections.

In elixir apps the module names define structure, not the path, so you can already do something like this in phoenix anyway?

foo/
foo_web/
├─ feature_1/
│  ├─ components/
│  ├─ liveviews/

maybe I’m completely misunderstanding your question.

I’m finding it very hard to write a succinct answer to this, lol, as it can get really into the weeds with certain designs. I do mean Phoenix, though, yes.

I believe here we’re talking about also including the domain layer, so the structure would really be:

foo/
├─ feature_1/
│  ├─ components/
│  ├─ liveviews/
│  ├─ context.ex

BUT, maybe I’m misunderstanding but I don’t think so?

Otherwise, @AstonJ a quick example is that I have a client app which is for managing a catalogue of artwork for a visual artist. The app has several LiveViews but there are two that both deal with listing artwork, one for the artist to manage her catalogue (this one is super complex with different views and tons of info) and one client facing that simply lists out all the artwork and allows them to requests licenses for them.

This is where I don’t want to get too much into the weeds because I could totally have two contexts here (with different schemas), one that lists artworks in the context of the artist herself looking at them, and one for clients to browser. I made the intentional decision to forgo this and simply have a flag on an artwork which says whether it can be shown for licensing or not. SOOOO, the Catalog context gets used in both the artwork management feature, and the “license requesting” feature. It’s a bit simpler but does mean I have to deal with ensuring some fields can’t be shown to my client’s clients.

Otherwise, I like to have that firm line between domain and web because I want the domain layer to be able to operate entirely on its own. The web layer is simply a client, IEx is another. But maybe I just need to see a really good example of vertical.