I'm painfully aware that there is little system documentation here. It's either in my head or a scrappy notebook in my pocket. If I were to be run over by a bus or attacked by an Apache helicopter, the poor s*d who came in would have a bit of a nightmare on his hands. So, my New Year Resolution is to write a systems manual or a set of notes explaining how it works. So, if you were that poor s*d, what would you like to see. I'd planned to do it as a series of bullet-points but I'm open to suggestions.
I realise that this may produce rather a long list, so maybe if you limit yourself to 5 items to start with. Who know, maybe we will end up with a de facto document, so that any technician can walk into any school, pick up the document and get stuck in. Do I see flying pigs? :)