That is, we got the laptops set up in the room where the training was supposed to take place. A phone switch then died, which prevented our network guys from setting up the switch that we had planned to use to connect the laptops. So, we set all the laptops to use the WiFi. This worked, mostly, except for one laptop that simply couldn't pick up an IP on the internal WiFi network - presumably the wireless router was overwhelmed by all the attention.
The training was due to start at 9:00 a.m., so naturally that was when the trainers (/technicians) arrived.
The new site is not set up - they haven't finished enough of the code for us to put it on our server yet - so the training was going to be done on their development server. Which, unsurprisingly, crashed last night, and was therefore completely inaccessible this morning. And since the trainers arrived just in time to start the class, they didn't find out until we already had everyone waiting at their computers. So, naturally, they were unable to get it fixed despite buying some time by showing off what elements the website contains and what cool things it will be able to do.
So we called off the training, and rescheduled it for Monday. And then I went back to my desk to try to catch up on the stuff I'd missed while I was
On the plus side, that meant I was able to attend the Weekly Family Lunch; and they did manage to get the thing fixed in time for the afternoon training, which didn't help any of our content suppliers but was something of a relief to those of us with publishing rights. The system looks pretty easy to use from their end, which is also to the good.
Tomorrow, we'll start looking at the back-end stuff: generating and modifying templates, setting permissions, creating workflows, and like that.
Anyone care to place a bet on whether we actually manage that training?