Help users with new project layout

Pulling this issue out from a seperate thread here… https://github.com/encode/starlette/pull/704#issuecomment-550247190

How do we best guide users around project layouts?

• starlette init.
• Pointers towards how to clone existing layouts.
• Something else?

[jugaadi]

For us, Starlette is the quintessential async web toolkit just like encode/databases. The fact that frameworks are being built over Starlette(like FastAPI, Responder, etc) proves it. I hope it becomes the Python equivalent of go-kit or spring boot.

So the question whether project layout falls under the scope of Starlette depends on the future path that the maintainers wish to take i.e toolkit vs framework approach. Whatever it is, I hope the decision is taken before v1.0

If its a framework, then it makes sense to dictate the project layout and other conventions. Else it is best left to the community to figure out the best way to utilize starlette for their usecase.

[alex-oleshkevich]

The Phoenix framework has a very good directory layout: https://github.com/phoenix-examples/hello_phoenix

It separates web application part (web dir) from the application (lib dir). Another directories like api, cli, etc may live next to web.