About the CC HTML Editor Online Tutorial, "Working with Website Projects"
To my mind, this very good and useful tutorial could be made great by adding a few things.
1) Please explain the internal structure and keywords of a .cpf file. I could perhaps reverse-engineer the thing through experiments, but why risk misunderstanding when Coffee Cup could just explain it?
2) It appears that registering an existing collection of Web site files as a CC Editor Project does not modify those files. It appears that all that happens is that a .cpf file is created within the Project's root folder in order to describe the project.
If that is true, then there is no risk in trying out the Project facility. Simply delete the .cpf file if you don't like the way the Project facility works.
But is that indeed true? Are there no other side effects, such as key/value pairs created in the Windows registry that are vulnerable to becoming orphans?
3) Please explain what happens when one deletes a Project.
4) Please explain the rules of Projects. For example, it appears that one and only one .cpf file, located at the root of a Project, controls that ensemble of files identically. One Project cannot overlap another, for example by perhaps sharing the same CSS files. Nor can any file within a Project's root or child directory be excluded from that Project.
But suppose I would like for three Projects to use the same baseline CSS, so that I don't have to manually synchronize copies B and C with changes I make in copy A. Could I use symbolic links (i.e., .lnk references) from Projects B and C to the CSS in A, or would that screw up the Projects?
Conclusion:
Projects look great. I'd like to try the idea, but I don't want to get stuck. The tutorial could explain the rules, and so better assure me of success.
halfnium -AT- alum.mit.edu
Yes, I looked just like that in 1962.