Setting up a build enviroment

Subdomains are one way to do it, for sure. Sub folders are another (easier?) way. You simply put projects in folders within your website. For example, my site www.gregkaleka.com has a folder tahoe-example, which you can only get to by typing it in. I can link people to www.gregkaleka.com/tahoe-example, and they'll see that page.

Here has been my experience. Usually the developing person(s) or company will have a server they can upload to. This is all pretty straight forward as you can point your client to the domain and they can see their website. You can also use a robots.txt file to keep legitimate search engines from indexing the site, which at this stage you would not what them doing that. Whether you use folders or subdomains kinda depends on the end result. Are you going to host the website for them too? Are you going to install the website onto a hosting account they already have or are going to purchase, or are you just going to turn the files over to them?

If you're planning to move the website from its developing server to a different server, than a subfolder would be okay I think. However, if you're also going to be hosting, it wouldn't work as well because you would still have to move it. If it is on a temp domain that is also a subdomain, than once it's ready to go live, you have the DNS servers for the domain pointed to that website, and soon enough the DNS servers will all propagate and direct incoming traffic to that site that was on a subdomain. No moving of the website necessary.

The latter part is what I've experienced most. Sites being built on temp sub domains and than DNS servers getting rerouted when you want it to go live.

You can also try a cloud development platform like Could9 or Nitrous.io that hosts your workspace in the cloud and allows you to share access with clients.

Rad! Thanks!