Setting

ATH Website Maintenance

1. Website Update Tasks

The setter will need to update this ATH website before, during, and after their Hunt. Hopefully this shouldn't be too onerous a task, and some notes are provided below to help.

During 2008, undertook some basic revamping of the website to hopefully make it a little easier to maintain. To do this, he used the Adobe Dreamweaver HTML Editor. This does not mean that all future updates need to be performed with that tool, but it would be helpful if the basic page template and library item references can be respected in order to facilitate future site-wide updates.

The website updates that will likely need to be performed as part of a Setter's tenure include:

Some help and pointers are given below on each of these tasks. Before that, though, some website related prepration needs to be undertaken.

2. Pre-Hunt Preparation

Well in advance of publishing the Hunt, the setter needs to prepare for maintaining the website:

3. ATH Website Design Principles

For the Armchair Treasure Hunt website itself, there are a few basic design principles that should be adhered to. The setter is of course free to do whatever they like for a web-based Hunt.

4. Updating the ATH News Headlines

There's no need to mount a 24 hour news service, but the key announcements regarding your Hunt should be announced in the 'Latest ATH News' headlines box on the home page:

It should be very easy to make these HTML updates, and a template news list item <li><⁄li> can be found commented out in the HTML source of the home page in the <div id="newsbox"> panel. There may well still be news items from the previous Hunt that you can use and update.

5. Publish the Armchair Treasure Hunt

The details of ATH publication may vary slightly depending on the type of Hunt being published, but the following instructions cover both a web-based Hunt and a single PDF document.

The 2017 Hunt has taken a different approach to the website structure; this section is out-of-date and has been removed until after the 2017 Hunt.

Once you have uploaded the ATH, index pages, and notes pages to the live site, check that everything is okay, and then announce ATH publication on the site home page.

6. Publish the Solution, Results, etc.

The Solution, Results, Tales and Setter Notes are all produced and published in the Archive section of the website for the appropriate year e.g. in the ⁄archive⁄2013⁄ folder. Pages also exist in the archive to provide a link to the Puzzle and the Poster. Publishing these six pages is thus a major part of the ATH archiving process. You can see examples of these pages under any previously archived ATH.

If the ATH puzzle was in the form of a single PDF document, that file should be archived to e.g. ⁄archive⁄2013⁄docs⁄puzzle2013.pdf.

For a web-based Hunt, copy all the files comprising the ATH into the e.g. ⁄archive⁄2013⁄ATH2013⁄ folder. The main index page is thus copied from ⁄current⁄hunt⁄index.html to ⁄archive⁄2013⁄ATH2013⁄index.html, and is the page to link to when referencing the archived puzzle.

Again template files and an appropriate sub-directory structure has been set up in the ⁄archive⁄YYYY⁄ folder. The instructions for using these templates to create the next year's ATH archive can be found in the ⁄archive⁄YYYY⁄ReadMe.txt document in that folder. The examples from previous years' Hunts should also act as a useful guide as they were all produced using these templates.

Once you have created these files and added the content, make an announcement on the ATH home page that the solution, results etc are now available. Also see the guidance on publishing the solution and generating the results by marking the entries.

7. Archive the Armchair Treasure Hunt

A large part of the archiving process is producing and publishing the Puzzle, Solution, Notes, Tales, Results, and Poster pages as described in the section above. The other steps that need to take place are shown below. Note that in recent years the archiving work has been done by ATH administration after the hunt is complete and the setter hands back web site 'control'.

And that's all there is to it!