Before you start

• Get an FTP software. There are free ones out there and 30 day trials. SmartFTP works well and can be used for non-commercial.
• Copy the website to OJUGBackup directory on your computer
• Create a OJUGWorking directory that mirrors only the files you want to change or need to test
• Create an OJUGUpload directory for the files to be uploaded

Making an Update

• On the OJUG website, copy existing file(s) to be changed and the revisions.html file to the Archive directory and rename them with the current date as a prefix.
  Eg, index.html would be copied to Archive directory as 2006-09-05index.html. Include the revisions.html file too. The files can be sorted to easily see which files were last changed for a recovery.
• Edit the revisions file and include the date, the file name, and what was changed. Include enough so that some else could follow and keep the same format.
• Change the date on the index.html file at the bottom. If this is the only change, it is not necessary to replace this file.
• Upload the files you want to be changed from your upload directory. As a result:
  1. The active files are ready for the public
  2. The last working files in the Archive folder.
  3. Revision.html file is changed
  4. The index.html file has the date.
• Test your changes to see if the site matches what you saw on your computer.
1. Test the html against the W3C validator
2. Test the css against the CSS 2.1 W3C validator
• Move the files from your upload directory, OJUGUpload to your original copied directory OJUGBackup. As a result:
1. This will leave the OJUGUpload directory empty, the OJUGBackup with a backup, and your OJUGWorking directory current!
2. Email the next speaker if a meeting is being changed and ask for feedback
3. Email Mike Levin with a link to the revision page