As mentioned previously, Phoenix is itself a full-featured Elixir application, and as a result, tends to follow a lot of the same conventions and rules that other Elixir applications follow. We’ve briefly touched on the topic previously, but now it's time to get into it and take a look at how Phoenix projects are structured so that we can understand how to build on top of Phoenix. The starting directory structure looks a little something like the following:
├── README.md├── assets│ ├── brunch-config.js│ ├── css│ ├── js│ ├── package.json│ ├── static│ └── vendor├── config│ ├── config.exs│ ├── dev.exs│ ├── prod.exs│ ├── prod.secret.exs│ └── test.exs├── lib│ ├── testapp│ ├── testapp.ex│ ├── testapp_web ...
