Choosing the right subdomain name

A subdomain is a small thing that's surprisingly easy to get wrong. A few guidelines that hold up well in practice:

Keep it short. Something you could read aloud once and remember is worth more than something descriptive but long.

Avoid dates, version numbers, or "temp" in the name — projects tend to outlive the label you gave them on day one.

If the project has a name, use it. Consistency between your project name and its subdomain makes it easier for people to find and trust.

And if you outgrow a subdomain later, that's fine — a project's settings page is where you can eventually point a custom domain at it instead.