expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-01-31 07:32:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

breadcrumb navigation added for main-thread pages only. Manual HTML.

Browse Source
This commit is contained in:
Philip Sargent 2020-03-02 12:51:18 +00:00
parent 637de04172
commit 5ce24e718d
7 changed files with 77 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/computing/yourlaptop.html
View File

@ -85,6 +85,7 @@ but all the recommended software here is open source (and please don't install p
<ul>
<li><a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html">PuTTY</a> including pagent. Version 0.73 was released on 2019-09-29. You need this to generate and to use ssh keys on Windows. Otherwise none of git, mercurial, scp, ftp or rsync will work. It includes command line tools ssh, scp (pscp) and sFTP (psftp).
<li><a href="https://desktop.github.com/">GitHub Desktop for Windows</a> - yes this works with the expo server
<li><a href="">VS Code</a> is a free (but not FOSS) editor with in-built git capability and plug-ins which render git branches graphically. Also available for Linux.
<li><a href="https://gitforwindows.org/">Git for Windows</a> - not as simple to use as it looks
<li><a href="https://www.gitkraken.com/">GitKraken</a> - Very pretty GUI interface to git, also Linux version.
Times-out for our server unless you buy it but free for university people.
@ -96,6 +97,7 @@ but all the recommended software here is open source (and please don't install p
<a href="../tortoise/tortoise-win.htm">Tortoise-on-Windows</a>. To be replaced by git in Sprin 2020.
</ul>
<p>A short note about the phenomenon of VS code is in order. In case you didn't know, by 2018 over <a href="https://insights.stackoverflow.com/survey/2018">a third</a> of software developers used this editor for their Linux and Windows work and it is undoubtedly more now. Not for beginners.
<p>For Android phones:
<ul>
<li><a href="https://www.termius.com/">Termius</a> - command line to create a key for your phone, to ssh (and mosh) login to the expo server. To get sftp you have to buy it.

12
handbook/survey/caveentry.html
View File

@ -13,11 +13,19 @@
<h2>Great, I have discovered a new cave...</h2>
<p>If you have not come to this page from the sequence starting at <a href="newcave.html">Starting a New Cave"</a> then go and read that first.
<li>This page outlines the next step of the process. Each part of it is documented separately.
<div style="width:100%;height:50px;background:#C8E1E2" align="center">
This page outlines step 6 of the survey production process. Each step is documented separately.<br />
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
</ul>
<a href="newcave.html">1</a>
- <a href="newwallet.html">2</a>
- <a href="newsurvex.html">3</a>
- <a href="drawup.htm">4</a>
- <a href="newrig.html">5</a>
- <a href="caveentry.html">6</a>
- <a href="cavedescription.html">7</a>
</div>
<h2>Process</h2>
<p>
This page and those following describe the process for creating new

12
handbook/survey/drawup.htm
View File

@ -10,11 +10,19 @@
<h2>Great, I have discovered a new cave...</h2>
<p>If you have not come to this page from the sequence starting at <a href="newcave.html">Starting a New Cave"</a> then go and read that first.
<li>This page outlines the next step of the process. Each part of it is documented separately.
<div style="width:100%;height:50px;background:#C8E1E2" align="center">
This page outlines step 4 of the survey production process. Each step is documented separately.<br />
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
</ul>
<a href="newcave.html">1</a>
- <a href="newwallet.html">2</a>
- <a href="newsurvex.html">3</a>
- <a href="drawup.htm">4</a>
- <a href="newrig.html">5</a>
- <a href="caveentry.html">6</a>
- <a href="cavedescription.html">7</a>
</div>
<h2>Process</h2>
<p>
<h3>Drawing up your survey</h3

20
handbook/survey/newcave.html
View File

@ -9,9 +9,6 @@
<body>
<h2 id="tophead">CUCC Expedition Handbook - New Cave</h2>
<h1>Creating a new cave in the online system</h1>
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
<h2>Great, I have discovered a new cave...</h2>
<p>So, you have staggered off the plateau with a fist-full of notes and surveys,
@ -26,9 +23,20 @@ survey information in your waterproof notebook. But first you should read the
<li><a href="/expofiles/presentations/cave_surveying_20130626.pdf">
Cave Surveying training course slidepack</a>.
</ul>
<li>This page outlines the rest of the process. Each part of it is documented separately.
</ul>
<br />
<div style="width:100%;height:50px;background:#C8E1E2" align="center">
This page outlines step 1 of the survey production process. Each step is documented separately.<br />
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
<a href="newcave.html">1</a>
- <a href="newwallet.html">2</a>
- <a href="newsurvex.html">3</a>
- <a href="drawup.htm">4</a>
- <a href="newrig.html">5</a>
- <a href="caveentry.html">6</a>
- <a href="cavedescription.html">7</a>
</div>
<h2>Process</h2>
<p>After 40 years or so, we have a well-defined process which you will need to learn.
Read <em>all</em> this list first, then follow

23
handbook/survey/newrig.html
View File

@ -3,6 +3,14 @@
<title>CUCC Expo Surveying Handbook: Drawing Up</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<style type="text/css">
#outer
}
</style>
<body>
<h2 id="tophead">CUCC Expedition Handbook - New rigging guide</h2>
<h1>New rigging guide</h1>
@ -10,19 +18,30 @@
<h2>Great, I have discovered a new cave...</h2>
<p>If you have not come to this page from the sequence starting at <a href="newcave.html">Starting a New Cave"</a> then go and read that first.
<li>This page outlines the next step of the process. Each part of it is documented separately.
<div style="width:100%;height:50px;background:#C8E1E2" align="center">
This page outlines step 5 of the survey production process. Each step is documented separately.<br />
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
<a href="newcave.html">1</a>
- <a href="newwallet.html">2</a>
- <a href="newsurvex.html">3</a>
- <a href="drawup.htm">4</a>
- <a href="newrig.html">5</a>
- <a href="caveentry.html">6</a>
- <a href="cavedescription.html">7</a>
</div>
</ul>
<h2>Process</h2>
<p>
<h3>Interim rigging guide</h3>
The logbook is the place where we record the rigging of caves as we discover them.
The logbook is the place where we record the rigging of caves as we discover them. For a particularly fine example of rigging guides in a logbook see <a href="../../years/2015/logbook.html">the 2005 logbook</a>.
<p>
When a cave is derigged, a good way of getting the rope lengths for your rigging guide is to leave the knots in ropes removed so they can be measured, but these days our caves are a bit deep and complicated for this to be feasible. Although a good survey and details of the belays can be used to estimate the length of rope needed, this is no substitute for measuring how much rope it actually took to rig.
<h3>Final rigging guide</h3>
<p>Complementing the passage description in vertical bits is a <b>Rigging

12
handbook/survey/newsurvex.html
View File

@ -13,11 +13,19 @@
<h2>Great, I have discovered a new cave...</h2>
<p>If you have not come to this page from the sequence starting at <a href="newcave.html">Starting a New Cave"</a> then go and read that first.
<li>This page outlines the next step of the process. Each part of it is documented separately.
<div style="width:100%;height:50px;background:#C8E1E2" align="center">
This page outlines step 3 of the survey production process. Each step is documented separately.<br />
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
</ul>
<a href="newcave.html">1</a>
- <a href="newwallet.html">2</a>
- <a href="newsurvex.html">3</a>
- <a href="drawup.htm">4</a>
- <a href="newrig.html">5</a>
- <a href="caveentry.html">6</a>
- <a href="cavedescription.html">7</a>
</div>
<h2>Process</h2>
<p>In principle you do not need any software other than a text editor to create a survex file.
So you do not need to have installed survex on your laptop at this point.

13
handbook/survey/newwallet.html
View File

@ -13,12 +13,19 @@
<h2>Great, I have discovered a new cave...</h2>
<p>If you have not come to this page from <a href="newcave.html">Starting a New Cave"</a> then go and read that first.
<li>This page outlines the next step of the process. Each part of it is documented separately.
</ul>
<div style="width:100%;height:50px;background:#C8E1E2" align="center">
This page outlines step 2 of the survey production process. Each step is documented separately.<br />
<!-- Yes we need some proper context-marking here, breadcrumb trails or something.
Maybe a colour scheme for just this sequence of pages
-->
<a href="newcave.html">1</a>
- <a href="newwallet.html">2</a>
- <a href="newsurvex.html">3</a>
- <a href="drawup.htm">4</a>
- <a href="newrig.html">5</a>
- <a href="caveentry.html">6</a>
- <a href="cavedescription.html">7</a>
</div>
<h2>Process</h2>
<p>