Here, I am assuming the following scenario: You are out there somewhere on planet Earth with an Internet connection to SEUL server. You would like to contribute some content (such as HTML/CSS) files, the effects of which can be seen on the Website by everyone.
SEUL uses CVS to track all files revisions. So you will need to be passingly familiar with basic Linux shell commands and CVS. Refer to the resources at the end of this document to learn about BASH, SSH and CVS. Ofcourse, if you are contributing webpages, you will need to have an understanding of HTML too.
Here's how to go about it:
How do you locate the file you need? You can use 'find' command as follows:
find . -exec grep -i "your_text_here" {} \; -print
or if you know the filename but not where you put it:
find . -name file_name.ext -print
This command, with "your_text_here" being a phrase that you want to look for inside each file, will list each file that has that phrase, plus the other text on that line. But it's not perfect, because it won't find it when your phrase is split up into two lines, etc. The -i (for grep) means a case insensitive search.
For instance, there's a lot of sdoc material in /pub/website/html/ in the repository. For the most part, you can guess where it should live in the repository, based on where you found it on the website. In particular, read the getting started file
Now, sdoc was a good idea, somewhere along the line. I don't think it's such a great idea currently. This means that if you want to do a webpage for
seul, you either
* make use of sdoc, use .sdoc as the suffix for your file, and cvs will handle it for you
* use .html as your suffix, and sdoc never enters the picture.
Why sdoc? : somebody else can decide what looks good, and even if they change their mind later as to how
CVS Information:
Secure Shell (SSH) Information: