<p>There is no script to do this (yet). In the list below everything in expofiles is done by directly overwriting what is on the server. Changes to expoweb and troggle must be done using the version control system as these are <ahref="../computing/repos.html">repositories</a>.
<li>expofiles/accounts/ - optional. Used for archiving after expo.
<li>expofiles/videos/ - optional. We don't do this much.
</ul>
<li>edit /expoweb/index.htm - edit the title and make it link to e.g. expoweb/years/2021/
<li>edit troggle/templates/base.html - change the title and add a link to this year's expo
<li>copy the contents of the previous year's expoweb/years/ folder, e.g. /2016/ to /2017/ and edit all the files therein. You should start with at least an index.html and a mission.html
</ul>
<h4>Whenever you like before Expo</h4>
<ul>
<li>copy wallets.py from the previous year's folder in expofiles/surveyscans/ into the current year
<li>create 50 folders in the new surveyscans year folder e.g. in expofiles/surveyscans/2021/ of the form /2021#01/, /2021#02/ etc.
<li>Test that the bierbook and seshbook LaTeX scripts expoweb/documents/bierbook work on your machine</li>
<li>create initial versions of the bierbook and the seshbook in expoweb/documents/bierbook (the final copies after expo will be scanned and put in e.g. expofiles/writeups/2021/ along with the scanned logbook). These need an updated names.txt file of expoers.
<li>update the gear tape colours for the expected expoers in <ahref="../geartape.html">/expoweb/handbook/geartape.html</a></li>