Making every mention of troggle link to the description of what it is

handbook/manual.html

@@ -62,7 +62,7 @@ expo.survex.com. This is currently hosted on a server at the university. We use
 
 <ul>
  <li><a href="http://expo.survex.com/repositories/home/expo/expoweb/graph">expoweb</a> - the data management system itself, including generation scripts</li>
- <li><a href="http://expo.survex.com/repositories/home/expo/troggle/graph/">troggle</a> - the database-driven part of the data management system</li>
+ <li><a href="http://expo.survex.com/repositories/home/expo/troggle/graph/">troggle</a> - the database-driven part of the data management system - see <a href="troggle-ish.html">notes on troggle</a> for further explanation</li>
  <li><a href="http://expo.survex.com/repositories/home/expo/loser/graph/">loser</a> - the survex survey data</li>
  <li><a href="http://expo.survex.com/repositories/home/expo/tunneldata/graph/">tunneldata</a> - the tunnel (and therion) data and drawings</li>
 </ul>

handbook/survey/newcave.html

@@ -238,7 +238,7 @@ mentioned, or when they are "defined".</p>
 
 <p>
 You will type this description, and pass it on to someone more nerdy who
-will file it in the right place. This will involve "creating a new cave" using the troggle system.
+will file it in the right place. This will involve "creating a new cave" using the <a href="../troggle-ish.html">troggle</a> system.
 <p><em>to be documented</em>
 
 

handbook/troggle-ish.html

@@ -20,7 +20,7 @@ Most people will not want to read this at all. This is for speleosoftwarearcheol
 <p>
 Troggle is the software collection (not really a "package") based on <a href="https://www.djangoproject.com/">Django</a>  
 originally intended to manage all expo data in a logical and accessible way 
-and publish it on the web.
+and publish it on the web. It was first used on the 2009 expo - see <a href="../years/2009/report.html">2009 logbook</a>.
 <p>Only a small part of troggle's original plan was fully implemented and deployed. 
 Many of the things it was intended to replace are still operating as a motley collection written by many different people in
 several languages (but mostly perl and python; we won't talk about the person who likes to use OCamL).
@@ -322,9 +322,6 @@ Storage:
  convert small 800x600 version into website by default. (matching structure?
 </pre>
 
-
-<h3>Footnote</h3>
-Copy this link into all pages mentioning troggle: <a href="../troggle-ish.html">troggle description</a>.
 <hr />
 
 <ul id="links">

years/1992/log.htm

@@ -15,14 +15,17 @@ get in. The winter snow fall had not fully melted and the entrance appeared
 snow plug. There was the possibility of gaining entrance down the side of
 the snow just to the left of the cave number. So we placed a Hilti and
 dropped down a ladder. This provided a way into the main hole. Some digging
-provided a route into the passageway into the cave. Since last year it
+provided a route into the passageway into the cave. 
+<p>Since last year it
 appears that the roof has fallen in and there is a new hole in the roof
 &lt;-- Bollocks ! Look at the survey fellas... The boulder choke is very
-loose and should be descended with caution. Once we arrived at Shell Pitch,
+loose and should be descended with caution. 
+<p>Once we arrived at Shell Pitch,
 Julian and Matt went ahead to start rigging Piezo. Mark and I began to
 re-rig Shell Pitch but due to a slight misjudgement we only had one hammer
 with us and were unable to dress the rock properly. This will be re-rigged
-next time we go down, hopefully. On the traverse to Piezo there is a move
+next time we go down, hopefully. 
+<p>On the traverse to Piezo there is a move
 over a deep hole which should be hand lined and possibly explored. Julian
 had rigged the first part of Piezo too a long free hang. We descended this
 but found that rigging the next pitch would be difficult avoid what could be
@@ -31,7 +34,8 @@ side is overhanging and should make an excellent place to rig, but
 unfortunately it is virtually impossible to reach, let alone to drill a
 hole. After some looking we spotted a good ish rigging point, again it was
 somewhat difficult to reach as a traverse out was required and then the rope
-just pulled you straight back. Matt at this point was feeling very cold and
+just pulled you straight back. 
+<p>Matt at this point was feeling very cold and
 decided to leave the cave. We then started rigging a descending traverse
 from the top of the pitch to reach this point. After 3 bolts we were tired
 and decided to come out. We're not far from reaching the good rigging side -
@@ -823,7 +827,7 @@ ticked off 2 QM's !
 
 <p>[and don't write up their trip at all, even 
 though Mike remembered it in 2009 when it wasn't
-parsed into the troggle database]
+parsed into the <a href="../../handbook/troggle-ish.html">troggle</a> database]
 
 <p> T/U 11 hours
 

years/2009/jobs.html

@@ -65,7 +65,7 @@
 	    <tr>
             <th rowspan="2" scope="row">Aaron Curtis </th>
             <td rowspan="2">Chief Troggle-odyte </td>
-            <td>Responsible for the development of Troggle</td>
+            <td>Responsible for the development of <a href="../../handbook/troggle-ish.html">Troggle</a></td>
           </tr>
 	  <tr>
 	    <tr>

years/2009/report.html

@@ -59,7 +59,7 @@ and its southern extremities were tantalisingly close to the north of
 
 <p>This year's expedition also had a non-caving goal (not just
 drinking G&ouml;sser). Recently members of CUCC have started to
-develop a piece of software called Troggle, which aims to facilitate
+develop a piece of software called <a href="../../handbook/troggle-ish.html">Troggle</a>, which aims to facilitate
 keeping track of logbook entries, typing up surveys, caves etc, and save time in a lot of the
 work that goes on behind the scenes when expo is over. This year was
 the first time Troggle would be tested "in th field" (well, spud hut).</p>