diff --git a/index.mdwn b/index.mdwn
index 3c5c216..d712a7f 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,4 +1,4 @@
-# Kia ora! Can I really just edit this?
+# Kia ora! Martin smells, and is bad at squash
 
 Welcome to the [Thorndon Squash Club](https://thorndonclub.co.nz) collaborative Wiki, where we amass the knowledge that empowers our volunteers to keep our club throbbing and our community thriving!
 

diff --git a/index.mdwn b/index.mdwn
index 754b7ef..3c5c216 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,4 +1,4 @@
-# Kia ora!
+# Kia ora! Can I really just edit this?
 
 Welcome to the [Thorndon Squash Club](https://thorndonclub.co.nz) collaborative Wiki, where we amass the knowledge that empowers our volunteers to keep our club throbbing and our community thriving!
 

diff --git a/TournamentTravel.mdwn b/TournamentTravel.mdwn
index a78f921..e9250e9 100644
--- a/TournamentTravel.mdwn
+++ b/TournamentTravel.mdwn
@@ -1,158 +1,11 @@
 # Upcoming travel
 
-## 19–20 Nov SquashGym Summer Open
+## Date — Tournament name
 
-(conflicts with Thorndon Doubles)
+* Name
 
-* Lucas
-* Martin
-
-## 2–3 Dec Silverdale A2&Below (traffic light system pending)
-
-* Martin
+-----
 
 # Completed
 
-## Feb 19–20 Ōtaki Open
-
-* Paige (own accomodation)
-* Martin
-* Linc (staying with Martin & family)
-* *Wayne?*
-
-## Mar 19–20 Nelson Open
-
-Plan: travel there by rental car (cheaper than own car on ferry) Friday morning and stop at Pelorus Bridge. Maybe a relaxed Sunday and take the ferry back.
-
-* Ferry Fri 9am – Sun 6:30pm, and staying together at 114 Rutherford Street:
-  * Martin
-  * Lucas & Caro
-  * Linc
-  * Jess (who arrives on the Bluebridge a bit earlier)
-* Same ferry, but staying at The Sands:
-  * Gil
-  * Lee-Ann
-  * Hannah
-  * Ruben (not playing)
-* Former member Hannah Thompson is in Nelson.
-* *Kate & Cam?*
-
-## Apr 2–4 KP A2&Below+Doubles ~~Queenstown Open or Te Puke Open or~~ 
-
-* Driving up Friday with Linc and dog, and staying at an AirBnB:
-  * Martin
-  * Linc
-  * Kay
-  * ~~Jess~~
-
-## Apr 9–10 Wairarapa Masters
-
-* Kay
-* Lee-Ann & Gillie
-* Diane
-* Jono
-* ~~Jemma~~
-
-## Apr 23–24 Geyser City Open (Rotorua)
-
-* Martin (passing through in a Campervan)
-
-## Apr 29 – May 1 Pirates Open (Dunedin)
-
-* Dan Foote
-
-## May 7–9 Kaikoura Open [closed]
-
-(conflicts with Tawa Open)
-
-* Lucas & Caro
-
-## May 21–22 Central & Taranaki Open @ Kawaroa New Plymouth
-
-(conflicts with Mana Open)
-
-* Kate & Cam
-
-## May 21–22 PSA Browns Bay
-
-(conflicts with Mana Open)
-
-* Martin
-
-## May 28–29 Hawkes Bay Tennis & Lawn Open
-
-* Martin
-* Tess
-* Jenny
-* Kay
-* Jess
-* Jono
-
-## May 28–29 Martinborough Open
-
-* Clint
-* Kate & Cam
-
-## Jun 4–6 Wanaka Open [closed]
-
-Heading out on 3 June, 10:20 flight, and returning 7 June 12:30 via Queenstown, possibly with a snowboard are:
-
-* Linc
-* Martin
-
-## Jun 11–12 Hawera Open
-
-* Jack D.
-* Martin
-* Brad & Christine
-* Jaron
-* Andrew L.
-* Sam & Grace from IB
-* Jack S. from IB
-
-## Jul 8–9 Greymouth Open [closed, waitlist]
-
-(conflicts with Hutt City Open)
-
-* Martin
-
-Current plan is to hitchhike my way down the west coast to the next one. Anyone? ;)
-
-## Jul 16–17 Southland Open @ Invercargill
-
-* Martin
-
-## [postponed due to COVID19] Aug 20–21 Surf City Open (Gisborne)
-
-(conflicts with Wainuiomata B&Below)
-
-* Martin
-* Kate & Cam?
-
-## [cancelled due to COVID19] Sep 3–5 Pirates Dunedin or Kaikoura Masters
-
-(conflicts with Kapiti Masters)
-
-* Martin
-* Linc
-
-Linc and Martin are taking the ferry over on Thursday, in the hope of hitting the slopes Friday morning. Post-tournament, we drive to Christchurch, and Martin flies home from there, while Lincoln goes to seek more snow.
-
-## 15–16 Oct Ossie's Ohakune Open
-
-* Shanti
-* Jemma
-* Linc
-* Martin
-
-## [cancelled] 22–23 Oct Katikati Open
-
-* Easy
-* Frosty
-* Martin
-
-## [cancelled] 29–30 Oct Foxton B&Below
-
-(conflicts with Martinborough Doubles)
-
-* *Martin?*
+Previous years: [[2021|TournamentTravel2021]]
diff --git a/TournamentTravel2021.mdwn b/TournamentTravel2021.mdwn
new file mode 100644
index 0000000..7f53297
--- /dev/null
+++ b/TournamentTravel2021.mdwn
@@ -0,0 +1,156 @@
+
+## Feb 19–20 Ōtaki Open
+
+* Paige (own accomodation)
+* Martin
+* Linc (staying with Martin & family)
+* *Wayne?*
+
+## Mar 19–20 Nelson Open
+
+Plan: travel there by rental car (cheaper than own car on ferry) Friday morning and stop at Pelorus Bridge. Maybe a relaxed Sunday and take the ferry back.
+
+* Ferry Fri 9am – Sun 6:30pm, and staying together at 114 Rutherford Street:
+  * Martin
+  * Lucas & Caro
+  * Linc
+  * Jess (who arrives on the Bluebridge a bit earlier)
+* Same ferry, but staying at The Sands:
+  * Gil
+  * Lee-Ann
+  * Hannah
+  * Ruben (not playing)
+* Former member Hannah Thompson is in Nelson.
+* *Kate & Cam?*
+
+## Apr 2–4 KP A2&Below+Doubles ~~Queenstown Open or Te Puke Open or~~ 
+

(Diff truncated)

diff --git a/TC/ClosingRegistrations.mdwn b/TC/ClosingRegistrations.mdwn
index bdebdf2..2440430 100644
--- a/TC/ClosingRegistrations.mdwn
+++ b/TC/ClosingRegistrations.mdwn
@@ -3,7 +3,10 @@
 During the [[advertising and registration phase|TC/RegistrationPhase]], it is
 prudent to regularly check the list of registrations, as there is no way to
 limit the number on iSquash, and you don't want to end up with heaps above
-your limit.
+your limit. The `tctools` toolkit contains [a simple script that you can
+invoke regularly to snapshot
+registrations](https://github.com/madduck/tctools/tree/main/scripts#splitting-off-a-waiting-list)
+at any given time.
 
 It may be a good idea to close registrations at 80–90% capacity, before
 specifically targetting members of your club, or inviting others you'd like to
@@ -23,16 +26,33 @@ have not been made, this can be any player, but if you've already drafted the
 draws, it pays to have a full waiting list so that there's a higher chance of
 another player in the same grade range able to slot right in.
 
+## Using a single iSquash event
+
 The first approach is slightly easier at first, but you'll later end up with
 two lists that may diverge. Also, leaving the main event up there means that
 people can just deregister themselves, without you finding out until you
 compare the status quo to the snapshot, and work out the intersection between
 the two sets.
 
-The second approach takes a bit more effort, but it's better in that it keeps
-the list of confirmed registrations separate from the waiting list. Moreover,
-if people want to pull out, they have to do so by letting you know, and you
-can then immediately look into filling their spot.
+Again, the [[tctools]] scripts take care of that for you though, and with these
+helpers, all you have to do is run
+[`scripts/snapshot_registrations.sh`](https://github.com/madduck/tctools/blob/main/scripts/snapshot_registrations.sh)
+at regular intervals, and it'll split the registered players into those who
+have made the cut, and those who are still on the waiting list. The way it
+works is by comparing all snapshots created, and keeping track of who
+registered when. The more often you run it, the better it'll be able to
+determine just who should make the cut because they were slightly earlier than
+the rest, because if two players register between any two runs, and there is
+only one space left, it'll be the higher graded player who gets the go, even if
+the lower graded player registered earlier — there is no other way of doing it
+than snapshots, since iSquash does not record registration times.
+
+## Using a separate waiting list event
+
+The second approach takes a bit more effort, but you may prefer it in that it
+keeps the list of confirmed registrations separate from the waiting list.
+Moreover, if people want to pull out, they have to do so by letting you know,
+and you can then immediately look into filling their spot.
 
 To hide an event from iSquash, set the "last registration date" property to
 yesterday's date, and create a new event, advertised as "waiting list", into
@@ -48,8 +68,15 @@ The downsides of having a separate event in place as the waiting list are:
   registered players, people might — no — people *will* forget that they've
   registered;
 
-And now is the right time to drop all registrants an email, to inform them
-that registrations have closed, and ask if any plans have changed, so that you
+Whichever approach you use is up to you. Before `tctools`' automation, the waiting
+list was the saner albeit more elaborate approach. With the help of `tctools`, the
+snapshot approach is likely to be a lot easier and flexible, if you can ensure
+that the snapshots are generated frequently.
+
+-----
+
+Now is the right time to drop all registrants an email, to inform them that
+registrations have closed, and ask if any plans have changed, so that you
 can update the list of players right away.
 
 Let's move on to [[player communications|TC/PlayerComms]].
diff --git a/TC/MakingDraws.mdwn b/TC/MakingDraws.mdwn
index 7ca64ed..7584afc 100644
--- a/TC/MakingDraws.mdwn
+++ b/TC/MakingDraws.mdwn
@@ -14,6 +14,13 @@ to deal with, it may be necessary to draft up some draws at random times
 beforehand, to identify holes that may need to be plugged e.g. by moving
 people over from the waiting list, and inviting other players.
 
+Therefore, you will want to delay making the draws until after sending out a
+"final call" to all registered players, and giving them enough time to get back
+to you with any changes. But you don't want to leave your players waiting too
+long, and it's generally good practice to have the draws finished on the weekend
+prior to your tournament — don't worry about results of a current tournament
+not having been entered yet.
+
 ## Applying for a TournamentControl event
 
 Now is a good time to [apply for a TournamentControl
@@ -26,7 +33,9 @@ don't need to specify a public IP address.
 Strictly speaking, draws are made in decreasing order of grading points at the
 time of "seeding the tournament", which is a required step on iSquash prior
 to extracting the list of registrations — where "required" means that you
-should do it, not that iSquash would in any way force you to.
+should do it, not that iSquash would in any way force you to. However, if you
+use [[tctools]] to snapshot the registrations, it'll do it automatically for
+you.
 
 When a player registers for an event, they are entered with their grading
 points at the time of their entry. When you register a player for an event,
@@ -49,33 +58,43 @@ to assign people to draws later in any order you choose, but wiggling their
 grading points at the time of seeding leaves a better paper trail of such
 actions, and ensures reproducible results.
 
-## The Draw Maker
+## `tctools` and The Draw Maker
 
 Extracting registrations from iSquash gives you a spreadsheet that you can
-play around with to make the draws, and the [[DrawMaker]] is a spreadsheet
-tool designed to make this process a lot easier, even enjoyable. Once you've
-loaded the registrations and waiting list, you can
+play around with to make the draws, and with the [[tctools]] comes a
+spreadsheet designed to make this process a lot easier, even enjoyable, called
+the "DrawMaker". Once you've loaded the registrations and waiting list, you
+can
 
 * easily pick&choose players into draws;
 * quickly see what contact details you're missing;
 * record player restrictions and analyse the effects these
-  restrictions have on playing times;
+  restrictions have on what days matches can take place;
 * and also plan out early games to be played on Wednesday and Thursday, so as
   to minimise the number of games that need to be played on Saturday morning,
   which is the main bottleneck of any tournament with a Saturday finish;
-* get access to a number of useful and less useful statistics
+* get access to a number of useful and less useful statistics;
+* automatically import the draws into iSquash.
+
+Usage of the Draw Maker is explained [on the project's
+homepage](https://github.com/madduck/tctools/tree/main/draw_maker#readme), and
+there are even some videos.
 
-Usage of the Draw Maker is explained on [[a separate page|DrawMaker]]. For
-now, we'll assume that you've arrived at a final set of player-to-draw
+For now, we'll assume that you've arrived at a final set of player-to-draw
 assignments by any means, and are ready to move on.
 
 ## Creating draws in iSquash
 
 Once you're happy with the draws, you need to go back to iSquash to create the
 draws, and assign the players according to what you've designed.
-Unfortunately, this is a cumbersome part of the process, but there is
-unfortunately no way around it, and it's required so that you can later record
-results and propagate them to the grading list.
+Unfortunately, this is a cumbersome part of the process, and unless you use
+`tctools` and the DrawMaker, there is unfortunately no way around it, and it's
+required so that you can later record results and propagate them to the grading
+list.
+
+Even if you are using the DrawMaker, please ensure that you know what's going on.
+It might still be a good idea to keep reading, although the following will all
+be done for you:
 
 While you are in the process of creating draws, it might be a good idea to
 untick "Show under Current Tournaments" in the iSquash settings of the event,
@@ -128,6 +147,15 @@ it's necessary for results entry (and other reasons).
 Once the draws are all seeded and matches initialised, you can tick the "Show
 under Current Tournaments" box again in the Pre-Tournament settings.
 
+## Using the DrawMaker and `tctools`
+
+The `tctools` come with a script called
+[`manage_isquash_tournament.py`](https://github.com/madduck/tctools/blob/main/scripts/manage_isquash_tournament.py)
+which can manage player registrations, create draws, and seed them. Please
+refer to [its
+documentation](https://github.com/madduck/tctools/tree/main/scripts#managing-isquash-tournaments)
+for more info.
+
 ## Scheduling matches
 
 Scheduling matches is the most painful part of tournament organisation, as it
@@ -136,6 +164,12 @@ holes, with players having restrictions and preferences left and right. One
 way to facilitate this is to flat-out refuse to honour more than one
 restriction (and announce this in the event description).
 
+The [DrawMaker](https://github.com/madduck/tctools/tree/main/draw_maker) does
+allow you to record the days on which players cannot play, and it will then
+assign the games to days. This works for 8, 6b, and 4 draws, and allows you to
+focus only on a subset of games at a time, which should make scheduling a fair
+bit easier.
+
 Another way to make it easier for you is to use
 [TournamentControl](https://tournamentcontrol.dtkapiti.co.nz/)
 instead of iSquash scheduling. TournamentControl also makes running the
@@ -159,14 +193,9 @@ else to get this information, then it's perfectly fine to forego the pain and
 skip this step.
 
 One way in which the players can find out is through TournamentControl,
-but that does not work on iPhones (August 2021). However, TournamentControl
-lets you export the data, and with a little bit of hackery, it is not only
-possible to publish game times on a web site, it's also conceivably to
-literally squeeze the schedule information into iSquash, but let's not get
-ahead of ourselves (we will cover these topics in [[TCHacks]). For now, let's
-assume you're going to use TournamentControl to schedule matches, and run the
-tournament. There are other solutions, including some that extend to
-scoreboards on the court, but Thorndon has a TournamentControl licence, so
-there…
+but that does not work on iPhones (August 2021). However, as part of `tctools`,
+there is [tc2web](https://github.com/madduck/tctools/tree/main/tc2web), which

(Diff truncated)

diff --git a/index.mdwn b/index.mdwn
index 07ed106..754b7ef 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -52,17 +52,17 @@ top right**. Let's keep this information alive, together.
 
 Our constitution only has room for one squash club captain, but until we get a chance to change that, at [Thorndon](https://thorndonsquash.co.nz) there's a team running Everything Squash:
 
-| Role                  | Name              | Phone      | Email                         |
-|-----------------------|-------------------|------------|-------------------------------|
-| Membership & grading  | Brad Watts        | 0273905892 | info@thorndonclub.co.nz       |
-| Interclub convenor    | Josie Grover      | 0279686450 | interclub@thorndonclub.co.nz  |
-| Intraclub convenor    | Shanti Spendiff   | 021566036  | intraclub@thorndonclub.co.nz  |
-| Welcoming committee   | Shanti Spendiff   | 021566036  | welcome@thorndonclub.co.nz    |
-| Club nights           | Christine Rukuwai | 0272527593 | christine.rukuwai@hotmail.com |
-|                       | Paras Khanna      | 0204727270 | paras.khanna87@gmail.com      |
-| Newsletter            | Martin Krafft     | 0211100938 | squashnews@thorndonclub.co.nz     |
-| Tournament control    | Martin Krafft     | 0211100938 | squashtc@thorndonclub.co.nz   |
-| Miscellanous & sundry | Martin Krafft     | 0211100938 | squash@thorndonclub.co.nz     |
+| Role                 | Name              | Phone      | Email                         |
+|----------------------|-------------------|------------|-------------------------------|
+| Membership & grading | Brad Watts        | 0273905892 | info@thorndonclub.co.nz       |
+| Welcoming committee  | Shanti Spendiff   | 021566036  | welcome@thorndonclub.co.nz    |
+| Interclub convenor   | Josie Grover      | 0279686450 | interclub@thorndonclub.co.nz  |
+| Intraclub convenor   | Christine Rukuwai | 0272527593 | intraclub@thorndonclub.co.nz  |
+| Club nights          | Christine Rukuwai | 0272527593 | christine.rukuwai@hotmail.com |
+|                      | Paras Khanna      | 0204727270 | paras.khanna87@gmail.com      |
+| Newsletter           | Victoria Moyle    | 0279514099 | squashnews@thorndonclub.co.nz |
+| Tournament control   | Martin Krafft     | 0211100938 | squashtc@thorndonclub.co.nz   |
+| Squash club captain  | Mike McCarroll    | 0278607128 | squash@thorndonclub.co.nz     |
 
 If you have an idea you'd like to see fly, or you would like to get involved, please get in touch with
 us. We run as a do-oracy, meaning that anything is possible if someone is prepared to see it through.

diff --git a/TournamentTravel.mdwn b/TournamentTravel.mdwn
index f79fff6..a78f921 100644
--- a/TournamentTravel.mdwn
+++ b/TournamentTravel.mdwn
@@ -1,9 +1,5 @@
 # Upcoming travel
 
-## 22–23 Oct Alexandra Open
-
-* Martin
-
 ## 19–20 Nov SquashGym Summer Open
 
 (conflicts with Thorndon Doubles)
@@ -11,6 +7,10 @@
 * Lucas
 * Martin
 
+## 2–3 Dec Silverdale A2&Below (traffic light system pending)
+
+* Martin
+
 # Completed
 
 ## Feb 19–20 Ōtaki Open

diff --git a/TournamentTravel.mdwn b/TournamentTravel.mdwn
index 1742546..f79fff6 100644
--- a/TournamentTravel.mdwn
+++ b/TournamentTravel.mdwn
@@ -1,12 +1,5 @@
 # Upcoming travel
 
-## 15–16 Oct Ossie's Ohakune Open
-
-* Shanti
-* Jemma
-* Linc
-* Martin
-
 ## 22–23 Oct Alexandra Open
 
 * Martin
@@ -145,6 +138,13 @@ Current plan is to hitchhike my way down the west coast to the next one. Anyone?
 
 Linc and Martin are taking the ferry over on Thursday, in the hope of hitting the slopes Friday morning. Post-tournament, we drive to Christchurch, and Martin flies home from there, while Lincoln goes to seek more snow.
 
+## 15–16 Oct Ossie's Ohakune Open
+
+* Shanti
+* Jemma
+* Linc
+* Martin
+
 ## [cancelled] 22–23 Oct Katikati Open
 
 * Easy

diff --git a/TournamentTravel.mdwn b/TournamentTravel.mdwn
index d6b038b..1742546 100644
--- a/TournamentTravel.mdwn
+++ b/TournamentTravel.mdwn
@@ -7,17 +7,16 @@
 * Linc
 * Martin
 
-## 22–23 Oct Katikati Open
+## 22–23 Oct Alexandra Open
 
-* Easy
-* Frosty
 * Martin
 
-## 29–30 Oct Foxton B&Below
+## 19–20 Nov SquashGym Summer Open
 
-(conflicts with Martinborough Doubles)
+(conflicts with Thorndon Doubles)
 
-* *Martin?*
+* Lucas
+* Martin
 
 # Completed
 
@@ -146,3 +145,14 @@ Current plan is to hitchhike my way down the west coast to the next one. Anyone?
 
 Linc and Martin are taking the ferry over on Thursday, in the hope of hitting the slopes Friday morning. Post-tournament, we drive to Christchurch, and Martin flies home from there, while Lincoln goes to seek more snow.
 
+## [cancelled] 22–23 Oct Katikati Open
+
+* Easy
+* Frosty
+* Martin
+
+## [cancelled] 29–30 Oct Foxton B&Below
+
+(conflicts with Martinborough Doubles)
+
+* *Martin?*

diff --git a/TournamentTravel.mdwn b/TournamentTravel.mdwn
index 763b79e..d6b038b 100644
--- a/TournamentTravel.mdwn
+++ b/TournamentTravel.mdwn
@@ -19,10 +19,6 @@
 
 * *Martin?*
 
-## Nov 12–13 Levin Summer Open
-
-* *Martin?*
-
 # Completed
 
 ## Feb 19–20 Ōtaki Open

diff --git a/TournamentTravel.mdwn b/TournamentTravel.mdwn
index 7bf9356..763b79e 100644
--- a/TournamentTravel.mdwn
+++ b/TournamentTravel.mdwn
@@ -1,31 +1,22 @@
 # Upcoming travel
 
-## Sep 3–5 Pirates Dunedin or Kaikoura Masters
-
-(conflicts with Kapiti Masters)
-
-* Martin
-* Linc
-
-Linc and Martin are taking the ferry over on Thursday, in the hope of hitting the slopes Friday morning. Post-tournament, we drive to Christchurch, and Martin flies home from there, while Lincoln goes to seek more snow.
-
 ## 15–16 Oct Ossie's Ohakune Open
 
-* *Martin?*
-
-## 23–29 Oct [Cook Islands Squash Open](https://www.dmck.com/events/cook-islands-squash-open/), Rarotonga
-
-* *Lucas?*
-* *Andrew?*
-* *Martin?*
+* Shanti
+* Jemma
+* Linc
+* Martin
 
-## late Oct Katikati Open
+## 22–23 Oct Katikati Open
 
 * Easy
 * Frosty
+* Martin
 
 ## 29–30 Oct Foxton B&Below
 
+(conflicts with Martinborough Doubles)
+
 * *Martin?*
 
 ## Nov 12–13 Levin Summer Open
@@ -149,3 +140,13 @@ Current plan is to hitchhike my way down the west coast to the next one. Anyone?
 
 * Martin
 * Kate & Cam?
+
+## [cancelled due to COVID19] Sep 3–5 Pirates Dunedin or Kaikoura Masters
+
+(conflicts with Kapiti Masters)
+
+* Martin
+* Linc
+
+Linc and Martin are taking the ferry over on Thursday, in the hope of hitting the slopes Friday morning. Post-tournament, we drive to Christchurch, and Martin flies home from there, while Lincoln goes to seek more snow.
+

diff --git a/Intraclub.mdwn b/Intraclub.mdwn
index bf1ec05..31dda65 100644
--- a/Intraclub.mdwn
+++ b/Intraclub.mdwn
@@ -45,14 +45,14 @@ ultimately influence the play format.
 * All 4 courts get booked out (speak with Club Captain
 or Squash Captain for help to book if needed).
 
-* Form 8 teams so all courts are used, otherwise go with
-6 teams and leave 1 court free for bookings
+* Teams should be 4–6 players, meaning 4–6 games a night.
 
-  * 32 = 8 teams of 4
+* The number of teams will depend on the number of weeks the competition runs:
 
-  * 40 = 8 teams of 5
-
-  * 48 = 8 teams of 6
+  * 4 teams → 4 draw → 3 weeks
+  * 5 teams → 5 draw → 4 weeks
+  * 6 teams → 6 draw → 5 weeks (or 3 weeks with type B/C)
+  * 8 teams → 8 draw → 7 weeks, or 3 weeks Swiss
 
 * If numbers don’t work out, we try to encourage a few
 more players we know to register, speak to those who are
@@ -86,6 +86,12 @@ if more than 4 players per team)
   * Best of 3 (fastest time wise but often over too
 quickly for lower graded players)
 
+## TournamentControl
+
+The way to put this into TournamentControl is by creating a div for every player in a team, i.e. if teams are 5 players, create 5 divs. In each div, there'll then be all the players at that seed from all the teams, and now it's just a round-robin within each div.
+
+It's a bit finnicky to get this set up because you basically have to hand-craft an iSquash draws export, but it's doable…
+
 ## Last Night : Food, drinks & recognition
 
 On the last night, we encourage people to stay around

diff --git a/TC/MakingDraws.mdwn b/TC/MakingDraws.mdwn
index 0c67b04..7ca64ed 100644
--- a/TC/MakingDraws.mdwn
+++ b/TC/MakingDraws.mdwn
@@ -14,6 +14,13 @@ to deal with, it may be necessary to draft up some draws at random times
 beforehand, to identify holes that may need to be plugged e.g. by moving
 people over from the waiting list, and inviting other players.
 
+## Applying for a TournamentControl event
+
+Now is a good time to [apply for a TournamentControl
+event](https://tournamentcontrol.dtkapiti.co.nz/request/). Thorndon has an
+unlimited plan, so you can add notifications, and avoid payment. You also
+don't need to specify a public IP address.
+
 ## Seeding registrations
 
 Strictly speaking, draws are made in decreasing order of grading points at the

diff --git a/LockdownVideoWorkouts.mdwn b/LockdownVideoWorkouts.mdwn
index f6a8103..cfebf47 100644
--- a/LockdownVideoWorkouts.mdwn
+++ b/LockdownVideoWorkouts.mdwn
@@ -11,7 +11,7 @@ Here are the exercises:
 |----|-------|------------------------|--------------------------|
 | 1. | Arms  | Push-ups               | Pull-ups under the table |
 | 2. | Legs  | High knees, butt kicks | Knees to chest jumps     |
-| 3. | Core  | Plank                  | Side-plank left          |
+| 3. | Core  | Plank                  | Side-plank left & right  |
 | 4. | Arms  | Dips                   | Pike pushes              |
 | 5. | Legs  | Box jumps              | Jump lunges              |
 | 6. | Core  | Crunches or sit-ups    | Burpies                  |

diff --git a/index.mdwn b/index.mdwn
index 749ec63..07ed106 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -74,7 +74,7 @@ coming up. You can [subscribe at this link](http://eepurl.com/HsUpz), and also
 [view past
 issues](https://us7.campaign-archive.com/home/?u=d6baf37078f25e832e9c4f904&id=208a4ee0e4).
 If you have something you'd like to add to the next issue, [drop us a
-line](mailto:squash@thorndonclub.co.nz).
+line](mailto:squashnews@thorndonclub.co.nz).
 
 Many of us also hang out in an online chat group, using the [Element
 Messenger](https://element.io/get-started). We chose this over Whatsapp,

diff --git a/index.mdwn b/index.mdwn
index bc41473..749ec63 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -60,7 +60,7 @@ Our constitution only has room for one squash club captain, but until we get a c
 | Welcoming committee   | Shanti Spendiff   | 021566036  | welcome@thorndonclub.co.nz    |
 | Club nights           | Christine Rukuwai | 0272527593 | christine.rukuwai@hotmail.com |
 |                       | Paras Khanna      | 0204727270 | paras.khanna87@gmail.com      |
-| Newsletter            | Martin Krafft     | 0211100938 | squash@thorndonclub.co.nz     |
+| Newsletter            | Martin Krafft     | 0211100938 | squashnews@thorndonclub.co.nz     |
 | Tournament control    | Martin Krafft     | 0211100938 | squashtc@thorndonclub.co.nz   |
 | Miscellanous & sundry | Martin Krafft     | 0211100938 | squash@thorndonclub.co.nz     |
 

diff --git a/local.css b/local.css
index 6ae0ed2..9605440 100644
--- a/local.css
+++ b/local.css
@@ -49,3 +49,37 @@ blockquote {
   font-style: italic;
   font-family: serif;
 }
+
+/* Dark mode. From
+ * https://ar.al/2021/08/24/implementing-dark-mode-in-a-handful-of-lines-of-css-with-css-filters/ */
+@media (prefers-color-scheme: dark) {
+  /* Set an off-white background and invert all elements
+      without altering their hue. */
+  html {
+    background: #eee;
+    filter: invert(100%) hue-rotate(180deg);
+  }
+
+  /* Optical adjustments. */
+
+  /* Do not invert media (revert the invert). */
+  img, video, iframe {
+    filter: invert(100%) hue-rotate(180deg);
+  }
+
+  /* Improve contrast on icons. */
+  .icon {
+    filter: invert(15%) hue-rotate(180deg);
+  }
+
+  /* Re-enable code block backgrounds. */
+  pre {
+    filter: invert(6%);
+  }
+
+  /* Improve contrast on list item markers. */
+  li::marker {
+    color: #666;
+  }
+}
+

diff --git a/index.mdwn b/index.mdwn
index 5024c84..bc41473 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -83,7 +83,8 @@ Element is independent. You can use it on your phone, install it on your
 desktop/laptop, and even run it straight from the browser, or any combination
 thereof. Visit [this link](https://matrix.to/#/#thorndon-squash:madduck.net)
 to get started, or just download the app, sign up for an account, and join
-`#thorndon-squash:madduck.net`.
+`#thorndon-squash:madduck.net`. There is also a women-only group, to which you
+need to get invited.
 
 ## How-to's & documentation
 

diff --git a/index.mdwn b/index.mdwn
index d9a32a6..5024c84 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -54,6 +54,7 @@ Our constitution only has room for one squash club captain, but until we get a c
 
 | Role                  | Name              | Phone      | Email                         |
 |-----------------------|-------------------|------------|-------------------------------|
+| Membership & grading  | Brad Watts        | 0273905892 | info@thorndonclub.co.nz       |
 | Interclub convenor    | Josie Grover      | 0279686450 | interclub@thorndonclub.co.nz  |
 | Intraclub convenor    | Shanti Spendiff   | 021566036  | intraclub@thorndonclub.co.nz  |
 | Welcoming committee   | Shanti Spendiff   | 021566036  | welcome@thorndonclub.co.nz    |

diff --git a/index.mdwn b/index.mdwn
index f4bbf89..d9a32a6 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -59,12 +59,31 @@ Our constitution only has room for one squash club captain, but until we get a c
 | Welcoming committee   | Shanti Spendiff   | 021566036  | welcome@thorndonclub.co.nz    |
 | Club nights           | Christine Rukuwai | 0272527593 | christine.rukuwai@hotmail.com |
 |                       | Paras Khanna      | 0204727270 | paras.khanna87@gmail.com      |
+| Newsletter            | Martin Krafft     | 0211100938 | squash@thorndonclub.co.nz     |
 | Tournament control    | Martin Krafft     | 0211100938 | squashtc@thorndonclub.co.nz   |
 | Miscellanous & sundry | Martin Krafft     | 0211100938 | squash@thorndonclub.co.nz     |
 
 If you have an idea you'd like to see fly, or you would like to get involved, please get in touch with
 us. We run as a do-oracy, meaning that anything is possible if someone is prepared to see it through.
 
+## Communications
+
+There is a semi-regular newsletter on stuff going on at the club, and what's
+coming up. You can [subscribe at this link](http://eepurl.com/HsUpz), and also
+[view past
+issues](https://us7.campaign-archive.com/home/?u=d6baf37078f25e832e9c4f904&id=208a4ee0e4).
+If you have something you'd like to add to the next issue, [drop us a
+line](mailto:squash@thorndonclub.co.nz).
+
+Many of us also hang out in an online chat group, using the [Element
+Messenger](https://element.io/get-started). We chose this over Whatsapp,
+because several of our members do not want to use a Facebook-owned app;
+Element is independent. You can use it on your phone, install it on your
+desktop/laptop, and even run it straight from the browser, or any combination
+thereof. Visit [this link](https://matrix.to/#/#thorndon-squash:madduck.net)
+to get started, or just download the app, sign up for an account, and join
+`#thorndon-squash:madduck.net`.
+
 ## How-to's & documentation
 
 * [[Club nights|ClubNights]]

diff --git a/LockdownVideoWorkouts.mdwn b/LockdownVideoWorkouts.mdwn
new file mode 100644
index 0000000..f6a8103
--- /dev/null
+++ b/LockdownVideoWorkouts.mdwn
@@ -0,0 +1,45 @@
+The following HIIT circuit is designed to be doable without equipment you wouldn't have at home. You mainly need a bit of space around you, and ideally proximity to your dining table and a chair (for dips and pullups), and if if you have any or all of the
+following, get it ready:
+
+* A mat;
+* An object to jump over, such as a shoe box
+* A bench or chair
+
+Here are the exercises:
+
+| #  | Focus | Rounds 1 & 3           | Rounds 2 & 4             |
+|----|-------|------------------------|--------------------------|
+| 1. | Arms  | Push-ups               | Pull-ups under the table |
+| 2. | Legs  | High knees, butt kicks | Knees to chest jumps     |
+| 3. | Core  | Plank                  | Side-plank left          |
+| 4. | Arms  | Dips                   | Pike pushes              |
+| 5. | Legs  | Box jumps              | Jump lunges              |
+| 6. | Core  | Crunches or sit-ups    | Burpies                  |
+
+## Technical setup
+
+Any video conferencing platform works. Ideally, put the workout on the screen and screenshare. This also allows for music to be shared, if people want that.
+
+One person keeps the time with a HIIT app. We've been using 
+[Tabata](https://play.google.com/store/apps/details?id=com.parabolicriver.tsp&hl=en&gl=US),
+configured as follows:
+
+| Setting                | Value           |
+| ---------------------- | --------------- |
+| Initial countdown      | 1 minute        |
+| Warumup interval       | 0               |
+| Exercise interval      | 40 seconds      |
+| Exercise interval beep | Referee whistle |
+| Rest interval          | 20 seconds      |
+| Rest interval beep     | Boxing gong     |
+| Skip last              | yes             |
+| Number of sets         | 6               |
+| Recovery interval      | 1 minute        |
+| Recovery interval beep | Chinese gong    |
+| Number of cycles       | 4               |
+| Cooldown interval      | 0               |
+| Interval beep          | Spors horn      |
+| Three second beep      | Short beep      |
+| Halfway beep           | Jingle bell     |
+
+Bonus points for figuring out how to mirror the phone to the screenshare…

diff --git a/HIIT.mdwn b/HIIT.mdwn
new file mode 100644
index 0000000..c9000a9
--- /dev/null
+++ b/HIIT.mdwn
@@ -0,0 +1,6 @@
+# Thorndon HIIT
+
+[[!wikipedia High-intensity_interval_training desc="HIIT"]] sessions are a great way to build strength and train that little pump in your chest. We've experimented with a number of formats:
+
+* [[Saturday morning sessions|SaturdayMorningSessions]]
+* [[Lockdown video workouts|LockdownVideoWorkouts]]

diff --git a/HIIT.mdwn b/HIIT/SaturdayMorningSessions.mdwn
similarity index 100%
rename from HIIT.mdwn
rename to HIIT/SaturdayMorningSessions.mdwn

diff --git a/index.mdwn b/index.mdwn
index c2cd72c..f4bbf89 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -71,7 +71,7 @@ us. We run as a do-oracy, meaning that anything is possible if someone is prepar
 * [[Interclub]]
 * [[Social Teams League|Intraclub]]
 * [[Running tournaments|TC]]
-* [[HIIT circuits at the club|HIIT]]
+* [[HIIT workouts|HIIT]]
 
 ## Miscellaneous
 

diff --git a/HIIT.mdwn b/HIIT.mdwn
index 3da62fc..38070e7 100644
--- a/HIIT.mdwn
+++ b/HIIT.mdwn
@@ -19,13 +19,13 @@ All equipment is by the lockers, and some of it is in locker #3. The key is betw
 * Wayne's jumping ropes;
 * 2 mats or towels to keep sweat off the court
 * A couple of dumb- and kettlebells
-* Printed signs for the individual stations
+* Printed [[signs for the individual stations|2021-Circuit_at_the_club.odt]]
 * A phone to run the timer app (see below)
 * Speakers connected to the phone
 
 ## App and music
 
-There are plenty of apps for HIIT out there; We've been using Tabata, configured as follows:
+There are plenty of apps for HIIT out there; We've been using [Tabata](https://play.google.com/store/apps/details?id=com.parabolicriver.tsp&hl=en&gl=US), configured as follows:
 
 | Setting                | Value           |
 | ---------------------- | --------------- |

diff --git a/HIIT/2021-Circuit_at_the_club.odt b/HIIT/2021-Circuit_at_the_club.odt
new file mode 100644
index 0000000..5a69ca4
Binary files /dev/null and b/HIIT/2021-Circuit_at_the_club.odt differ

diff --git a/HIIT.mdwn b/HIIT.mdwn
new file mode 100644
index 0000000..3da62fc
--- /dev/null
+++ b/HIIT.mdwn
@@ -0,0 +1,81 @@
+# Running HIIT circuits at Thorndon Club
+
+## Basics
+
+The standard circuits we've been doing take about 45 minutes, so courts 1&2 need to be booked accordingly, and longer if there are drills afterwards.
+
+A full circuit consists of 18 stations, and we cycle through these twice, for a total of 36. These are done in sets of six, with a minute of rest in between two sets. Each set consists of 6 exercises to be done for a consistent 45 seconds, followed by 15 seconds to change stations.
+
+It generally takes about 15 minutes to set up, and less if people are helping. The best way to get people engaged is to ensure they know where to get the equipments, and give them station signs, which include setup information. Stations 1–5, 6–12, and 13–18 are a good way to partition the tasks if required, or let people figure it out for themselves.
+
+## Equipment
+
+All equipment is by the lockers, and some of it is in locker #3. The key is between sauna and wall. You will need:
+
+* 4 racquets (spare racquets are upstairs in the bucket by the HelloClub kiosk);
+* The red bag containing ladder, cones, and jump bars;
+* Wayne's battle rope;
+* Martin's TRX;
+* Wayne's jumping ropes;
+* 2 mats or towels to keep sweat off the court
+* A couple of dumb- and kettlebells
+* Printed signs for the individual stations
+* A phone to run the timer app (see below)
+* Speakers connected to the phone
+
+## App and music
+
+There are plenty of apps for HIIT out there; We've been using Tabata, configured as follows:
+
+| Setting                | Value           |
+| ---------------------- | --------------- |
+| Initial countdown      | 1 minute        |
+| Warumup interval       | 0               |
+| Exercise interval      | 45 seconds      |
+| Exercise interval beep | Referee whistle |
+| Rest interval          | 15 seconds      |
+| Rest interval beep     | Boxing gong     |
+| Skip last              | yes             |
+| Number of sets         | 6               |
+| Recovery interval      | 1 minute        |
+| Recovery interval beep | Chinese gong    |
+| Number of cycles       | 6               |
+| Cooldown interval      | 0               |
+| Interval beep          | Spors horn      |
+| Three second beep      | Short beep      |
+| Halfway beep           | Jingle bell     |
+
+It helps to have speakers so that everyone hears the beeps.
+
+And when you have speakers, you clearly need music. Fast electronic music works well (such as Trance, Underworld, Nine Inch Nails, Chemical Brothers), but surely Metal, and other genres will also do, even disco.
+
+## Assigning people to starting stations, and kicking it off
+
+The circuit has 18 stations and can thus accomodate at most 18 people at a time.
+
+1. Pick someone at random and assign the person to station 1;
+2. Pick someone else at random, assign to station 2. Tell person at station 1 to follow this person;
+3. Assign someone to 3, tell person at 2 to follow them, etc.
+4. Put yourself last, which means you'll be leading.
+5. Start the app countdown, which sets off the 1 minute initial countdown, allowing people to find their stations and get ready.
+6. At 35 seconds to go, point out the mid-way jingle the app is playing.
+7. Work hard…
+
+## Drills afterwards
+
+Drills on the courts afterwards might include:
+
+* Matchplay on court 1 (2–4 on court depending on numbers)
+* Drills with 2–4 people on court. If there are 3 people, the 3rd just hits length on the other wall. With 4 people, each pair does the same drill on their half. **Important to emphasise that when the ball crosses the middle line, you wait until the other ralley has finished!**. Rotate every couple of ralleys. Drills include:
+    * Channels/lanes long only
+    * Channels/lanes with full length, i.e. including shorts
+    * Drop feeds from the back, drives by the person up front
+    * Feeds from the back, volleys to the back by the person up front
+    * Two people boasting or dropping, one person driving or playing a cross lob that has to touch the side wall
+* Match play with twists, i.e. any combination of:
+    * An unforced error (or just hitting the tin, and serving out) yields -2 or -3 or *even resets score to 0*;
+    * Losing the point at 3, 6 or 10 points means going back to the previous level, i.e. 10→6, 6→3, 3→0. Losing again means down another level;
+    * Reaching the back wall immediately scores a point;
+    * Touching the side wall before the front wall on a straight drive immediately loses you the ralley;
+    * The service box is always out;
+* 10-AB — King/Queen of the court with every ralley scoring, wherein a player upon reaching 10 has to then beat all the other players in a row (10A, 10B, …), and failing to do so will reset them to 7.
diff --git a/index.mdwn b/index.mdwn
index 6bbb56b..c2cd72c 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -71,6 +71,7 @@ us. We run as a do-oracy, meaning that anything is possible if someone is prepar
 * [[Interclub]]
 * [[Social Teams League|Intraclub]]
 * [[Running tournaments|TC]]
+* [[HIIT circuits at the club|HIIT]]
 
 ## Miscellaneous
 

diff --git a/index.mdwn b/index.mdwn
index 59a28f6..6bbb56b 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -45,8 +45,8 @@ future to squash in New Zealand, and maybe in other places, too.
 [[!toggle id="wiki" text="Hide"]]
 """]]
 
-Anyone can edit the information here, just by **clicking** edit at the
-top and on the right. Let's keep this information alive, together.
+Anyone can edit the information here, just by **clicking edit at the
+top right**. Let's keep this information alive, together.
 
 ## The Team
 

diff --git a/index.mdwn b/index.mdwn
index 41ae0e1..59a28f6 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -45,6 +45,9 @@ future to squash in New Zealand, and maybe in other places, too.
 [[!toggle id="wiki" text="Hide"]]
 """]]
 
+Anyone can edit the information here, just by **clicking** edit at the
+top and on the right. Let's keep this information alive, together.
+
 ## The Team
 
 Our constitution only has room for one squash club captain, but until we get a chance to change that, at [Thorndon](https://thorndonsquash.co.nz) there's a team running Everything Squash:

diff --git a/index.mdwn b/index.mdwn
index dcbf12f..41ae0e1 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,4 +1,4 @@
-# Welcome
+# Kia ora!
 
 Welcome to the [Thorndon Squash Club](https://thorndonclub.co.nz) collaborative Wiki, where we amass the knowledge that empowers our volunteers to keep our club throbbing and our community thriving!
 
@@ -45,7 +45,7 @@ future to squash in New Zealand, and maybe in other places, too.
 [[!toggle id="wiki" text="Hide"]]
 """]]
 
-# The Team
+## The Team
 
 Our constitution only has room for one squash club captain, but until we get a chance to change that, at [Thorndon](https://thorndonsquash.co.nz) there's a team running Everything Squash:
 
@@ -62,13 +62,13 @@ Our constitution only has room for one squash club captain, but until we get a c
 If you have an idea you'd like to see fly, or you would like to get involved, please get in touch with
 us. We run as a do-oracy, meaning that anything is possible if someone is prepared to see it through.
 
-# How-to's & documentation
+## How-to's & documentation
 
 * [[Club nights|ClubNights]]
 * [[Interclub]]
 * [[Social Teams League|Intraclub]]
 * [[Running tournaments|TC]]
 
-# Miscellaneous
+## Miscellaneous
 
 * [[Tournament travel|TournamentTravel]]

diff --git a/index.mdwn b/index.mdwn
index b4fac26..dcbf12f 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,7 +1,11 @@
+# Welcome
+
+Welcome to the [Thorndon Squash Club](https://thorndonclub.co.nz) collaborative Wiki, where we amass the knowledge that empowers our volunteers to keep our club throbbing and our community thriving!
+
 [[!toggle  id="wiki" text="What is this? What is a Wiki?"]]
 
 [[!toggleable  id="wiki" text="""
-# What is this? What is a Wiki?
+## What is this? What is a Wiki?
 
 Hi, I'm Martin, Thorndon Squash Club Captain of the 2021 season. When I took
 on this role in 2020, I knew I was only going to be able to do this for a

diff --git a/index.mdwn b/index.mdwn
index bbe007d..b4fac26 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,6 +1,6 @@
 [[!toggle  id="wiki" text="What is this? What is a Wiki?"]]
 
-[[!toggleable  id="ipsum" text="""
+[[!toggleable  id="wiki" text="""
 # What is this? What is a Wiki?
 
 Hi, I'm Martin, Thorndon Squash Club Captain of the 2021 season. When I took
@@ -37,7 +37,8 @@ friendly, approachable communities out there, and I hope there is a long
 future to squash in New Zealand, and maybe in other places, too.
 
 — Kia ora, [Martin](mailto:m@rtin.kiwi), August 2021
-[[!toggle id="ipsum" text="hide"]]
+
+[[!toggle id="wiki" text="Hide"]]
 """]]
 
 # The Team

diff --git a/index.mdwn b/index.mdwn
index 248c310..bbe007d 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,3 +1,6 @@
+[[!toggle  id="wiki" text="What is this? What is a Wiki?"]]
+
+[[!toggleable  id="ipsum" text="""
 # What is this? What is a Wiki?
 
 Hi, I'm Martin, Thorndon Squash Club Captain of the 2021 season. When I took
@@ -34,10 +37,12 @@ friendly, approachable communities out there, and I hope there is a long
 future to squash in New Zealand, and maybe in other places, too.
 
 — Kia ora, [Martin](mailto:m@rtin.kiwi), August 2021
+[[!toggle id="ipsum" text="hide"]]
+"""]]
 
 # The Team
 
-Our constitution only has room for one squash club captain, but until we get a chance to change that, at Thorndon there's a team running everything squash:
+Our constitution only has room for one squash club captain, but until we get a chance to change that, at [Thorndon](https://thorndonsquash.co.nz) there's a team running Everything Squash:
 
 | Role                  | Name              | Phone      | Email                         |
 |-----------------------|-------------------|------------|-------------------------------|

diff --git a/index.mdwn b/index.mdwn
index 155320e..248c310 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,3 +1,40 @@
+# What is this? What is a Wiki?
+
+Hi, I'm Martin, Thorndon Squash Club Captain of the 2021 season. When I took
+on this role in 2020, I knew I was only going to be able to do this for a
+year, before I had to return back home to Germany. I made it my calling to
+extract as much information as I could from Nicole, the previous club captain,
+and long-standing members of the club, such as Brad, and cater the role more
+towards a team effort. Nicole had already floated the idea of a "subcommittee",
+i.e. distributing tasks across multiple people, and I promised I would
+document as much as possible to pass on to my successors, and this is the
+platform where all this information is collected.
+
+This platform is [[!wikipedia Wiki desc="a Wiki"]], which is a very simple
+collaborative tool. It is my theory and hope that its low barrier of entry
+will mean that the information here stays alive, and won't go stale. Anyone
+can edit any page, and there is no login required. Just **click on the Edit
+button at the top right** and you will be presented with text you can edit and
+save. It might take you a second or two to get used to the [[!wikipedia
+Markdown desc="plain-text format used"]], but you may well soon learn to
+appreciate the format as being designed to be human-readable. Head over to the
+[[Sandbox]] to try it out!
+
+If you're thinking right now that this will get abused… well, let it happen.
+Every [[change is logged|RecentChanges]] and can be reverted, and should there
+really ever be a problem with *everyone* able to edit, we can start requiring
+signups. But let's cross that bridge when we get there.
+
+My hope is that this site, which documents how we do things at the [Thorndon
+Squash Club](https://thorndonclub.co.nz) will not only be useful to future
+Thorndon Squash Club Captains, but also to the community beyond. I've only had
+the privilege to be in New Zealand for 4 years, and play squash for 3 of
+those, but I feel comfortable that this is one of the most inclusive,
+friendly, approachable communities out there, and I hope there is a long
+future to squash in New Zealand, and maybe in other places, too.
+
+— Kia ora, [Martin](mailto:m@rtin.kiwi), August 2021
+
 # The Team
 
 Our constitution only has room for one squash club captain, but until we get a chance to change that, at Thorndon there's a team running everything squash:

diff --git a/TC/PlayerComms.mdwn b/TC/PlayerComms.mdwn
index 97d78e0..717bb99 100644
--- a/TC/PlayerComms.mdwn
+++ b/TC/PlayerComms.mdwn
@@ -1,8 +1,10 @@
 # Player communications
 
-> Running a tournament is 10% organisation  
+> Running a tournament  
+> is 10% organisation  
 > and 90% dealing with people  
-> who don't read their email.
+> who don't read their email.  
+> (Martin, 2021)
 
 Good player communications is critical to running a successful tournament.
 This includes regular updates weeks before the event, nudges just before and

diff --git a/TC/ClosingRegistrations.mdwn b/TC/ClosingRegistrations.mdwn
index ab37ea0..bdebdf2 100644
--- a/TC/ClosingRegistrations.mdwn
+++ b/TC/ClosingRegistrations.mdwn
@@ -52,4 +52,4 @@ And now is the right time to drop all registrants an email, to inform them
 that registrations have closed, and ask if any plans have changed, so that you
 can update the list of players right away.
 
-Let's move on to [[Player communications|TC/PlayerComms]].
+Let's move on to [[player communications|TC/PlayerComms]].

diff --git a/TC/MakingDraws.mdwn b/TC/MakingDraws.mdwn
new file mode 100644
index 0000000..0c67b04
--- /dev/null
+++ b/TC/MakingDraws.mdwn
@@ -0,0 +1,165 @@
+# Making the draws
+
+"Making the draws" refers to the process by which players are grouped into
+"draws", i.e. cohorts within which they will play each other. Such cohorts
+vary in size from 4 to 16 or 32 players, though the most common draw size at
+New Zealand tournaments is the 8-draw, followed by 6 & 4, and only tournaments
+with a Sunday finish have 16 or 12, 9 or 5-draws.
+
+Once the draws have been made, it'll become increasingly more difficult to
+make changes between cohorts, and so it is a good idea to delay putting
+significant time into the draws until a week or two before the tournament.
+Nevertheless, depending on the number of registrations, and changes you've had
+to deal with, it may be necessary to draft up some draws at random times
+beforehand, to identify holes that may need to be plugged e.g. by moving
+people over from the waiting list, and inviting other players.
+
+## Seeding registrations
+
+Strictly speaking, draws are made in decreasing order of grading points at the
+time of "seeding the tournament", which is a required step on iSquash prior
+to extracting the list of registrations — where "required" means that you
+should do it, not that iSquash would in any way force you to.
+
+When a player registers for an event, they are entered with their grading
+points at the time of their entry. When you register a player for an event,
+they are actually entered with an effective grading of 0, which is not useful
+at all. Using the "Seed tournament" button in the "Pre-tournament" management
+section on iSquash, you can snapshot the current grading for each registered
+player, to give a consistent picture.
+
+The dialog also gives you a means by which you can override the grading for
+individual players, though this should be used sparringly. Common use cases
+include that a result has been entered wrongly, or too late. It's important to
+note that overriding the grading here only affects the order in which players
+appear in the registration table; It does not actually affect their grading,
+or have any influence on how the results from the tournament get calculated.
+
+Even though draws should be made in decreasing order of grading points,
+tournament control has a bit of wiggle room, which may be required in certain
+cases, usually involving travelling players and time constraints. You are free
+to assign people to draws later in any order you choose, but wiggling their
+grading points at the time of seeding leaves a better paper trail of such
+actions, and ensures reproducible results.
+
+## The Draw Maker
+
+Extracting registrations from iSquash gives you a spreadsheet that you can
+play around with to make the draws, and the [[DrawMaker]] is a spreadsheet
+tool designed to make this process a lot easier, even enjoyable. Once you've
+loaded the registrations and waiting list, you can
+
+* easily pick&choose players into draws;
+* quickly see what contact details you're missing;
+* record player restrictions and analyse the effects these
+  restrictions have on playing times;
+* and also plan out early games to be played on Wednesday and Thursday, so as
+  to minimise the number of games that need to be played on Saturday morning,
+  which is the main bottleneck of any tournament with a Saturday finish;
+* get access to a number of useful and less useful statistics
+
+Usage of the Draw Maker is explained on [[a separate page|DrawMaker]]. For
+now, we'll assume that you've arrived at a final set of player-to-draw
+assignments by any means, and are ready to move on.
+
+## Creating draws in iSquash
+
+Once you're happy with the draws, you need to go back to iSquash to create the
+draws, and assign the players according to what you've designed.
+Unfortunately, this is a cumbersome part of the process, but there is
+unfortunately no way around it, and it's required so that you can later record
+results and propagate them to the grading list.
+
+While you are in the process of creating draws, it might be a good idea to
+untick "Show under Current Tournaments" in the iSquash settings of the event,
+and only tick that box again when you're done.
+
+Please refer to the [iSquash tournament module
+manual](https://www.squash.org.nz/sit/static/manuals/iSquash_Tournament_Module_Manual.pdf)
+for how to use iSquash to create draws, though the process is pretty
+self-explanatory.
+
+For each draw you create, you have to enter a few pieces of data:
+
+1. The type of draw: Most options here are self-explanatory. The 3 different
+   6-draws are: round-robin, type B, and type C. Type B means that the draw is
+   split into a top and a bottom draw in the first round, and then these play
+   a round-robin within each. Type C means that two round-robins are played
+   across all 6 players (1,4,5 and 2,3,6), and then the #1's play each other,
+   as do the #2's and the #3's. It's a matter of taste which one you'll play,
+   though type C might work best when the draw is very close, i.e. there is
+   not a lot of points between the top and the bottom seed. This cannot be
+   changed later.
+
+2. Gender/sex: This also cannot be changed later. Even if you have one member
+   of the opposite gender/sex play, it needs to be Mixed, and it also needs to
+   be Mixed if you want to include any ungraded/international players.
+
+3. Draw name: Make it short. This is usually of the form "M1", "W2", and "J3".
+   Note that an Open division is usually abbreviated e.g. "MO", but this means
+   that the Open division will show up below the numbered divisions, which is
+   at least aesthetically displeasing. Therefore, considerung using "M0"
+   instead.
+
+4. Draw description: Just spell it out, e.g. "Men's Div 1" or "Women's Open"
+
+5. Draw Round: See manual.
+
+6. Lock Draw: to prevent accidental modifications, tick this when you're done.
+
+## Seeding draws
+
+When you click "Seed Draw" for a draw, you get to fill in the slots with
+players. If your list of registered players is already properly ordered
+(because you (ab)used the registration seeding functionality), then you can
+just pick the top seed and hit "Populate", or make the choices manually.
+
+Whenever you make changes to the players, don't forget to visit the "Matches"
+page for each draw, and hit "Initialize Matches". Yes, it's cumbersome, but
+it's necessary for results entry (and other reasons).
+
+Once the draws are all seeded and matches initialised, you can tick the "Show
+under Current Tournaments" box again in the Pre-Tournament settings.
+
+## Scheduling matches
+
+Scheduling matches is the most painful part of tournament organisation, as it
+is literally the attempt to fit a couple of hundred square pegs through round
+holes, with players having restrictions and preferences left and right. One
+way to facilitate this is to flat-out refuse to honour more than one
+restriction (and announce this in the event description).
+
+Another way to make it easier for you is to use
+[TournamentControl](https://tournamentcontrol.dtkapiti.co.nz/)
+instead of iSquash scheduling. TournamentControl also makes running the
+tournament a lot easier, and so that is the natural way, but first, let's draw
+some lines around terms.
+
+1. There is match scheduling, which is absolutely required so that you'll have
+   worked through all the constraints, and your players know when to turn up;
+
+2. And then there is match scheduling on iSquash which is:
+
+   a. an absolute pain in terms of usability;
+   b. not strictly necessary, *if the players know where else to obtain the
+      information*.
+
+If you choose not to schedule matches in iSquash because you cannot be assed
+to do a woefully repetitive and error-prone task by hand, then the diagrams
+players can view for their draws on iSquash won't have times, nor will the
+tables listing their matches. If you can ensure that the players know where
+else to get this information, then it's perfectly fine to forego the pain and
+skip this step.
+
+One way in which the players can find out is through TournamentControl,
+but that does not work on iPhones (August 2021). However, TournamentControl
+lets you export the data, and with a little bit of hackery, it is not only
+possible to publish game times on a web site, it's also conceivably to
+literally squeeze the schedule information into iSquash, but let's not get
+ahead of ourselves (we will cover these topics in [[TCHacks]). For now, let's
+assume you're going to use TournamentControl to schedule matches, and run the
+tournament. There are other solutions, including some that extend to
+scoreboards on the court, but Thorndon has a TournamentControl licence, so
+there…
+
+Let's go [[schedule|Scheduling]]!

diff --git a/TC.mdwn b/TC.mdwn
index 7e9a55e..0408158 100644
--- a/TC.mdwn
+++ b/TC.mdwn
@@ -7,5 +7,5 @@ Running a squash tournament is a multi-stage process, each stage requiring a dif
 3. [[Closing registrations|TC/ClosingRegistrations]]
 4. [[Player communications|TC/PlayerComms]]
 5. [[Making the draws|TC/MakingDraws]]
-6. [[Schedulung|TC/Scheduling]]
+6. [[Scheduling|TC/Scheduling]]
 7. [[Running the tournament|TC/TournamentPhase]]

diff --git a/TC/RegistrationPhase.mdwn b/TC/RegistrationPhase.mdwn
index ac30402..137849c 100644
--- a/TC/RegistrationPhase.mdwn
+++ b/TC/RegistrationPhase.mdwn
@@ -43,6 +43,15 @@ Put anything you want in here, but consider including information such as:
 * Remarks for local players ("may be required to play Wed/Thu")
 * Accomodation offers
 
+One other thing you might want to mention here is how welcoming you are to
+player restrictions. We all lead busy lives, no question, and it's usually not
+a problem if a player cannot play before 8pm on Friday, or not at all on
+Thursday (like all remote players), but if people start to "prefer an early
+game", or have multiple restrictions, your life will get exponentially harder
+with the number of balls you're trying to juggle. It's not uncommon for
+tournament directors to mention in the description that only one restriction
+or preference will be honoured.
+
 It's possible to do a bit of basic formatting using the web page editor, but
 if you want to do this properly, write it up in a text editor, and then
 copy-paste it into the field. This way, you can even insert images, provided

diff --git a/TC.mdwn b/TC.mdwn
index 7dbe8a8..7e9a55e 100644
--- a/TC.mdwn
+++ b/TC.mdwn
@@ -7,4 +7,5 @@ Running a squash tournament is a multi-stage process, each stage requiring a dif
 3. [[Closing registrations|TC/ClosingRegistrations]]
 4. [[Player communications|TC/PlayerComms]]
 5. [[Making the draws|TC/MakingDraws]]
-6. [[Running the tournament|TC/TournamentPhase]]
+6. [[Schedulung|TC/Scheduling]]
+7. [[Running the tournament|TC/TournamentPhase]]
diff --git a/TC/PlanningPhase.mdwn b/TC/PlanningPhase.mdwn
index d768c9d..b23491b 100644
--- a/TC/PlanningPhase.mdwn
+++ b/TC/PlanningPhase.mdwn
@@ -133,3 +133,5 @@ Themes often lead to costume nights, and squash players across New Zealand
 people can come prepared.
 
 Other than that, you are free to do pretty much anything. Get creative.
+
+And now it's time to [[create a tournament and accept registrations|TC/RegistrationPhase]].
diff --git a/TC/PlayerComms.mdwn b/TC/PlayerComms.mdwn
index a5a41d8..97d78e0 100644
--- a/TC/PlayerComms.mdwn
+++ b/TC/PlayerComms.mdwn
@@ -133,3 +133,5 @@ the important few words in each paragraph.
 
 No matter what you do, however, most people will not read the messages, so
 prepare to chase people up, and provide a lot of signage on site.
+
+Next: [[Making the draws|MakingDraws]]
diff --git a/TC/RegistrationPhase.mdwn b/TC/RegistrationPhase.mdwn
index 543f9e3..ac30402 100644
--- a/TC/RegistrationPhase.mdwn
+++ b/TC/RegistrationPhase.mdwn
@@ -105,3 +105,8 @@ If your players often travel to other clubs, make sure they take some
 printouts with them.
 
 Colour printing can be done quite easily at e.g. the Warehouse Stationary.
+
+## Keep a watch
+
+From now on, it's a good idea to check your registrations every couple of
+weeks, then days, because at some point, you'll have to [[close registrations|TC/ClosingRegistrations]].

diff --git a/Club_nights.mdwn b/ClubNights.mdwn
similarity index 100%
rename from Club_nights.mdwn
rename to ClubNights.mdwn
diff --git a/Tournament_travel.mdwn b/TournamentTravel.mdwn
similarity index 100%
rename from Tournament_travel.mdwn
rename to TournamentTravel.mdwn
diff --git a/index.mdwn b/index.mdwn
index 1af3520..155320e 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -17,11 +17,11 @@ us. We run as a do-oracy, meaning that anything is possible if someone is prepar
 
 # How-to's & documentation
 
-* [[Club nights]]
+* [[Club nights|ClubNights]]
 * [[Interclub]]
 * [[Social Teams League|Intraclub]]
 * [[Running tournaments|TC]]
 
 # Miscellaneous
 
-* [[Tournament travel]]
+* [[Tournament travel|TournamentTravel]]

diff --git a/Tournament_travel.mdwn b/Tournament_travel.mdwn
index fafa854..7bf9356 100644
--- a/Tournament_travel.mdwn
+++ b/Tournament_travel.mdwn
@@ -1,18 +1,13 @@
 # Upcoming travel
 
-## Aug 20–21 Surf City Open (Gisborne)
-
-(conflicts with Wainuiomata B&Below)
-
-* Martin
-* Kate & Cam?
-
 ## Sep 3–5 Pirates Dunedin or Kaikoura Masters
 
 (conflicts with Kapiti Masters)
 
-* *Martin?*
-* *Linc?*
+* Martin
+* Linc
+
+Linc and Martin are taking the ferry over on Thursday, in the hope of hitting the slopes Friday morning. Post-tournament, we drive to Christchurch, and Martin flies home from there, while Lincoln goes to seek more snow.
 
 ## 15–16 Oct Ossie's Ohakune Open
 
@@ -136,10 +131,6 @@ Heading out on 3 June, 10:20 flight, and returning 7 June 12:30 via Queenstown,
 * Sam & Grace from IB
 * Jack S. from IB
 
-## Jul 8–9 Hawke's Bay Lawn Tennis Open
-
-* *Jess?*
-
 ## Jul 8–9 Greymouth Open [closed, waitlist]
 
 (conflicts with Hutt City Open)
@@ -151,3 +142,10 @@ Current plan is to hitchhike my way down the west coast to the next one. Anyone?
 ## Jul 16–17 Southland Open @ Invercargill
 
 * Martin
+
+## [postponed due to COVID19] Aug 20–21 Surf City Open (Gisborne)
+
+(conflicts with Wainuiomata B&Below)
+
+* Martin
+* Kate & Cam?

diff --git a/index.mdwn b/index.mdwn
index 7d1fcff..1af3520 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,3 +1,20 @@
+# The Team
+
+Our constitution only has room for one squash club captain, but until we get a chance to change that, at Thorndon there's a team running everything squash:
+
+| Role                  | Name              | Phone      | Email                         |
+|-----------------------|-------------------|------------|-------------------------------|
+| Interclub convenor    | Josie Grover      | 0279686450 | interclub@thorndonclub.co.nz  |
+| Intraclub convenor    | Shanti Spendiff   | 021566036  | intraclub@thorndonclub.co.nz  |
+| Welcoming committee   | Shanti Spendiff   | 021566036  | welcome@thorndonclub.co.nz    |
+| Club nights           | Christine Rukuwai | 0272527593 | christine.rukuwai@hotmail.com |
+|                       | Paras Khanna      | 0204727270 | paras.khanna87@gmail.com      |
+| Tournament control    | Martin Krafft     | 0211100938 | squashtc@thorndonclub.co.nz   |
+| Miscellanous & sundry | Martin Krafft     | 0211100938 | squash@thorndonclub.co.nz     |
+
+If you have an idea you'd like to see fly, or you would like to get involved, please get in touch with
+us. We run as a do-oracy, meaning that anything is possible if someone is prepared to see it through.
+
 # How-to's & documentation
 
 * [[Club nights]]

diff --git a/TC/PlayerComms.mdwn b/TC/PlayerComms.mdwn
new file mode 100644
index 0000000..a5a41d8
--- /dev/null
+++ b/TC/PlayerComms.mdwn
@@ -0,0 +1,135 @@
+# Player communications
+
+> Running a tournament is 10% organisation  
+> and 90% dealing with people  
+> who don't read their email.
+
+Good player communications is critical to running a successful tournament.
+This includes regular updates weeks before the event, nudges just before and
+during the tournament, and alerts to changes as they come.
+
+Two primary channels exist: email, and text messages, and you will need both.
+And both need accurate contact details, which is why we start out with…
+
+## Data hygiene
+
+In theory, iSquash holds an email address and mobile phone number for each
+player, and these data are made available to you when people register. So much
+for the theory. The reality is that these data are often outdated, and that
+can be a pain.
+
+Where you discover that these data are out-of-date, please do two things:
+
+1. Edit the player's registration through iSquash for your tournament (List
+   registrations → find player → Edit…) so that the next time you download the
+   registrations table, the data will be accurate.
+
+2. Nudge the player to update their data in their iSquash profile, for future
+   events.
+
+The [[Draw Maker|TC/DrawMaker]] does a fair bit of cleanup on the phone
+numbers, and it is worth the effort to ensure that by the time you're making
+the draws, you have a mobile phone number for each of your players, as well as
+an email address they read. Haha.
+
+## Text messages
+
+In a world of messengers and social media, the most reliable way to get ahold
+of a player in New Zealand is still the good old text message. Most providers
+give you an unlimited amount of those to be sent, and that is good, because
+you will be making use of that *a lot*.
+
+While it's of course possible to send each text message by hand, you'll really
+want a way to automate the sending of bulk messages. Unfortunately, I am not
+aware of a solution that does not involve coding (like I do), but please
+augment this wiki if you figure out ways to automate this.
+
+Use cases for text messages:
+
+- Chase the first bulk email up with a text message to ensure people got the
+  mail, or move it out of spam to increase the likelihood they won't miss
+  the next one;
+- Alert the player to changes, or get their input on what's possible if a
+  change is required;
+- Recruit players.
+
+There is a little trick you can use to get at the iSquash-registered mobile
+phone number (or email) of any player in New Zealand: register them for your
+tournament! Half the time, their number shows up before you even add the
+player, due to the way the system works. And in the cases where only a
+land-line is shown, actually entering the person, downloading the registration
+table, and removing the person again will go completely unnoticed in 99.9% of
+the time. But you know what they say: with great power comes great
+responsibility, so don't abuse this.
+
+## Direct player communications
+
+Once the draws have been made and loaded into [[TournamentControl]], you can
+use the tool itself to send messages to your players. These messages are very
+powerful, as they are individually sent, and can include form fields, such as
+the name, as well as first game time. There is even infrastructure in place to
+get confirmation from a player that they have absorbed the information.
+
+However, as TournamentControl doesn't get used until later in the process of
+organising a tournament, we need another way to send messages.
+
+## Bulk emails, Mautic, MailChimp & Co.
+
+You can send bulk emails either directly from your email programme, or use a
+marketing tool, such as [Mautic](https://mautic.org) or
+[MailChimp](https://mailchimp.com). Sending emails directly is vastly easier
+to do on an infrequent basis (but whenever you do, **remember to [use the Bcc
+field](https://www.rightinbox.com/blog/how-to-use-bcc-in-email)!**).
+
+If you're planning to send out emails on a semi-regular basis, or you run
+multiple events a year, it may well pay off to invest a bit of time into
+setting up a platform better suited for the task. Benefits include better
+email deliverability (though a lot still ends up in spam folders), as well as
+tracking of who opened your messages (though many clients now block this sort
+of tracking).
+
+At Thorndon, we have a free MailChimp subscription to communicate with our
+members. I set up an additional "audience", and imported all the players from
+all our previous tournaments, tagging each contact with a tag to identify the
+source, e.g. `2021-04-open` while importing contacts who played our April 2021
+Open. If you make sure to select the "Update existing contacts" checkbox,
+you'll grow your audience in a smart way, and can later target them
+accordingly.
+
+I also went through the list of contacts and tagged each Thorndon player with
+`thorndon`, and now I can easily send a message to e.g. all Thorndon players
+registered for the April Open by combining the two tags.
+
+So once you've closed registrations, copy-paste the registrations table into
+the Mailchimp contact import tool, select "Update existing contacts", and make
+sure to assign a new tag, e.g. `2021-08-open`. You can do the same for the
+waiting list, using e.g. `2021-08-open-wl`. Now you're set, and you can easily
+send messages, e.g.:
+
+* To `2021-08-open`, announcing that registrations have closed, to please
+    alert of any changes to plans, and to inform you of dietary preferences,
+    and the like;
+* A few weeks from the event, send another message to `2021-08-open`, telling
+    them that the waiting list is filling up, and asking people to let you
+    know if they cannot play anymore. Remember: people will forget they have
+    even registered;
+* Send a message to `2021-08-open-wl` to keep your waiting list people "hot";
+* Announce the draws to `2021-08-open` once they're done, and apologise to
+    your waiting list people, inviting them to your next tournament;
+* Post-tournament, run a survey among players.
+* Etc.…
+
+It is a bit of a pain to keep these tags up-to-date post-import, as changes
+come in. It is possible to automate this through the MailChimp API, but to
+date, nobody has provided the tool for this yet. So, when someone withdraws,
+you should manually remove the `2021-08-open` tag, and when you move someone
+from the waiting list, swap the `-wl` tag for the main one. That way, you can
+always make sure that you are targetting exactly the right audience.
+
+## Closing words
+
+Finally, remember to keep your messages short, and use bold-face to highlight
+the important few words in each paragraph.
+
+No matter what you do, however, most people will not read the messages, so
+prepare to chase people up, and provide a lot of signage on site.

diff --git a/local.css b/local.css
index 69b0b19..6ae0ed2 100644
--- a/local.css
+++ b/local.css
@@ -1,3 +1,7 @@
+body {
+  font-family: "Lato, Arial, sans-serif";
+}
+
 div.pageheader {
   background: #5cc133;
   color: #fff;
@@ -40,3 +44,8 @@ th {
 tr.even {
   background: #eee;
 }
+
+blockquote {
+  font-style: italic;
+  font-family: serif;
+}

diff --git a/local.css b/local.css
index a8710d6..69b0b19 100644
--- a/local.css
+++ b/local.css
@@ -3,6 +3,11 @@ div.pageheader {
   color: #fff;
 }
 
+#pagebody {
+  max-width: 50em;
+  margin: 0 auto;
+}
+
 h1 {
   font-weight: bold;
   font-size: 130%;

diff --git a/local.css b/local.css
index d86565b..a8710d6 100644
--- a/local.css
+++ b/local.css
@@ -8,6 +8,14 @@ h1 {
   font-size: 130%;
 }
 
+h1, h2 {
+  border-bottom: 2px solid #5cc133;
+}
+
+h3, h4 {
+  border-bottom: 1px solid #5cc133;
+}
+
 table {
   border: 1px #aaa solid;
   border-collapse: collapse;

diff --git a/local.css b/local.css
index b84a904..d86565b 100644
--- a/local.css
+++ b/local.css
@@ -1,198 +1,3 @@
-/*	lessish stylesheet for ikiwiki
-	responsive styles based on the Less CSS Framework
-	version 0.1 - 29 June 2012 
-	https://github.com/spiffin/ikiwiki_lessish */
-
-/*	Less Framework 4
-	http://lessframework.com
-	by Joni Korpi
-	License: http://opensource.org/licenses/mit-license.php	*/
-
-/*	Typography presets
-	------------------	*/
-
-.gigantic {
-	font-size: 110px;
-	line-height: 120px;
-	letter-spacing: -2px;
-}
-
-.huge, h1 {
-	font-size: 52px;
-	line-height: 61px;
-	letter-spacing: -1px;
-}
-
-.large, h2 {
-	font-size: 42px;
-	line-height: 48px;
-}
-
-.bigger, h3 {
-	font-size: 26px;
-	line-height: 36px;
-}
-
-.big, h4 {
-	font-size: 22px;
-	line-height: 30px;
-}
-
-body {
-	font: 1.25em/150% Georgia, serif;
-}
-
-.small, small {
-	font-size: 13px;
-	line-height: 18px;
-}
-
-/* Selection colours (easy to forget) */
-
-::selection 	 	{background: rgb(255,255,158);}
-::-moz-selection 	{background: rgb(255,255,158);}
-img::selection 		{background: transparent;}
-img::-moz-selection	{background: transparent;}
-body {-webkit-tap-highlight-color: rgb(255,255,158);}
-
-/*		Default Layout: 992px. 
-		Gutters: 24px.
-		Outer margins: 48px.
-		Leftover space for scrollbars @1024px: 32px.
--------------------------------------------------------------------------------
-cols    1     2      3      4      5      6      7      8      9      10
-px      68    160    252    344    436    528    620    712    804    896    */
-
-body {
-	width: 896px;
-	padding: 72px 48px 84px;
-	margin: 0 auto;
-	color: rgb(60,60,60);
-	-webkit-text-size-adjust: 100%; /* Stops Mobile Safari from auto-adjusting font-sizes */
-}
-
-/*		Tablet Layout: 768px.
-		Gutters: 24px.
-		Outer margins: 28px.
-		Inherits styles from: Default Layout.
------------------------------------------------------------------
-cols    1     2      3      4      5      6      7      8
-px      68    160    252    344    436    528    620    712    */
-
-@media only screen and (min-width: 768px) and (max-width: 991px) {
-	
-	body {
-		width: 712px;
-		padding: 48px 28px 60px;
-	}
-}
-
-/*		Mobile Layout: 320px.
-		Gutters: 24px.
-		Outer margins: 34px.
-		Inherits styles from: Default Layout.
----------------------------------------------
-cols    1     2      3
-px      68    160    252    */
-
-@media only screen and (max-width: 767px) {
-	
-	body {
-		width: 252px;
-		padding: 48px 34px 60px;
-	}
-	
-}
-
-/*		Wide Mobile Layout: 480px.
-		Gutters: 24px.
-		Outer margins: 22px.
-		Inherits styles from: Default Layout, Mobile Layout.
-------------------------------------------------------------
-cols    1     2      3      4      5
-px      68    160    252    344    436    */
-
-@media only screen and (min-width: 480px) and (max-width: 767px) {
-	
-	body {
-		width: 436px;
-		padding: 36px 22px 48px;
-	}
-	
-}
-
-/*	End Less
-	------	*/
-
-.header {
-	font-weight: normal;
-	font-size: 200%;
-}
-
-h1, h2, h3, h4 { font-weight: normal; margin: 10px 0 -10px; }
-
-p + p { margin-top: 8px; }
-
-a:link { text-decoration: underline; color: #59c903; }
-a:visited { text-decoration: underline; color: #5d9a20; }
-a:hover { background: #efefef; text-decoration: none; color: #333; }
-a:active { background: #efefef; text-decoration: underline; color: #00ff00; }
-
-hr { border: 0; height: 1px; color: #333; margin: 10px 0; background-color: #666; }
-
-.actions ul {
-	margin: 0 0 10px;
-	padding: 16px .8em 10px 0px;
-	height: auto;
-}
-.actions li {
-	padding: 0 .5em 0 0;
-}
-
-.pagedate,
-.pagelicense,
-.pagecopyright {
-	font-size: small;
-	color: #ccc;
-}
-
-blockquote {
-	font-style: italic;
-}
-
-code {
-	font: 14px Monaco, Courier, monospace;
-	line-height: 24px;
-}
-
-textarea {
-	font: 12.5px Monaco, monospace;
-	background: #232323;
-	color: #a7ed61;
-}
-
-.pageheader #otherlanguages,
-.pageheader .actions ul {
-	border-bottom: 1px solid #666;
-}
-
-#pageinfo {
-	margin: 1em 0;
-	border-top: 1px solid #666;
-}
-
-.notebox {
-	color: #333 !important;
-}
-
-.sidebar {
-	border: 1px solid #aaa;
-}
-
-input#searchbox {
-	background: none;
-}
-

(Diff truncated)

diff --git a/local.css b/local.css
index d86565b..b84a904 100644
--- a/local.css
+++ b/local.css
@@ -1,3 +1,198 @@
+/*	lessish stylesheet for ikiwiki
+	responsive styles based on the Less CSS Framework
+	version 0.1 - 29 June 2012 
+	https://github.com/spiffin/ikiwiki_lessish */
+
+/*	Less Framework 4
+	http://lessframework.com
+	by Joni Korpi
+	License: http://opensource.org/licenses/mit-license.php	*/
+
+/*	Typography presets
+	------------------	*/
+
+.gigantic {
+	font-size: 110px;
+	line-height: 120px;
+	letter-spacing: -2px;
+}
+
+.huge, h1 {
+	font-size: 52px;
+	line-height: 61px;
+	letter-spacing: -1px;
+}
+
+.large, h2 {
+	font-size: 42px;
+	line-height: 48px;
+}
+
+.bigger, h3 {
+	font-size: 26px;
+	line-height: 36px;
+}
+
+.big, h4 {
+	font-size: 22px;
+	line-height: 30px;
+}
+
+body {
+	font: 1.25em/150% Georgia, serif;
+}
+
+.small, small {
+	font-size: 13px;
+	line-height: 18px;
+}
+
+/* Selection colours (easy to forget) */
+
+::selection 	 	{background: rgb(255,255,158);}
+::-moz-selection 	{background: rgb(255,255,158);}
+img::selection 		{background: transparent;}
+img::-moz-selection	{background: transparent;}
+body {-webkit-tap-highlight-color: rgb(255,255,158);}
+
+/*		Default Layout: 992px. 
+		Gutters: 24px.
+		Outer margins: 48px.
+		Leftover space for scrollbars @1024px: 32px.
+-------------------------------------------------------------------------------
+cols    1     2      3      4      5      6      7      8      9      10
+px      68    160    252    344    436    528    620    712    804    896    */
+
+body {
+	width: 896px;
+	padding: 72px 48px 84px;
+	margin: 0 auto;
+	color: rgb(60,60,60);
+	-webkit-text-size-adjust: 100%; /* Stops Mobile Safari from auto-adjusting font-sizes */
+}
+
+/*		Tablet Layout: 768px.
+		Gutters: 24px.
+		Outer margins: 28px.
+		Inherits styles from: Default Layout.
+-----------------------------------------------------------------
+cols    1     2      3      4      5      6      7      8
+px      68    160    252    344    436    528    620    712    */
+
+@media only screen and (min-width: 768px) and (max-width: 991px) {
+	
+	body {
+		width: 712px;
+		padding: 48px 28px 60px;
+	}
+}
+
+/*		Mobile Layout: 320px.
+		Gutters: 24px.
+		Outer margins: 34px.
+		Inherits styles from: Default Layout.
+---------------------------------------------
+cols    1     2      3
+px      68    160    252    */
+
+@media only screen and (max-width: 767px) {
+	
+	body {
+		width: 252px;
+		padding: 48px 34px 60px;
+	}
+	
+}
+
+/*		Wide Mobile Layout: 480px.
+		Gutters: 24px.
+		Outer margins: 22px.
+		Inherits styles from: Default Layout, Mobile Layout.
+------------------------------------------------------------
+cols    1     2      3      4      5
+px      68    160    252    344    436    */
+
+@media only screen and (min-width: 480px) and (max-width: 767px) {
+	
+	body {
+		width: 436px;
+		padding: 36px 22px 48px;
+	}
+	
+}
+
+/*	End Less
+	------	*/
+
+.header {
+	font-weight: normal;
+	font-size: 200%;
+}
+
+h1, h2, h3, h4 { font-weight: normal; margin: 10px 0 -10px; }
+
+p + p { margin-top: 8px; }
+
+a:link { text-decoration: underline; color: #59c903; }
+a:visited { text-decoration: underline; color: #5d9a20; }
+a:hover { background: #efefef; text-decoration: none; color: #333; }
+a:active { background: #efefef; text-decoration: underline; color: #00ff00; }
+
+hr { border: 0; height: 1px; color: #333; margin: 10px 0; background-color: #666; }
+
+.actions ul {
+	margin: 0 0 10px;
+	padding: 16px .8em 10px 0px;
+	height: auto;
+}
+.actions li {
+	padding: 0 .5em 0 0;
+}
+
+.pagedate,
+.pagelicense,
+.pagecopyright {
+	font-size: small;
+	color: #ccc;
+}
+
+blockquote {
+	font-style: italic;
+}
+
+code {
+	font: 14px Monaco, Courier, monospace;
+	line-height: 24px;
+}
+
+textarea {
+	font: 12.5px Monaco, monospace;
+	background: #232323;
+	color: #a7ed61;
+}
+
+.pageheader #otherlanguages,
+.pageheader .actions ul {
+	border-bottom: 1px solid #666;
+}
+
+#pageinfo {
+	margin: 1em 0;
+	border-top: 1px solid #666;
+}
+
+.notebox {
+	color: #333 !important;
+}
+
+.sidebar {
+	border: 1px solid #aaa;
+}
+
+input#searchbox {
+	background: none;
+}
+

(Diff truncated)

diff --git a/local.css b/local.css
index bf8e7c5..d86565b 100644
--- a/local.css
+++ b/local.css
@@ -1,547 +1,3 @@
-/* ikiwiki style sheet */
-
-/* Note that instead of modifying this style sheet, you can instead edit
- * local.css and use it to override or change settings in this one.
- */
-
-/* html5 compat */
-article,
-header,
-footer,
-nav {
-	display: block;
-}
-
-.header {
-	margin: 0;
-	font-size: 140%;
-	font-weight: bold;
-	line-height: 1em;
-	display: block;
-}
-
-.inlineheader .author {
-	margin: 0;
-	font-size: 112%;
-	font-weight: bold;
-	display: block;
-}
-
-.actions ul {
-	margin: 0;
-	padding: 6px .4em;
-	height: 1em;
-	list-style-type: none;
-}
-.actions li {
-	display: inline;
-	padding: .2em;
-}
-.pageheader .actions ul {
-	border-bottom: 1px solid #000;
-}
-
-.inlinepage .actions ul {
-	border-bottom: 0;
-}
-
-#otherlanguages ul {
-	margin: 0;
-	padding: 6px;
-	list-style-type: none;
-}
-#otherlanguages li {
-	display: inline;
-	padding: .2em .4em;
-}
-.pageheader #otherlanguages {
-	border-bottom: 1px solid #000;
-}
-
-.inlinecontent {
-	margin-top: .4em;
-}
-
-.pagefooter,
-.inlinefooter,
-.comments {
-	clear: both;
-}
-
-#pageinfo {
-	margin: 1em 0;
-	border-top: 1px solid #000;
-}
-
-.tags {
-	margin-top: 1em;
-}
-
-.inlinepage .tags {
-        display: inline;
-}
-
-.mapparent {
-	text-decoration: none;
-}
-
-.img caption {
-	font-size: 80%;
-	caption-side: bottom;
-	text-align: center;
-}
-
-img.img {
-	margin: 0.5ex;
-}
-
-.align-left {
-	float:left;
-}
-
-.align-right {
-	float:right;
-}
-
-#backlinks {
-	margin-top: 1em;
-}
-
-#searchform {
-	display: inline;
-	float: right;
-}
-
-#editcontent {
-	width: 98%;
-}
-
-.editcontentdiv {
-	width: auto;
-	overflow: auto;
-}
-
-img {
-	border-style: none;
-}
-
-pre {
-	overflow: auto;
-}
-
-div.recentchanges {
-	border-style: solid;
-	border-width: 1px;
-	overflow: auto;
-	width: auto;
-	clear: none;
-	background: #eee;
-	color: black !important;
-}
-.recentchanges .metadata {
-	padding: 0px 0.5em;
-}
-.recentchanges .changelog {
-	font-style: italic;
-	clear: both;
-	display: block;
-	padding: 1px 2px;
-	background: white !important;
-	color: black !important;
-}
-.recentchanges .desc {
-	display: none;
-}
-.recentchanges .diff {
-	display: none;
-}
-.recentchanges .committer {
-	float: left;
-	margin: 0;
-	width: 40%;
-}
-.recentchanges .committype {
-	float: left;
-	margin: 0;
-	width: 5%;
-	font-size: small;
-}
-.recentchanges .changedate {
-	float: left;
-	margin: 0;
-	width: 35%;
-	font-size: small;
-}
-.recentchanges .pagelinks,
-.recentchanges .revert {
-	float: right;
-	margin: 0;
-	width: 60%;
-}
-
-.blogform, #blogform {
-	padding: 10px 10px;
-	border: 1px solid #aaa;
-	background: #eee;
-	color: black !important;
-	width: auto;
-	overflow: auto;
-}
-
-.inlinepage {
-	padding: 10px 10px;
-	border: 1px solid #aaa;
-	overflow: auto;
-}

(Diff truncated)

diff --git a/local.css b/local.css
index d86565b..bf8e7c5 100644
--- a/local.css
+++ b/local.css
@@ -1,3 +1,547 @@
+/* ikiwiki style sheet */
+
+/* Note that instead of modifying this style sheet, you can instead edit
+ * local.css and use it to override or change settings in this one.
+ */
+
+/* html5 compat */
+article,
+header,
+footer,
+nav {
+	display: block;
+}
+
+.header {
+	margin: 0;
+	font-size: 140%;
+	font-weight: bold;
+	line-height: 1em;
+	display: block;
+}
+
+.inlineheader .author {
+	margin: 0;
+	font-size: 112%;
+	font-weight: bold;
+	display: block;
+}
+
+.actions ul {
+	margin: 0;
+	padding: 6px .4em;
+	height: 1em;
+	list-style-type: none;
+}
+.actions li {
+	display: inline;
+	padding: .2em;
+}
+.pageheader .actions ul {
+	border-bottom: 1px solid #000;
+}
+
+.inlinepage .actions ul {
+	border-bottom: 0;
+}
+
+#otherlanguages ul {
+	margin: 0;
+	padding: 6px;
+	list-style-type: none;
+}
+#otherlanguages li {
+	display: inline;
+	padding: .2em .4em;
+}
+.pageheader #otherlanguages {
+	border-bottom: 1px solid #000;
+}
+
+.inlinecontent {
+	margin-top: .4em;
+}
+
+.pagefooter,
+.inlinefooter,
+.comments {
+	clear: both;
+}
+
+#pageinfo {
+	margin: 1em 0;
+	border-top: 1px solid #000;
+}
+
+.tags {
+	margin-top: 1em;
+}
+
+.inlinepage .tags {
+        display: inline;
+}
+
+.mapparent {
+	text-decoration: none;
+}
+
+.img caption {
+	font-size: 80%;
+	caption-side: bottom;
+	text-align: center;
+}
+
+img.img {
+	margin: 0.5ex;
+}
+
+.align-left {
+	float:left;
+}
+
+.align-right {
+	float:right;
+}
+
+#backlinks {
+	margin-top: 1em;
+}
+
+#searchform {
+	display: inline;
+	float: right;
+}
+
+#editcontent {
+	width: 98%;
+}
+
+.editcontentdiv {
+	width: auto;
+	overflow: auto;
+}
+
+img {
+	border-style: none;
+}
+
+pre {
+	overflow: auto;
+}
+
+div.recentchanges {
+	border-style: solid;
+	border-width: 1px;
+	overflow: auto;
+	width: auto;
+	clear: none;
+	background: #eee;
+	color: black !important;
+}
+.recentchanges .metadata {
+	padding: 0px 0.5em;
+}
+.recentchanges .changelog {
+	font-style: italic;
+	clear: both;
+	display: block;
+	padding: 1px 2px;
+	background: white !important;
+	color: black !important;
+}
+.recentchanges .desc {
+	display: none;
+}
+.recentchanges .diff {
+	display: none;
+}
+.recentchanges .committer {
+	float: left;
+	margin: 0;
+	width: 40%;
+}
+.recentchanges .committype {
+	float: left;
+	margin: 0;
+	width: 5%;
+	font-size: small;
+}
+.recentchanges .changedate {
+	float: left;
+	margin: 0;
+	width: 35%;
+	font-size: small;
+}
+.recentchanges .pagelinks,
+.recentchanges .revert {
+	float: right;
+	margin: 0;
+	width: 60%;
+}
+
+.blogform, #blogform {
+	padding: 10px 10px;
+	border: 1px solid #aaa;
+	background: #eee;
+	color: black !important;
+	width: auto;
+	overflow: auto;
+}
+
+.inlinepage {
+	padding: 10px 10px;
+	border: 1px solid #aaa;
+	overflow: auto;
+}

(Diff truncated)

diff --git a/local.css b/local.css
index b4e119c..d86565b 100644
--- a/local.css
+++ b/local.css
@@ -3,12 +3,6 @@ div.pageheader {
   color: #fff;
 }
 
-div.pageheader,
-#pagebody {
-  max-width: 40em;
-  margin: 0 auto;
-}
-
 h1 {
   font-weight: bold;
   font-size: 130%;

diff --git a/local.css b/local.css
index 42dbcb9..b4e119c 100644
--- a/local.css
+++ b/local.css
@@ -4,7 +4,7 @@ div.pageheader {
 }
 
 div.pageheader,
-div.pagebody {
+#pagebody {
   max-width: 40em;
   margin: 0 auto;
 }

diff --git a/local.css b/local.css
index d86565b..42dbcb9 100644
--- a/local.css
+++ b/local.css
@@ -3,6 +3,12 @@ div.pageheader {
   color: #fff;
 }
 
+div.pageheader,
+div.pagebody {
+  max-width: 40em;
+  margin: 0 auto;
+}
+
 h1 {
   font-weight: bold;
   font-size: 130%;

diff --git a/local.css b/local.css
index d8d0d2c..d86565b 100644
--- a/local.css
+++ b/local.css
@@ -19,8 +19,9 @@ td, th {
 }
 
 th {
+  background: #5cc133;
+  color: #fff;
   font-weight: bold;
-  background: #aaa;
 }
 
 tr.even {

diff --git a/local.css b/local.css
index 70ef952..d8d0d2c 100644
--- a/local.css
+++ b/local.css
@@ -20,6 +20,7 @@ td, th {
 
 th {
   font-weight: bold;
+  background: #aaa;
 }
 
 tr.even {

diff --git a/local.css b/local.css
index 8ad8d1a..70ef952 100644
--- a/local.css
+++ b/local.css
@@ -13,15 +13,15 @@ table {
   border-collapse: collapse;
 }
 
-thead td {
+td, th {
+  border: 1px #ddd solid;
+  padding: 0.5em;
+}
+
+th {
   font-weight: bold;
 }
 
 tr.even {
   background: #eee;
 }
-
-td {
-  border: 1px #ddd solid;
-  padding: 0.5em;
-}

diff --git a/local.css b/local.css
index 9061051..8ad8d1a 100644
--- a/local.css
+++ b/local.css
@@ -7,3 +7,21 @@ h1 {
   font-weight: bold;
   font-size: 130%;
 }
+
+table {
+  border: 1px #aaa solid;
+  border-collapse: collapse;
+}
+
+thead td {
+  font-weight: bold;
+}
+
+tr.even {
+  background: #eee;
+}
+
+td {
+  border: 1px #ddd solid;
+  padding: 0.5em;
+}

diff --git a/TC/PlanningPhase.mdwn b/TC/PlanningPhase.mdwn
index 6245a5d..d768c9d 100644
--- a/TC/PlanningPhase.mdwn
+++ b/TC/PlanningPhase.mdwn
@@ -1,5 +1,3 @@
-[[!sidebar content="[[!toc]]"]]
-
 # Planning to run a tournament
 
 Running a tournament is both fun, and also quite a bit of work. However, as with most things, the better the plan, the better the outcome, and that includes lower stress levels.

diff --git a/TC.mdwn b/TC.mdwn
index 7030206..7dbe8a8 100644
--- a/TC.mdwn
+++ b/TC.mdwn
@@ -4,5 +4,7 @@ Running a squash tournament is a multi-stage process, each stage requiring a dif
 
 1. [[Initial planning|TC/PlanningPhase]]
 2. [[Advertising and registrations|TC/RegistrationPhase]]
-3. [[Making the draws|TC/MakingDraws]]
-4. [[Running the tournament|TC/TournamentPhase]]
+3. [[Closing registrations|TC/ClosingRegistrations]]
+4. [[Player communications|TC/PlayerComms]]
+5. [[Making the draws|TC/MakingDraws]]
+6. [[Running the tournament|TC/TournamentPhase]]
diff --git a/TC/ClosingRegistrations.mdwn b/TC/ClosingRegistrations.mdwn
new file mode 100644
index 0000000..ab37ea0
--- /dev/null
+++ b/TC/ClosingRegistrations.mdwn
@@ -0,0 +1,55 @@
+# Closing registrations
+
+During the [[advertising and registration phase|TC/RegistrationPhase]], it is
+prudent to regularly check the list of registrations, as there is no way to
+limit the number on iSquash, and you don't want to end up with heaps above
+your limit.
+
+It may be a good idea to close registrations at 80–90% capacity, before
+specifically targetting members of your club, or inviting others you'd like to
+play.
+
+There are two ways to closing registrations:
+
+1. Noting that the event has closed, and downloading the registrations so as to
+   snapshot the list of registered players at the time;
+2. Hiding the event from iSquash, and putting a new event in place
+   which serves as a waiting list.
+
+Both approaches fundamentally serve the same purpose: you get a set list of
+players, and when someone pulls our due to a change of plans, or an injury,
+you will hopefully have another player ready to take their spot. If the draws
+have not been made, this can be any player, but if you've already drafted the
+draws, it pays to have a full waiting list so that there's a higher chance of
+another player in the same grade range able to slot right in.
+
+The first approach is slightly easier at first, but you'll later end up with
+two lists that may diverge. Also, leaving the main event up there means that
+people can just deregister themselves, without you finding out until you
+compare the status quo to the snapshot, and work out the intersection between
+the two sets.
+
+The second approach takes a bit more effort, but it's better in that it keeps
+the list of confirmed registrations separate from the waiting list. Moreover,
+if people want to pull out, they have to do so by letting you know, and you
+can then immediately look into filling their spot.
+
+To hide an event from iSquash, set the "last registration date" property to
+yesterday's date, and create a new event, advertised as "waiting list", into
+which you copy-paste the details from the main event.
+
+The downsides of having a separate event in place as the waiting list are:
+
+* Interested layers might hesitate to sign up to a waiting list, and feel left
+  out.
+* Already registered players *will* re-register on the waiting list, no matter
+  how much you tell them that this is not necessary;
+* Since the event no longer shows up on iSquash along with the yellow star for
+  registered players, people might — no — people *will* forget that they've
+  registered;
+
+And now is the right time to drop all registrants an email, to inform them
+that registrations have closed, and ask if any plans have changed, so that you
+can update the list of players right away.
+
+Let's move on to [[Player communications|TC/PlayerComms]].

diff --git a/TC/RegistrationPhase.mdwn b/TC/RegistrationPhase.mdwn
new file mode 100644
index 0000000..543f9e3
--- /dev/null
+++ b/TC/RegistrationPhase.mdwn
@@ -0,0 +1,107 @@
+# Advertising and registrations
+
+## Creating an iSquash tournament
+
+To begin advertising your tournament, and let people register, you have to
+create a tournament on iSquash, and there is [a whole
+manual](https://www.squash.org.nz/sit/static/manuals/iSquash_Tournament_Module_Manual.pdf)
+available for that. Let us focus in the following on the tricks and
+peculiarities not described therein.
+
+Here is a bit of detail for the different form fields you have to fill in when
+creating a tournament:
+
+| Field                  | Notes                                                                            |
+|------------------------|----------------------------------------------------------------------------------|
+| Code                   | Can be anything, often similar to squash code, e.g. `WNTHSNCTY`                  |
+| Name                   | What shows up in the tournaments listing. 40 characters                          |
+| Description            | Sort of visible when registering, later visible when draws are published         |
+| Detail                 | This is where you advertise all there is to know before registration. See below. |
+| Locations              | All the clubs where this tournament will be played at                            |
+| Organiser              | The person who will receive questions etc.                                       |
+| Dates                  | Usually Friday & Saturday/Sunday, but should be moved to Thu/Wed accordingly     |
+| Start advertising      | Today's date, or maybe a date in the future                                      |
+| Last reg. day          | After this day, the tournament will no longer be visible for registrations       |
+| Scope                  | Limits who can register, usually "Open"                                          |
+| Fees                   | See below                                                                        |
+| Tournament in progress | "Child-safety" to prevent accidental changes                                     |
+| Show tournament        | Shows tournament *as soon as the last reg. day has passed*                       |
+| T&C                    | See below.                                                                       |
+
+Once you hit "save", and as soon as the "start advertising" date is reached,
+people can register for your tournament on iSquash, and you can manually add
+players too (they will not get notified about this…).
+
+### Detailed description
+
+Put anything you want in here, but consider including information such as:
+
+* What is this event?
+* Who can register?
+* When does it finish, and what can players expect?
+* Specific rules, i.e. double-dot & PAR11 also for C-graders, or even everyone
+* Remarks for local players ("may be required to play Wed/Thu")
+* Accomodation offers
+
+It's possible to do a bit of basic formatting using the web page editor, but
+if you want to do this properly, write it up in a text editor, and then
+copy-paste it into the field. This way, you can even insert images, provided
+they reside on some publicly-accessible URL to which you link.
+
+### Tournament fee
+
+Entry fees for tournaments in NZ are generally $35 or $40, which gets used
+for expenses, towards the prize money, as well as food following the
+prize-giving (unless the community provides that).
+
+Generally, people are good at paying their fee on site. Over time, people have
+come up with a number of ways to make this even more likely:
+
+* Early-bird fees, including paying before their first game
+* Providing bank account details (requires consolidation…)
+* Using iSquash to collect payment (reduces the number of people registering
+    just to reserve a spot)
+* Punishing the last person to pay
+* …
+
+Where there is a Juniors division, Juniors are usually charged a lot less (and
+their prizes are a lot lower).
+
+Also, if you want to attract families, consider offering a family entry fee.
+
+It is possible to consider charging e.g. $50 for a tournament, if players get
+more than the usual out.
+
+### Terms & Conditions
+
+Anything you want to put in here that you want your players to abide by
+(though nobody reads this anyway). Here is a standard text:
+
+> Game scores will be reported to iSquash for all games. Please report to TC
+> no later than 15 minutes before your game, and mark/ref the game after
+> yours. You must comply with all Thorndon Health & Safety requirements and
+> the Squash Wellington Code of Conduct while attending this event. If you
+> have any questions please contact our Club Manager.
+
+## Posters & spreading the word
+
+It's a good idea to create a poster for your event, and send it to the other
+clubs for display, as not everyone stays on top of events appearing on
+iSquash. So if you get a poster sent to you, please print it and hang it up,
+too.
+
+The poster should be catchy, and include at least:
+
+* The event name
+* What is this tournament (e.g. "Open")
+* When?
+* Where?
+* Cost, and how to register
+* What to expect (dinner) and bring (costumes…?)
+* Contact details
+* Sponsor logos
+
+If your players often travel to other clubs, make sure they take some
+printouts with them.
+
+Colour printing can be done quite easily at e.g. the Warehouse Stationary.

diff --git a/TC/PlanningPhase.mdwn b/TC/PlanningPhase.mdwn
index 6ec0c82..6245a5d 100644
--- a/TC/PlanningPhase.mdwn
+++ b/TC/PlanningPhase.mdwn
@@ -16,8 +16,54 @@ The answers to these questions will preempt many decisions later in the process,
 
 ## When should this tournament happen?
 
+Tournaments usually take place on Friday and Saturday of any given weekend.
+Some tournaments run until Sunday (see below). Local players are often
+required to play on Thursday already, sometimes even on Wednesday.
+
+The squash season roughly runs from February to October, and the weekend for a
+tournament largely depends on the region's calendar, which is negotiated
+between the clubs for the next season just after each season finishes.
+Therefore, the decision when a tournament should take place happens long
+before the season starts, and involves coordination with the other clubs.
+
+Aspects to consider when selecting/applying for dates are:
+
+* School holidays (will there be enough interest and volunteers?)
+* Public holidays, such as Easter and Queens Birthday Weekend
+* Regional and national events, such as
+  * Senior nationals (usually early July)
+  * Teams nationals (usually late August)
+  * Master nationals (usually late October)
+  * Superchamps regional eliminations (usually late July)
+  * Superchamps nationals (usually late September)
+* Season fringe times may not be as popular with higher players
+* Club champs
+
+For clubs that also have tennis competitions, it may be a good idea to avoid
+conflicting with their events.
+
 ## What players am I targeting?
 
+The most generic tournament format is the "Open", which is open to players of
+all grades. These sometimes favour higher- over lower-graded players by
+selecting the top X players, rather than to choose the first X players to
+register.
+
+Such tournaments have an Open division for the top players (men & women), and
+then spread out lower-graded players across numbered divisions, e.g. "Div 1"
+and "Div 3".
+
+In an effort to not let the A graders steal the show like they might at an
+Open, the so-called "& below" tournaments have become popular, too, and one
+often sees "B & Below", "A2 & Below", and sometimes even "C & Below" events.
+These events do not have an "Open" division, but just start with "Div 1".
+
+The answer to the question what type of tournament to run very much depends on
+the region, and what else is on. In general, tournaments should be "Open",
+especially if they aren't commonly overrun by A-graders. However, if you have
+reason to believe that it would be of motivational value to your players to
+cap the grades at the top, feel free to run a "& Below", as appropriate.
+
 ## Saturday or Sunday finish?
 
 At Thorndon, we generally finish on Saturday night, which translates to better bar sales, and a better vibe throughout the day. The reasons for this are:
@@ -26,7 +72,14 @@ At Thorndon, we generally finish on Saturday night, which translates to better b
 * not having to stay sober that night in preparation of another game on Sunday means there's a better party to be expected;
 * lastly, a tournament takes a toll on organisers and volunteers, but also players. Having Sunday off after a big Saturday allows people to rejoin with their families, and relax.
 
-Finishing on Saturday generally means that everyone gets to play 3 games, i.e. the tournament is confined to 4, 6, and 8 draws. If 5, 12, and 16 draws are desired or needed, then each player has to take to the courts 4 times, and that is unlikely possibe with a Saturday finish.
+Finishing on Saturday generally means that everyone gets to play 3 games, i.e. the tournament is confined to 4, 6, and 8 draws.
+
+If 5, 12, and 16 draws are desired or needed, then each player has to take to
+the courts 4 times, and that is unlikely possibe with a Saturday finish.
+
+Sunday-finish tournaments make most sense if Monday is a public holiday, or if
+a lot of players travel, and you want to give them 4 matches, instead of just
+3, to make it worth their while.
 
 ## How many players can I accommodate?
 
@@ -57,11 +110,28 @@ Finally, if sticking to plan is really a concern, then the match rules can be mo
 
 ### An example: The 2021 August Thorndon Open
 
-At the time of writing, the next Thorndon Open is just 2 weeks away, and we are looking to accommodate 106 players, meaning 53 games in each round. Despite being called the "Thorndon Welcomes the South Island Open", only 22% of the players came from outside the local Wellington region (not including Ōtaki, Kāpiti, Masterton, and Martinborough). Chance also had it that a lot of the divisions would be made up entirely of local people. As a result, 31 round 1 games can be played on Wednesday, and 21 round 2 games on Thursday, leaving only 22 round 1 games for Friday night, and 32 round 2 games for Saturday morning — to be fitted into a 4 hour time slot!
+At the time of writing, the next Thorndon Open is just 2 weeks away, and we
+are looking to accommodate 108 players, meaning 54 games in each round.
+Despite being called the "Thorndon Welcomes the South Island Open", only 26%
+of the players came from outside the local Wellington region (not including
+Ōtaki, Kāpiti, Masterton, and Martinborough). Chance also had it that a lot of
+the divisions would be made up entirely of local people. As a result, 31 round
+1 games can be played on Wednesday & Thursday, and 18 round 2 games on
+Thursday & Friday, leaving only 23 round 1 games for Friday night, and 36
+round 2 games for Saturday morning — to be fitted into a 4.5 hour time slot!
 
 Don't despair, the [[Draw Maker|TC/DrawMaker]] can help juggle all this, but
 only once the registrations roll in and we have some real data to play with.
 
 ## On the subject of themes
 
-tbc.
+Feel free to give your tournament a theme, such as the "Welcomes the South
+Island Open", or the "Sin City Open". The important thing to keep in mind is
+to maintain an inclusive atmosphere, e.g. by highlighting that everyone can
+enter the "South Island" tournament.
+
+Themes often lead to costume nights, and squash players across New Zealand
+*love* to dress up. Just make sure to announce it well ahead of time, so that
+people can come prepared.
+
+Other than that, you are free to do pretty much anything. Get creative.

diff --git a/sidebar.mdwn b/sidebar.mdwn
deleted file mode 100644
index ffc2908..0000000
--- a/sidebar.mdwn
+++ /dev/null
@@ -1 +0,0 @@
-[[!toc levels=2 startlevel=2]]

diff --git a/TC/PlanningPhase.mdwn b/TC/PlanningPhase.mdwn
index c9159f1..6ec0c82 100644
--- a/TC/PlanningPhase.mdwn
+++ b/TC/PlanningPhase.mdwn
@@ -1,3 +1,5 @@
+[[!sidebar content="[[!toc]]"]]
+
 # Planning to run a tournament
 
 Running a tournament is both fun, and also quite a bit of work. However, as with most things, the better the plan, the better the outcome, and that includes lower stress levels.

diff --git a/sidebar.mdwn b/sidebar.mdwn
new file mode 100644
index 0000000..ffc2908
--- /dev/null
+++ b/sidebar.mdwn
@@ -0,0 +1 @@
+[[!toc levels=2 startlevel=2]]

diff --git a/TC/PlanningPhase.mdwn b/TC/PlanningPhase.mdwn
index 474b608..c9159f1 100644
--- a/TC/PlanningPhase.mdwn
+++ b/TC/PlanningPhase.mdwn
@@ -47,7 +47,7 @@ If we assume the average game time to be 30 minutes (more on that in a sec), the
 
 Nevertheless, there are a couple of reasons why this number is a very conservative, and hosting tournaments with around 100 people at Thorndon is possible, even with people travelling from outside the region:
 
-First, if we can get a maximum of round 1 games played on Wednesday and/or Thursday, then some of the round 2 games can already be played on Thursday and/or Friday (when less round 1 games need to be played), and this substantially helps to free up Saturday morning.
+First, if we can get a maximum of round 1 games played on Wednesday and/or Thursday (where both players are local, and have not ruled out their availability), then some of the round 2 games can already be played on Thursday and/or Friday (these always come i pairs, and require 4 players to be local and available). This substantially helps to free up Saturday morning.
 
 Second, 30 minutes is a pretty generous average game time. Sure, some of the higher-graded players have been known to play twice as long as that, but contrariwise, players in lower divisions often finish in less time. Rather than overcompensating though (with e.g. 40 minutes), it's better to keep the slots short(er) and risk running a bit late. It might be counter-intuitive, but a tournament that runs late is better than a tournament that runs early (due to longer slot lengths), because more people will be present on site (waiting), and the courts never turn silent.
 
@@ -57,6 +57,9 @@ Finally, if sticking to plan is really a concern, then the match rules can be mo
 
 At the time of writing, the next Thorndon Open is just 2 weeks away, and we are looking to accommodate 106 players, meaning 53 games in each round. Despite being called the "Thorndon Welcomes the South Island Open", only 22% of the players came from outside the local Wellington region (not including Ōtaki, Kāpiti, Masterton, and Martinborough). Chance also had it that a lot of the divisions would be made up entirely of local people. As a result, 31 round 1 games can be played on Wednesday, and 21 round 2 games on Thursday, leaving only 22 round 1 games for Friday night, and 32 round 2 games for Saturday morning — to be fitted into a 4 hour time slot!
 
+Don't despair, the [[Draw Maker|TC/DrawMaker]] can help juggle all this, but
+only once the registrations roll in and we have some real data to play with.
+
 ## On the subject of themes
 
 tbc.

diff --git a/Interclub.mdwn b/Interclub.mdwn
new file mode 100644
index 0000000..a9a02b2
--- /dev/null
+++ b/Interclub.mdwn
@@ -0,0 +1,7 @@
+# Interclub
+
+1. Announcements
+2. Setting up HelloClub events for registration
+3. Making the teams
+4. On the night
+5. Results entry

diff --git a/Club_nights.mdwn b/Club_nights.mdwn
new file mode 100644
index 0000000..4c638b3
--- /dev/null
+++ b/Club_nights.mdwn
@@ -0,0 +1,3 @@
+# Thursday club night
+
+tbc.

diff --git a/logo.png b/logo.png
new file mode 100644
index 0000000..865c02f
Binary files /dev/null and b/logo.png differ

diff --git a/Intraclub.mdwn b/Intraclub.mdwn
new file mode 100644
index 0000000..bf1ec05
--- /dev/null
+++ b/Intraclub.mdwn
@@ -0,0 +1,117 @@
+(this is pasted from an email Shanti sent on 2021-01-17)
+
+# Social Team Leagues
+
+## Frequency
+
+* Ideally we run these twice per year to compliment the
+Interclub season.
+
+* Once in the Spring after Interclub finishes but
+ideally ending before start of Dec as participation
+really drops off by then.
+
+* Once before Autumn Interclub starts. Typically good to
+kick this off to coincide with schools starting up again
+(early Feb) to allow for 5 to 6 weeks of play before
+Interclub starts.
+
+## Cost
+
+* $10 for members and $35 for non-members.
+
+* Non-members are welcome but priority should really be
+given to our own club members. We’ve never turned anyone
+away however.
+
+* Fees allow for the purchase of food on the last night,
+cover balls and leave some left over as a contribution
+back to the club.
+
+* Note – we charged more in the past ($25/$40) and did a
+free drink for each person, pizza & salad and prizes but
+upon reflection and discussion with club & squash
+captain, decided it was better to keep it really
+inexpensive for members since we all pay a membership
+fee – the main driver for the team leagues are club
+spirit, encouraging participation for all (not just the
+super competitive) and most of all, fun 😊
+
+## Format
+
+* Number of weeks and number of registrations will
+ultimately influence the play format.
+
+* All 4 courts get booked out (speak with Club Captain
+or Squash Captain for help to book if needed).
+
+* Form 8 teams so all courts are used, otherwise go with
+6 teams and leave 1 court free for bookings
+
+  * 32 = 8 teams of 4
+
+  * 40 = 8 teams of 5
+
+  * 48 = 8 teams of 6
+
+* If numbers don’t work out, we try to encourage a few
+more players we know to register, speak to those who are
+reserves but can maybe play most nights or if all else
+fails, see if a few players want to play twice
+
+* Book courts out from 6:15pm.
+
+* 6:15 to 6:30 setup / optional warmup – not necessary
+but helps things run smoother
+
+* 6:30pm start
+
+* 9 to 9:30pm finish (most courts will be done by 9, but
+good to keep a few til 9:30)
+
+* Games are not for points
+
+* Ideally every player and every team get to play each
+night
+
+* Depending on number of players per team, can choose
+from the following:
+
+  * Best of 5 (takes the longest, preferred by most but
+not required)
+
+  * 3 games (this works quite well time wise, especially
+if more than 4 players per team)
+
+  * Best of 3 (fastest time wise but often over too
+quickly for lower graded players)
+
+## Last Night : Food, drinks & recognition
+
+On the last night, we encourage people to stay around
+after the games finish for food and drinks along with
+recognizing team results (placement based on team
+performance throughout the league)
+
+* Pizza is usually the easiest and drinks from the bar.
+
+* The organizer(s) usually say a few words and announce
+the team results
+
+* Generally no prizes but can usually give away a few
+free drinks or something similar
+
+  * Last round we did free drink for members of team with
+best spirit
+
+  * Teams were given a colour and one team in particular
+made a good effort each week to dress in their colour
+
+* Try to encourage team support and player feedback for
+the newer players
+
+* We have tried getting some dress-up / team spirit
+going with limited success
+
+* I think the longer we stick with this, the more people
+will join in

diff --git a/TC/PlanningPhase.mdwn b/TC/PlanningPhase.mdwn
new file mode 100644
index 0000000..474b608
--- /dev/null
+++ b/TC/PlanningPhase.mdwn
@@ -0,0 +1,62 @@
+# Planning to run a tournament
+
+Running a tournament is both fun, and also quite a bit of work. However, as with most things, the better the plan, the better the outcome, and that includes lower stress levels.
+
+Planning includes answering a number of questions:
+
+1. When should this tournament happen?
+2. What players am I targeting?
+3. Does it finish on a Saturday or a Sunday?
+4. How many players can I accommodate?
+5. Is there a theme I want to use?
+
+The answers to these questions will preempt many decisions later in the process, so it's important to get them right.
+
+## When should this tournament happen?
+
+## What players am I targeting?
+
+## Saturday or Sunday finish?
+
+At Thorndon, we generally finish on Saturday night, which translates to better bar sales, and a better vibe throughout the day. The reasons for this are:
+
+* most players will have two games on Saturday, and many will stick around;
+* not having to stay sober that night in preparation of another game on Sunday means there's a better party to be expected;
+* lastly, a tournament takes a toll on organisers and volunteers, but also players. Having Sunday off after a big Saturday allows people to rejoin with their families, and relax.
+
+Finishing on Saturday generally means that everyone gets to play 3 games, i.e. the tournament is confined to 4, 6, and 8 draws. If 5, 12, and 16 draws are desired or needed, then each player has to take to the courts 4 times, and that is unlikely possibe with a Saturday finish.
+
+## How many players can I accommodate?
+
+The number of players one can host at a tournament depends on four factors:
+
+* Saturday or Sunday finish?
+* The number of courts (possibly across several venues)
+* The number of people able to play their first and possibly second round games before Friday night
+* The anticipated average length of a game
+
+As argued above, Thorndon customarily runs 3-round tournaments that finish on a Saturday, and so the following text uses this assumption.
+
+The number of games to be played in each round is equal to half the total count of players (each player gets 3 games, but each game always has two players, so the total number of games is 1.5 times the number of players, and then this number is divided by the number of rounds: n × 1.5 / 3 = n / 2).
+
+With round 1 often starting on Wednesday or Thursday evening, and round 3 starting already on Saturday afternoon, the bottleneck of any 3-round tournament is round 2, which is mostly confined to Saturday morning. This means that the number of people you can host at a tournament loosely depends on the number of games you can play on Saturday morning.
+
+An 8am start is the earliest possible, and this means there's a window of 4–5 hours during which all round 2 games need to be played, minus any round 2 games that you were able to squeeze in on Friday night.
+
+If we assume the average game time to be 30 minutes (more on that in a sec), then 4 hours means there are 8 slots, and across 4 courts, this means that 32 games can be played. By the above logic, this therefore means that a 64 players can be hosted.
+
+Nevertheless, there are a couple of reasons why this number is a very conservative, and hosting tournaments with around 100 people at Thorndon is possible, even with people travelling from outside the region:
+
+First, if we can get a maximum of round 1 games played on Wednesday and/or Thursday, then some of the round 2 games can already be played on Thursday and/or Friday (when less round 1 games need to be played), and this substantially helps to free up Saturday morning.
+
+Second, 30 minutes is a pretty generous average game time. Sure, some of the higher-graded players have been known to play twice as long as that, but contrariwise, players in lower divisions often finish in less time. Rather than overcompensating though (with e.g. 40 minutes), it's better to keep the slots short(er) and risk running a bit late. It might be counter-intuitive, but a tournament that runs late is better than a tournament that runs early (due to longer slot lengths), because more people will be present on site (waiting), and the courts never turn silent.
+
+Finally, if sticking to plan is really a concern, then the match rules can be modified and all games made PAR11, not just for B-grade and up). D-grade players and below don't really like PAR11, so maybe a compromise is to make it PAR11 for C-grade and up to shorten some of the games.
+
+### An example: The 2021 August Thorndon Open
+
+At the time of writing, the next Thorndon Open is just 2 weeks away, and we are looking to accommodate 106 players, meaning 53 games in each round. Despite being called the "Thorndon Welcomes the South Island Open", only 22% of the players came from outside the local Wellington region (not including Ōtaki, Kāpiti, Masterton, and Martinborough). Chance also had it that a lot of the divisions would be made up entirely of local people. As a result, 31 round 1 games can be played on Wednesday, and 21 round 2 games on Thursday, leaving only 22 round 1 games for Friday night, and 32 round 2 games for Saturday morning — to be fitted into a 4 hour time slot!
+
+## On the subject of themes
+
+tbc.

diff --git a/TC.mdwn b/TC.mdwn
new file mode 100644
index 0000000..7030206
--- /dev/null
+++ b/TC.mdwn
@@ -0,0 +1,8 @@
+# Running squash tournaments
+
+Running a squash tournament is a multi-stage process, each stage requiring a different set of steps and tools. Therefore it makes sense to break it down:
+
+1. [[Initial planning|TC/PlanningPhase]]
+2. [[Advertising and registrations|TC/RegistrationPhase]]
+3. [[Making the draws|TC/MakingDraws]]
+4. [[Running the tournament|TC/TournamentPhase]]

diff --git a/index.mdwn b/index.mdwn
index 9ed264c..7d1fcff 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -4,3 +4,7 @@
 * [[Interclub]]
 * [[Social Teams League|Intraclub]]
 * [[Running tournaments|TC]]
+
+# Miscellaneous
+
+* [[Tournament travel]]

diff --git a/local.css b/local.css
index f5cc8c9..9061051 100644
--- a/local.css
+++ b/local.css
@@ -2,3 +2,8 @@ div.pageheader {
   background: #5cc133;
   color: #fff;
 }
+
+h1 {
+  font-weight: bold;
+  font-size: 130%;
+}

diff --git a/Tournament_travel.mdwn b/Tournament_travel.mdwn
new file mode 100644
index 0000000..fafa854
--- /dev/null
+++ b/Tournament_travel.mdwn
@@ -0,0 +1,153 @@
+# Upcoming travel
+
+## Aug 20–21 Surf City Open (Gisborne)
+
+(conflicts with Wainuiomata B&Below)
+
+* Martin
+* Kate & Cam?
+
+## Sep 3–5 Pirates Dunedin or Kaikoura Masters
+
+(conflicts with Kapiti Masters)
+
+* *Martin?*
+* *Linc?*
+
+## 15–16 Oct Ossie's Ohakune Open
+
+* *Martin?*
+
+## 23–29 Oct [Cook Islands Squash Open](https://www.dmck.com/events/cook-islands-squash-open/), Rarotonga
+
+* *Lucas?*
+* *Andrew?*
+* *Martin?*
+
+## late Oct Katikati Open
+
+* Easy
+* Frosty
+
+## 29–30 Oct Foxton B&Below
+
+* *Martin?*
+
+## Nov 12–13 Levin Summer Open
+
+* *Martin?*
+
+# Completed
+
+## Feb 19–20 Ōtaki Open
+
+* Paige (own accomodation)
+* Martin
+* Linc (staying with Martin & family)
+* *Wayne?*
+
+## Mar 19–20 Nelson Open
+
+Plan: travel there by rental car (cheaper than own car on ferry) Friday morning and stop at Pelorus Bridge. Maybe a relaxed Sunday and take the ferry back.
+
+* Ferry Fri 9am – Sun 6:30pm, and staying together at 114 Rutherford Street:
+  * Martin
+  * Lucas & Caro
+  * Linc
+  * Jess (who arrives on the Bluebridge a bit earlier)
+* Same ferry, but staying at The Sands:
+  * Gil
+  * Lee-Ann
+  * Hannah
+  * Ruben (not playing)
+* Former member Hannah Thompson is in Nelson.
+* *Kate & Cam?*
+
+## Apr 2–4 KP A2&Below+Doubles ~~Queenstown Open or Te Puke Open or~~ 
+
+* Driving up Friday with Linc and dog, and staying at an AirBnB:
+  * Martin
+  * Linc
+  * Kay
+  * ~~Jess~~
+
+## Apr 9–10 Wairarapa Masters
+
+* Kay
+* Lee-Ann & Gillie
+* Diane
+* Jono
+* ~~Jemma~~
+
+## Apr 23–24 Geyser City Open (Rotorua)
+
+* Martin (passing through in a Campervan)
+
+## Apr 29 – May 1 Pirates Open (Dunedin)
+
+* Dan Foote
+
+## May 7–9 Kaikoura Open [closed]
+
+(conflicts with Tawa Open)
+
+* Lucas & Caro
+
+## May 21–22 Central & Taranaki Open @ Kawaroa New Plymouth
+
+(conflicts with Mana Open)
+
+* Kate & Cam
+
+## May 21–22 PSA Browns Bay
+
+(conflicts with Mana Open)
+
+* Martin
+
+## May 28–29 Hawkes Bay Tennis & Lawn Open
+
+* Martin
+* Tess
+* Jenny
+* Kay
+* Jess
+* Jono
+
+## May 28–29 Martinborough Open
+
+* Clint
+* Kate & Cam
+
+## Jun 4–6 Wanaka Open [closed]
+
+Heading out on 3 June, 10:20 flight, and returning 7 June 12:30 via Queenstown, possibly with a snowboard are:
+
+* Linc
+* Martin
+
+## Jun 11–12 Hawera Open
+
+* Jack D.
+* Martin
+* Brad & Christine
+* Jaron
+* Andrew L.
+* Sam & Grace from IB
+* Jack S. from IB
+
+## Jul 8–9 Hawke's Bay Lawn Tennis Open
+
+* *Jess?*
+
+## Jul 8–9 Greymouth Open [closed, waitlist]
+
+(conflicts with Hutt City Open)
+
+* Martin
+
+Current plan is to hitchhike my way down the west coast to the next one. Anyone? ;)
+
+## Jul 16–17 Southland Open @ Invercargill
+
+* Martin

diff --git a/local.css b/local.css
new file mode 100644
index 0000000..f5cc8c9
--- /dev/null
+++ b/local.css
@@ -0,0 +1,4 @@
+div.pageheader {
+  background: #5cc133;
+  color: #fff;
+}

diff --git a/index.mdwn b/index.mdwn
index c56b616..9ed264c 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,3 +1,6 @@
 # How-to's & documentation
 
-* [[Running tournaments|RunningTournaments]]
+* [[Club nights]]
+* [[Interclub]]
+* [[Social Teams League|Intraclub]]
+* [[Running tournaments|TC]]

diff --git a/index.mdwn b/index.mdwn
index ca47845..c56b616 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1 +1,3 @@
-Testing Git commits
+# How-to's & documentation
+
+* [[Running tournaments|RunningTournaments]]

diff --git a/index.mdwn b/index.mdwn
index 0841923..ca47845 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1 +1 @@
-Nothing here yet
+Testing Git commits

diff --git a/index.mdwn b/index.mdwn
new file mode 100644
index 0000000..0841923
--- /dev/null
+++ b/index.mdwn
@@ -0,0 +1 @@
+Nothing here yet

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..eecda60
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+/.ikiwiki