<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>{{logbook_entries.0.expedition}} Expo Logbook</title>
<link rel="stylesheet" href="/css/main2.css" />
<meta name="keywords" content="NOEDIT">
<style>figure {font-weight: bold; font-size: small; font-family: sans-serif;font-variant-caps: small-caps;}</style>
</head>
<!-- Exported by troggle because one entry has been edited, and we reconstruct the whole thing. 

As of 10 Dec.2024 the list of participants in every trip is re-ordered to be in alphabetic
order of name (or nickname, if used) whenever any entry is edited and the logbook.html file 
re-written. This is prevent spurious re-orderings and spurious git commit lines which obscure real changes.

Sorry about all the crap that surrounds the image tags which has been imported along with the content
when UK Caving blogs have been parsed.

Exported on {% now 'Y-m-d H:m' %} using either the control panel webpage or when editing a logbook entry online
See troggle/code/views/other.py and core.models/logbooks.py writelogbook(year, filename)
-->
<body>

<button type="button" onclick="window.scrollTo(0, document.body.scrollHeight)" autofocus>Scroll To Bottom</button>
<br/>
<a href="/logbookedit/">Add Log book entry</a>

{%for logbook_entry in logbook_entries%} <hr />
<div class="tripdate" id="{{logbook_entry.slug}}">{{logbook_entry.date|date:'Y-m-d'}}</div>
<div class="trippeople">{{logbook_entry.get_participants|safe}}</div>
<div class="triptitle">{{logbook_entry.title|safe}}</div>
{{logbook_entry.text|safe}}
<div class="timeug">T/U: {{logbook_entry.time_underground|safe}} hours</div>
<div class="editentry"><br /><a href="/logbookedit/{{logbook_entry.slug}}">Edit this entry</a><br /></div>
{% endfor %}<hr />

<button type="button" onclick="window.scrollTo(0, 0)" autofocus>Scroll To Top</button>
<br/>
<a href="/logbookedit/">Add Log book entry</a>

</body>
</html>
