Just set up a private area on your web server so that you can show them. There is nothing you can do locally without giving the client the IP address of your local machine. This way they can see the site in a testing environment before it goes live.
Upload your client site to a TEST folder on their web server or yours.
If you don't have a web space yet, you should get one for previewing and debugging sites before they go live.
Putting the test site onto the client's server sounds best, but so as to not make a mistake, how exactly is this done? I notice in Dreamweaver (CS5) there is a dropdown menu to choose from:
- Local view
- Remote server
- Testing server
- Repository viewer
Do these have anything to do with it?
If I "put" the test website onto the client's ftp, how does it go into a "test" sub folder?
Sorry for coming with such basic questions, but this is for a nonprofit organization and I'm on board because of my graphic design experience ... hence, I was the most qualified to take on the website changes. I'm so close to being done, hope you can help me out.
Thanks a bunch,
Your original post mentioned:
I downloaded all of their website files via an FTP
This indicates that web space is present, so the other poster mentioning IF there's webspace has already been clearly addressed. You managed to download the files via an FTP. Simply reverse the process and choose to upload the new, test website to a test directory. I would use a dedicated FTP application for this process or simply set the root directory of your site definition in DW to the present TEST directory on the server.
We have a test domain set-up and have it as an addon domain to our business domain for testing purposes only like...mytestsite.com. We then add subdomains to it with the client's name,,,client,mytestsite,com so they can look at it and test it themselves and tell us what to do next. We also test their sites on it and when we have their site completed we then give them the link to it. If they approve it then we upload to their hosting company but keep the subdomain on our sever if and when the client wants changes. We can then make the changes on the subweb. test and tell the cleint to check it out.
Sites > Manage Sites > Edit >
Advanced > Remote Info Host Directory: public_html/TEST/
where public_html = the folder your web host has set-up as your site's root folder. This varies by hosting provider. If your host doesn't use a public_html/ folder, you can omit this and simply use TEST/
Hope this makes sense,