 So, lucky last thanks everyone for hanging around for this. So, look, Catalyst is a Moodle partner and we see lots and lots of Moodles and I've been involved with Moodle on both sides of the web browser since about 2008. Now all Moodles are different but we'd see some commonalities between them and I thought I'll put in a talk and just go through sort of 10 things that you can do to sort of improve your Moodle experience. And I've tried to make these really low barrier to entry so, you know, you can do them yourself now today or with a little help from your friends. I've also tried to sort of spread them across the whole sort of Moodle experience so hopefully something, everyone will get something from it. And look, this is probably a bit of a health check as well so if you're doing everything in these 10 points, that's awesome, that would be really good. So let's get into it and also actually before I do, this is actually starting to feel like a bit more of a summary than a presentation after sitting through everyone's awesome presentations for the last two days. So visit Moodle.org. Now if you're not doing this and you only ever do one of these 10 things, do this. Like this is the heart of the Moodle community in my opinion. It's got all the Moodle documentation, all the developer documentation, the forums are awesome. Like if you've got a how question of how do I do something in Moodle, go here. Someone's already likely asked the question in the forums, someone's already given an awesome answer. Look I go here on the rare time that I develop these days because I can never remember the data API and it's also something I actually get new developers to do as part of their ramp up is actually visit this. And look, you'll find things in Moodle that you probably don't know Moodle does and look if there's some of the cool new features as well you'll find out by here. So visit this and visit it often. So set up analytics. So analytics help you discover patterns of data in your Moodle and look there's been a few talks about analytics around this Moodle. It gives you like just adding some analytics to your site like Google Analytics or Pwik gives you some really good operational data about your site. Things like in this slide, why are all my users leaving only after 10 seconds? We probably can't quite read that. But it's also to a good first step on your user journey in analytics. So this is getting Google Analytics or Pwik into your site is really low stress. You can just add tracker code via the user interface. You don't actually need to do a deployment or change some code although as Gavin showed you there's also the cool plug-in as well. But once it's in there you'll start to sort of think of some questions that you haven't asked and it's a bit of a journey of discovery and you can actually get in and really see some cool things about your Moodle. Look this is Pwik, I like Pwik, it's open source. You can install it yourself and have full control over your data. If you want to know any more about this come and grab me after this presentation and I'll give you a bit of a demo. Take your backups, do you know where your backups are? And that would be a question I would ask anybody who looks after your backups and if you ask them do you know where my backups are and they don't meet your gaze or they stammer, that's something you might want to investigate. And then look if they do know where they are follow up with asking them how long it's going to take to restore one. And then have them show you just to prove that they're not lies. The reason why I want to say this is it's much better to ask this question and fix the problems before your data centre is full of order. Now this is Photoshopped but we've had clients where this has happened. Talk to your users. Now when I'm talking about users I'm talking about not just your users like your students and your teachers but your administrative users, your support users, your IT staff, all of those groups and look quite often one of those groups use one or more of those groups as an angry pack of lines to be avoided at all costs. But moodles that work well that suit your users needs that are well supported, people talk. They're good lines of communication. So set up a meeting of representatives from all those groups, have a frank and open conversation about what's going on, what works, what doesn't, share the ideas and the pain points and look it's really surprising to me how many organisations don't do this and wonder why they're engaging with their moodles low. And look the change that come out of this, there might not be any, you might be all on track but if you don't talk you don't know. So do this and do it often. Enable conditional access. Now this is something that's been in moodles since 2.3 I believe and it allows you to limit access to activities within a course. And you can limit activities by all sorts of things you might be able to read that. Things like date, grade, user profile, you can do complex sets of them now and look the combinations of criteria can be quite complex as we've seen in some of the other presentations. So it's really, obviously it's really good for you know structuring a flow before a course, doing X before doing Y. It's really good for also doing remedial or extra credit work. Hey you didn't do great in that course, but quiz, here's some extra resources. Hey you absolutely did 100%, here's some more challenging work. We've also seen it used in sort of a learning as discovery type way so you can sort of unlock certain activities as you work through them and something else pops up and the users can go oh that's that information that I thought I might need and then go through that. Want more information on conditional access? C.1. So this one's a bit of a techy one. Set up memcached with moodle universal cache and I did sort of touch on this when I did my performance talk earlier in the moot. So just a really quick outline on this, caching is a way that computer applications speed up information by storing the result. So it doesn't have to go to the database and do this crazy complicated query and then come back. If it caches it, it'll do it once and there's return result from then on after. Markwell the moodle universal cache is how moodle handles a lot of its application caching. It handles a lot of that sort of request story. By default it stores data to disk. If you put that into an application like memcached which is a little application that runs on the server that allows you to store those cache results in memory, things get faster. Look it does require you to install an application on your server but generally it's pretty easy for most operating systems that you want to run moodle on. Why would you do this? Well, essentially speed and cost. Speed makes your site better. Users don't have to wait. Cost, things, faster sites and more performance, you can do less with more. Do a plug-in audit. So as we all know plug-ins allow you to extend moodle but moodle's been around for a while, collect plug-ins and as we sort of learned yesterday up to about 240 in some cases. Look, are these plug-ins being used if so by who and even others use them and so the moodle interface which you probably can't see does allow you to drill down, find out what plug-ins are being used and how many are being used in your site and then you can actually drill down and see where they are. Now I suppose look unused plug-ins can be candidates for removal like if you're not using them why bother having the support burden for them but also just because they're not being used it doesn't mean that they should be removed it just might be that no one in your organisation knows about them so do the audit, have a bit of a look at them and take your results to the catch-up that you'll have from point four. Now check out the plug-in directory and in some cases this is almost the ante of what I said in number seven but if you've got a question where I wish moodle could or I wish moodle had there's probably a plug-in for it. The one that's come up a few times is actually people are talking about analytics is the moodle URLs that are view dot some crazy ID or user dot some crazy ID there's a plug-in to make them semantic clean URLs there's a plug-in for that. You want tokens so you can you know issue tokens for people to sign up for your courses and you know sort of have that barrier to entry there's a plug-in for it want a better wiki there's a plug-in for it. So you have a moodle's built to be extended browse and review some courses so not everyone in your organisation has sort of full visibility of all of your courses and you as sort of a teacher may not have sort of visibility of what your other colleagues are doing so sort of having something like a course review just allows you to sort of start sharing ideas and that helps that building the process of building champions and developing best practices so you know if you get a chance to do review other courses in your organisation and even organise a show and tell and finally start an upgrade of compensation now every version of moodle is better say it again every version of moodle is better and look the more often you upgrade the easier that it is so if you're on an old version look upgrades can be a bit painful but look just start the conversation and see where you are you know find out where find actually find out what version of moodle you're on and whether it's still supported because that's always a good trigger for an up-to-date conversation I see a lot of I wish Moodle could or I wish Moodle did it's probably in the new version like 3.1 it's gonna be awesome so get people excited about upgrading that's it