CUCC Expedition Handbook
Updating the website - HOWTO
Please refer to the latest web updating guide in CUCC website
Expo data is kept in a number of different locations.
- Loser
- Contains the survex data. Mercurial repository ssh://expo@seagrass.goatchurch.org.uk/loser
- Expoweb
- Contains the current website. Mercurial repository ssh://expo@seagrass.goatchurch.org.uk/expoweb
- Tunnel data
- Contains the tunnel data. Mercurial repository ssh://expo@seagrass.goatchurch.org.uk/tunneldata
- Troggle
- Contains the unfinished Django based website. Mercurial repository https://goatchurch@troggle.googlecode.com/hg/ troggle
- Scanned notes
- Scans of survey notes and drawn up surveys. Can be got via rsync.
Mercurial is a distributed revision control system. On expo this means that
many people can edit and merge their changes with each other either when they can access
the internet. Mercurial is over the top for scanned survey notes, which do not get modified, so
they are kept as a plain directory of files.
If you run windows, you are recommended to install
Tortoise Hg, which nicely interfaces with
windows explorer.
Get the repositories
Mercurial
Linux
hg clone RepositoryURL
Windows
InstallTortoise Hg.
In windows explorer right click, select Tortoise Hg .. and click Clone repository.
Set the source path to RepositoryURL
Set the destination to somewhere on your local harddisk.
Press clone.
RSync
Linux
rsync -av expoimages expo@seagrass.goatchurch.org.uk:
Windows
Not sure yet
The website conventions bit
This is likely to change with structural change to the site, with style
changes which we expect to implement and with the method by which the
info is actually stored and served up.
... and it's not written yet, either :-)
- Structure
- Info for each cave – automatically generated by make-indxal4.pl
- Contents lists & relative links for multi-article publications like
journals. Complicated by expo articles being in a separate hierarchy.
- Translations
- Other people's work - the noinfo hierarchy.
- Style guide for writing cave descriptions: correct use of boldface
(once for each passage name, at the primary definition thereof; other
uses of the name should be links to this, and certainly should not be bold.)