Publishing to 4sightmagazine.com Using Dreamweaver MX - A Quick Tutorial

The following shows how to publish your web site to www.4sightmagazine.com using Dreamweaver MX.  The process for other versions of Dreamweaver should look about the same. 

Publishing using other software may be similar in principle, but the appearance of the process will vary.  If your HTML editor does not have publishing ability, I may need to help you set up your method of publishing on an individual basis.

After your index.htm web page has been made, you can copy it (publish) to the 4sightmagazine web site, along with other files.  Find and click on 'New Site'.  If you already tried to make a site that didn't work, click 'Edit Site', then pick the site you created.

Pick a name for your site connection.  Any text will do.

Select 'No' for server technology.  Our current web host supports .ASP, but we won't use it in this class.

Enter your local file location.

Make the following settings, substituting your username where 'username' is shown.  Then click 'Test Connection'.

If there is a connection, you should see this:

Check In / Check Out is used if there is more than one web author for a site.  We don't do that, so select 'No'.

Now get ready to publish your site. 

Click the 'Expand/Collapse' button (shown in white below).

Connect your computer to the remote web site.

Show all the files at both locations - remote on the left, local on the right.  NOTE:  FrontPage puts these in the opposite locations.  If you ever use both programs, beware!

Instead of 'Publishing', Dreamweaver uses the word PUT to copy files from your computer to the remote website.  It uses the word GET to copy files from the remote site to your computer.  You will rarely use the GET command, and if you are not careful, you will overwrite files on your computer that you just edited. 

There is more than one way to PUT files on your web site.  There are icons you can click.  Show below is where the file to be PUT is right clicked, then you click on PUT.  The file is then copied to the remote site.