When you deploy a small project the zero-config way (e.g. Python serverless functions in /api plus a static page), Vercel effectively expects vercel.json, /api, /public, requirements.txt and the runtime modules at the repository root. On GitHub, that pushes the README down under a long list of runtime files, which hurts readability when the repo itself is a public artifact — in my case a hackathon submission that judges read on GitHub.

A Root Directory setting exists, but it is presented as a monorepo feature and is easy to miss for a single small app. Request: make the subdirectory layout an explicit, discoverable choice at project import time ("Where is your app located?"), and document the plain Python/static case for it.