From 7223a746bf688433e43df94329e2c47868bc77ce Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@klebos.com>
Date: Tue, 26 May 2020 00:26:14 +0100
Subject: [PATCH] cave and entrance template files links in handbook

---
 handbook/survey/caveentryfields.html |  8 ++++++++
 handbook/survey/newcavefile.html     | 11 ++++++++++-
 handbook/troggle/trogstatus.html     |  2 +-
 3 files changed, 19 insertions(+), 2 deletions(-)

diff --git a/handbook/survey/caveentryfields.html b/handbook/survey/caveentryfields.html
index 24e00fdca..ca12e5f9f 100644
--- a/handbook/survey/caveentryfields.html
+++ b/handbook/survey/caveentryfields.html
@@ -16,6 +16,14 @@
     caves and entrances, and especially how to add images/surveys so that they appear properly,
     is to be found on the sequence of pages <a href="caveentry.html">starting here</a>.
   </p>
+  <p>
+    There are template files for you to fill-in when creating new caves and entrance in the online system. Download them:
+    <ul>
+    <li><a download href="../../templates/cave_data.html">cave_data template</a>
+    <li><a download href="../../templates/entrance_data.html">entrance_data template</a>
+    </ul>
+    These are actually XML files, not HTML files, using special tags which are used by the online system to create the webpages in combination with numerical survey data. Instructions are within each file.
+  </p>
 
 <h2>List of New Cave/Cave_data fields</h2>
   <dl>
diff --git a/handbook/survey/newcavefile.html b/handbook/survey/newcavefile.html
index 2c1af0b42..571695665 100644
--- a/handbook/survey/newcavefile.html
+++ b/handbook/survey/newcavefile.html
@@ -69,7 +69,16 @@ the form and the file format however.
 <p>If  instead of using the form you create the file by hand and upload it to the server you will also need find a nerd to run the cave import procedure before troggle "knows" that the cave exists.
 <h3>Cave entrances</h3>
 <p>There is <a href="newentrancefile.html">an exactly analogous file</a> for cave entrances except that those files live in <span style="font-family: monospace">:expoweb:/entrance_data/</span> 
-
+<h3>Template Files - please use these</h3>
+  <p>
+    There are template files for you to fill-in when creating new caves and entrance in the online system. Download them:
+    <ul>
+    <li><a download href="../../templates/cave_data.html">cave_data template</a>
+    <li><a download href="../../templates/entrance_data.html">entrance_data template</a>
+    </ul>
+    These are XML files, exactly as shown above, but with extensive instructions within each file.
+  </p>
+  
 <h2>File layout</h2>
   <p>The caves in our site are stored as XML files in the directory <tt>:expoweb:/cave_data</tt> and in
     files named <tt>:expoweb:/cave_data/{area}-{cavenumber}</tt>. Entrances are correspondingly
diff --git a/handbook/troggle/trogstatus.html b/handbook/troggle/trogstatus.html
index 488e790a6..071f32500 100644
--- a/handbook/troggle/trogstatus.html
+++ b/handbook/troggle/trogstatus.html
@@ -41,7 +41,7 @@ Upgrading to later django versions is a real pig - not helped by the fact that a
 <li>For a table displaying the various versions of django and support expiry dates 
 see <a href="https://www.djangoproject.com/download/">the django download</a> page. 
 Django 1.7 expired in December 2015.
-Django: <a href="">full deprecation timeline</a>.
+Django: <a href="https://www.djangoproject.com/download/#supported-versions">full deprecation timeline</a>.
 
 <li>Ubuntu 20.04 came out on 23rd April but it does not support python2 at all. So we cannot use it for software maintenance (well be can, but only using non-recommended software, which is what we are trying to get away from).
 </ul>