This page contain the following:
The Site Definition is one of the most important aspects of how Dreamweaver functions. Once you have created a Site Definition, Dreamweaver knows
Because Dreamweaver remembers how everything within the Site Definition is linked together. And by "links", that means any tags that use the href or src attributes. That would include links to other Web pages, links to images, links to the CSS file, links to Flash or other embedded assets, and links to JavaScript files which include the Spry features that come with this version of Dreamweaver.
If you work outside a Site Definition, be prepared to have your links scrambled and not functional once they are uploaded to the server. Even though your links may test fine in preview, the links are likely just linking to files on your specific drive on your specific computer. Here's a perfect example of a bad relative link to a folder called spiffy:
<a href="file:///C|/Documents and Settings/HP_Administrator/Desktop/spiffy/">
When it says file:///C| that means a place on your C: drive on your home computer. When you upload the files, the links are still looking JUST AT YOUR SPECIFIC DRIVE ON YOUR SPECIFIC COMPUTER. They are not looking for the files you just uploaded to the server computer. In other words, when someone else on their own computer (like, ahem, your instructor!) goes to use your Web pages, some or all of the links will be broken and your Web pages will look and/or act like junk. This is the biggest disaster possible when using Dreamweaver.
If you create links in Dreamweaver, within a site definition (green folders), you'll get good links. Here's a perfect example of a good relative link to a folder called spiffy:
<a href="spiffy/">
Use the EXPORT/ IMPORT feature within Dreamweaver. It works like this:
In Week 1, we discussed the concept of Local vs. Remote Sites. As a reminder, a local site is where your site is stored "locally" - or on your hard drive or USB drive. A remote site is where your site resides out on the Internet - typically a web server. The local site and the remote site should always mirror each other.
When you set up your site in Dreamweaver, you are only required to define the local site folder (you do not have to set up a Remote Server for every site). If you work in Dreamweaver frequently, you will get very skilled at setting up a local site because you will be doing it a lot! In fact, in our class, you will be setting up many local sites throughout the course of term - basically, everytime you start a new assignment, you will be creating a new local site.
Instructor Note:
For CAS111d, you will have MANY local sites set up within Dreamweaver.
In the "real world", you would most likely be working on multiple sites for multiple clients who all use different web servers. In that case, you would have a separate site definition set up for each client with both Local Site and Remote Site information stored in the Site Definition.
In our class, we are going to set things up a bit differently since ALL of your assignments for the entire term are going to one location - the SWS.
You will be setting up multiple LOCAL site definitions - but only one of them will have the REMOTE server information. This is the Class Site Definition and this is the one that you will use whenever you are ready to upload files to the SWS. You will be creating this in CAL3-2.
Instructor Note:
For CAS111d, you will have ONE remote site set up within Dreamweaver.
If you always work on the same computer, you should only have to create the cas111d site ONE TIME! Every time you need to use it, simply select cas111d from the drop-down list in the Files Panel within Dreamweaver.
If you will be working on different computers or classroom computers for your assignments, you will not have access to the cas111d site definition on every computer. This is because the site definition information is stored on a computer's hard drive. Each time you need to access the cas111d site (when you need to upload your files), you will need to recreate the site following the instructions above. If you find this time consuming (it is!), you can also EXPORT the site definition which will allow you to put the site definition on your USB drive. Then when you sit down at a new computer, you can simply IMPORT the cas111d site and then it will show up in the Files Panel within Dreamweaver.
Back to the top of the page
To set up a new Site Definition, follow these steps: https://sws.pcc.edu/help/ftp/cs5.html
Instructor Note:
If you do not remove the path before /student, you will not be able to connect.
Always construct one Site Definition for one server.
Instructor Note:
Let me state that again: one Site Definition for one server.
You may have read in a textbook, online or heard from another instructor that you should create separate site definitions for each project or assignment. This makes sense for the purpose of learning how to set up a Site Definition, but it makes no sense for the purpose of being efficient and logical.
Nothing will create the potential for more file management chaos than creating multiple Site Definitions -- if you make one error regarding the Local Root Folder or Remote Folder, chaos will ensue. Instead, stick to the rule of one Site Defition per server and your life will be easier.
Since you'll be working with the Student Web Server, you should make just one Site Definition for all of your work in class for that server. In other words, have all your chapter folders, assignment folders, and test folders under one main folder for the class. I recommend calling the main folder cas111d. (Keep all your folder and file names lower case and use no spaces.)
The folder on your computer or USB drive is equivalent to the folder you have defined on the server, so when you upload your files from your computer/USB drive, they will go to the proper server folder.
For example, in the case of this class, your folder on your computer or USB drive should be named cas111d. Your folder on the SWS is your username folder, which is always your name followed by a number, like janedoe18. In this example then, cas111d = janedoe18, which means they are at an equivalent folder level and any files or folders you upload that are stored under cas111d will automatically go under janedoe18 on the SWS and create an equivalent file/folder structure. That's good file management!
After you have completed a Site Definition, you will see the folders in the Files panel turn green -- GREEN IS GOOD. Those folders are all of the ones under your Site folder which, in this example, is cas111d. Always work inside green folders. If you are working in yellow folders, you are working outside the Site Definition and probably destroying your links. YELLOW IS BAD.
Site cloaking enables you to exclude files and folders from operations such as Get or Put or Synchronizing. You can also cloak all files of a particular type (fla, psd, ste, and so on) from site operations.
Beginning with Week 3, you will be using the Site Management feature within Dreamweaver to upload your files and folders to the SWS. Each assignment contains instruction
Filezilla is an FTP program that allows you to transfer files and folders from one location to another. For our class, you will be transferring files from your USB or Hard drive to the SWS. You can also use Filezilla to perform File Management tasks, such as renaming, deleting, moving, etc.
You will be using Filezilla for Modules 1 and 2. Beginning with Module 3, you will be using Dreamweaver to upload files.
PCC provides support for Filezilla. Refer to their support page if you need help using Filezilla.
The most likely cause of problems uploading are typographical errors in the path, username, and/or passwords. Double, triple, or quadruple check these. You can also export the Site Definition (see Backup above) and send that .ste file to the instructor for a second opinion.
In some rare cases, most notably on Macintosh computers, students have commented that they are unable to upload files and there are no other errors with their Site Definitions. The most likely reason is that their Mac firewalls (part of the Mac OS) are blocking the connection. To fix this problem,