<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>Handbook Troggle Index</title> <link rel="stylesheet" type="text/css" href="/css/main2.css" /> </head> <body> <style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style> <h2 id="tophead">CUCC Expedition Handbook</h2> <h1>Handbook Troggle - Index</h1> <p>The number of different webpages describing troggle, configuring the server troggle runs on, maintaining the underlying Django system, current documentation, future design issues and historical decisions is all getting a bit voluminous. So we need a complete index: <p><img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a> <a href="trogintro.html">Troggle - Introduction</a> - what it is<br> <a href="training/trogbegin.html">Troggle - initial training</a> - start here for complete beginners<br> <a href="trogusers.html">Troggle - the Users</a> - Who needs to know What and When<br> <a href="trogreports.html">Troggle - Surveys & Caves</a> - Trips, surveys, explorers, sketches, data...<br> <a href="trogdocm.html">Troggle - Fixing things</a> - users' manuals for data import<br> <a href="trogmanual.html">Troggle - Maintenance</a> - list of maintenance tasks<br> <a href="trogarch.html">Troggle - Architecture</a> - diagrams, files, structure<br> <a href="datamodel.html">Troggle - Data Model</a> - syntax-coloured list of classes, instance variables and foreign keys<br> <a href="trogdesign.html">Troggle - What it does Badly</a> - Design Decisions for the Future<br> <ul> <li><a href="trogregistr.html">Troggle Login and user registration</a> - proposal to remove registration (DONE)<br> <li><a href="lbredesign.html">Troggle Logbook Format Redesign</a> - revising the logbook HTML (DONE)<br> <li><a href="menudesign.html">Troggle Menu Design</a> - options for replacing the menuing system<br><br> <li><a href="namesredesign.html">Troggle people's names' redesign</a> (DONE) <li><a href="trogsimpler.html">Troggle - a kinder simpler troggle?</a> - Radost's proposals (critiqued)<br> <li><a href="trogspeculate.html">Troggle Architecture Speculations</a> - as in April 2020<br> <li><a href="trog2030.html">Troggle in 2025-2030</a> - architectural evolution proposal<br> <li><a href="trogkill.html">Troggle - Kill it with Fire</a> - rewrite considerations<br> </ul> <a href="troglaptop.html">Troggle laptop configuration</a> - how to set up a software development machine<br> <ul> <li><a href="djangostart.html">Django initial installation</a> - what django-start should do<br> </ul> <a href="serverconfig.html">Troggle server configuration</a> - how to get troggle running on a new machine (incomplete!)<br> <a href="trogimport.html">Troggle - Data Import</a> - reset and import data<br> <ul> <li><a href="exportjson.html">Troggle - JSON export</a> - export data as JSON<br> </ul> <a href="trogdjango.html">Troggle and Django</a> - The Django web framework we use<br> <a href="trogdjangup.html">Troggle: updating Django</a> - Upgrading troggle to use a later Django version<br> <a href="trogtests.html">Troggle tests</a> - test suite for programmers<br> <a href="trogstatus.html">Troggle & expo systems - status update</a> - where we are now<br> <br> <a href="trognotes.html">Troggle Programmers's Notes</a> - improving, updating, fixing, refactoring<br> <a href="trogassumptions.html">Pre-Troggle Assumptions</a> - list of assumptions<br> <a href="archnotes.html">Archive Notes</a> - old ideas and original discussions<br> <br> <a href="scriptsother.html">Additional Scripts</a> - non-django but important<br> <ul> <li><a href="scriptsqms.html">QM (Question Mark) Scripts</a> - all five ways we do it<br> <li><a href="scriptscurrent.html">Additional Scripts</a> - more detail<br> <li><a href="exporttgz.html">Export all.tgz</a> - export compressed survey data (Makefile)<br> </ul> <br> <hr /> Return to: <a href="trogintro.html">Troggle intro</a><br /> <hr /></body> </html>