On occasion, I have visitors ask me if it is possible to completely design a new website using Dreamweaver, without touching their existing functional site, and only publish (upload) the new site when everything in the new site is completed. This tutorial shows you how it is done.
The reason for this question is that both my main Dreamweaver CS4 tutorial and the earlier Dreamweaver CS3 tutorial guide the newcomer to publish their site at a very early stage. While this is acceptable (and in fact desirable) for a brand new website, it is not practical for people who already have a functional website. The latter usually want their existing website to continue to work, while designing the new one, and only upload everything when the redesign is complete.
IMPORTANT: If you do not have an existing site, this tutorial is NOT for you. Please follow the procedure given in the main Dreamweaver CS4 tutorial instead. (In fact, if you are completely new, you should really start by going through the How to Make / Create a Website: The Beginner's A-Z Guide first, to avoid confusion.)
The main tutorial series is designed for the newcomer in mind. The order in which things are set is the result of many years of teaching webmasters-to-be, and is designed not just to help you get your website up and running as soon as possible, but also to teach new things in a context that helps the learning process and provide the foundation for stuff that is taught in the later chapters. It is also designed with the unstated objective of building your confidence and competence as a webmaster, and exposing you to things that you will need to understand to better appreciate (and more efficiently deal with) what you will do later.
What I'm trying to say is that it's best to only use the shortcut in this article if you really have an existing website that needs to continue functioning while you develop a new design. Otherwise, you'll be doing yourself a disservice.
It's possible to actually design your website and complete all the pages before even publishing a single page when using Dreamweaver.
The following sections tell you what to skip (or more accurately, to defer to later) in the main Dreamweaver CS4 and CS3 tutorials. Note that you will still need to use the Dreamweaver CS4 or CS3 tutorials as a guide.
Follow the steps in that section to set up the Site Manager for FTP access until you complete the part where you click the "Done" button to dismiss the "Manage Sites" dialog box. Then stop. That is, skip only the step that tells you to use "Site | Put".
Let me put it another way (so that there is no misunderstanding): complete chapter 1 in entirety except the step telling you to invoke the "Site | Put" menu. The "Site | Put" step is the part that tells Dreamweaver to transfer your web page from your computer to the Internet. And, of course, since you didn't click "Site | Put", the section entitled "Testing Your Web Page" will be irrelevant, since your web page will not be on the Internet for you to test.
Do the same for chapters 2 to 6. That is, ignore any steps that tell you to publish the page or use "Site | Put".
In chapter 7, we learn to use Dreamweaver's site management facilities to handle the publication of your website for you (instead of manually publishing your page as you did earlier). Instructions for how this is accomplished is given in the section entitled "How to Publish Multiple Pages the Easy Way with Dreamweaver CS4" (click the link to locate the section, if you need to).
Skip that section (for now). Also skip any part of the tutorial that tells you to use "Site | Synchronize" to publish your website.
Skip the section that tells you to publish your web page using "Site | Synchronize". You will also not be able to test your feedback form since you have not published it to your website.
After you've completed designing and adding pages/content to your website, go back to chapter 7. Read and follow the instructions in the "How to Publish Multiple Pages the Easy Way with Dreamweaver CS4" section. This will cause Dreamweaver to upload all the pages on your website in one fell swoop.
You will then need to thoroughly check out every page on your website. Pay special attention to the feedback form page taught in chapter 8 and follow the instructions for testing it in that chapter. If you have problems with the form, return to chapter 8 and redo the steps again. Now that you have a "live" site to actually test the feedback form, it'll be easier to spot problems and fix them.
Follow all the steps in chapter one, except the step that tells you to use "Site | Put" to publish your website. Since you're skipping this step, you will not be able to complete the section entitled "Testing the Web Page" either (you'll have nothing to test since you didn't publish anything).
Complete these chapters normally, skipping only the part of the tutorial that tells you to use "Site | Put" to publish your website.
Follow the instructions in chapter 5 except the section "Publishing the Nearly Complete Website" and any part of the tutorial that tells you to use "Site | Synchronize Sitewide".
As before, follow the instructions and only skip the step telling you to upload your pages using "Site | Synchronize Sitewide". Since you've not uploaded anything to your website, you will also (obviously) not be able to test to make sure that your feedback form works.
Once you've finished designing all the pages on your website, and are ready to publish them, return to chapter 5. Read and follow the instructions in the "Publishing the Nearly Complete Website" section. Then test your website, making sure that you also test the Feedback Form (by sending yourself a message or two). If the Feedback Form fails to work, return to chapter 6 and redo the instructions there. Now that your site is "live", it'll be much easier to test and fix problems with your feedback form.
While you are designing your website, it is good from time to time to make sure that it looks the way you want it to look in a web browser. Dreamweaver is a web editor, not a browser, so just because your site looks good in it does not necessarily mean that it will appear the same way in a real browser.
Since you are deferring the publication of your website till the end, you won't be able to do any of the testing described in the main tutorials. However, it is still possible to do limited testing by pointing your web browser to the copy of your website saved on your computer.
To do that, open your web browser, and type into the address bar the full path to the file you want to check. For example, if your Dreamweaver website files are saved in "c:\Users\chris\Desktop\mysite", and you want to check your "index.html" page, type "c:\Users\chris\Desktop\mysite\index.html" (without the quotes) into your browser's address bar.
Note that some things will not behave the same way offline. For example, Internet Explorer may issue a warning about scripts on your web page when you test it offline. If you referred to an image or some other resource on your website using an absolute URL instead of a relative one (absolute and relative URLs are explained in chapter 5 of the Dreamweaver tutorial), the image or resource may not show (since you have not uploaded that image/resource to your site yet).
In addition, it will not be possible to test the feedback form at all. The latter can only be tested when it is on a real web host, since the program used to process the form needs to run on a web server. As such, if you have modified the supplied form, you won't know whether your modifications have broken anything until you've actually published your site and tested it.
A word of caution: offline testing cannot replace "live" testing. Just because your site looks fine when tested in this way does not mean that it will look correct when published. There are some problems that you will not be able to detect when you test offline, even visual ones like images and files that are wrongly linked but still appearing correct on your own computer. You must test your site thoroughly when you finally publish the site.
Let me reiterate that I don't recommend that you take this approach of deferring certain steps till later. For the newcomer, it may introduce too many problems that compound to create a situation they don't know how to fix. Under normal circumstances, if you make a mistake in the chapter and don't know how to solve it, all you need to do is to redo the chapter. However, if you follow this guide and skip the crucial uploading and testing steps in each chapter, you won't know about your mistakes until you have finished the entire tutorial. And then what are you going to do? Redo everything?
If you don't actually have a working website to worry about, and your only reason for not wanting to publish your website from the very start is vanity, let me say that doing the above can hamper your progress and cause you to face unnecessary headaches. Remember that I have no ulterior motive for wanting you to follow either the main (systematic) tutorial, or the skip-about one I wrote here. I gain nothing by your use of either set of instructions, not even the abstract satisfaction of having someone learn from my articles. After all, I wrote both sets.
I'm saying this because I know how newcomers think. They are worried about an unpolished website being published. But as I said elsewhere, if you are only just starting out, your site will have no visitors except you and any hapless victim you forcibly drag to your computer to show off to. So you really don't have to worry that someone will see your work in progress. Besides, everyone starts somewhere. There is no shame in being a beginner.
Do you find this article useful? You can learn of new articles and scripts that are published on thesitewizard.com by subscribing to the RSS feed. Simply point your RSS feed reader or a browser that supports RSS feeds at http://www.thesitewizard.com/thesitewizard.xml. You can read more about how to subscribe to RSS site feeds from my RSS FAQ.
This article is copyrighted. Please do not reproduce this article in whole or part, in any form, without obtaining my written permission.
It will appear on your page as: