 or connect them. Sorry, what was the legacy language? So, yeah, now that it's just about to hit seven, oh, we've just had Jason Green. Jason, before we pick off, can you just say a quick hello and tell us we're dining and connecting in from? Yeah, sure. So, I'm actually going to go to Australia. This would be my first meetup with you guys in Sydney. Fantastic. It's sorry, Jason. You said that you were calling in from Australia. We're in Australia, and who do you work for doing dribble? Yeah, so we do dribble in Woga Woga. Right. And we're a company called Angry Ant, we're designed. Fantastic. Well, thank you so much for joining us, and it's a real pleasure to be hosting someone remotely for their first Wellington dribble meetup. Although, of course, it's not the way to dribble meetup, but it's the Australasian meetup today. Cool. Now, I've got to keep read careful time. It's seven on the dot. Our first speaker tonight was Tom Murphy from Mexico's, I'm Senior Solution Architect, and he's going to be talking to us about this fun LMS. Okay, take stage. Next one. I'll be your slide changer. I'm just going to share our presentation, and then we'll quickly slides. Yeah, that's good. My visible. Can you look on the screen for me? Oh, look, I am. I mean, the only way I get lit is if I block. So, that's vaguely visible. One moment. Two, and there we go. Okay, great. So, okay, which is today over learning is the name of Sparks custom LMS that we bought for them, even though we didn't build an LMS from scratch, pretty much forks an existing opinion distribution, which is a group seven and now a group of eight LMS. So, I'll be talking about, we've been, had the contract with Sparks for coming up to two years. So, this is a little story about what that journey was like. Next slide. Okay, quickly just ask everyone remotely, can you give us a thumbs up if you can see the slides, and if you can hear Tom, okay. Fantastic. Okay, shit. Okay, slides. Cool. So, Sparks, when they came to us, they had three different closed source LMSs with an average age of about 10 years old, which is their annual license feasible. They had a very limited option of deferring one year's worth of license costs for it to build an LMS. And they'd never done the open source stuff in Sparks, which was the possible exception of Linux, which I'm sure that they weren't allowed to talk to anyone in meetings. So, off we go. Next slide. Yes, next slide. So, we were too small for Sparks, so we introduced Spark and Acquia, and Spark and Acquia talked about a year, and after about nine months, that turned into a paid discovery. Which, you know, we thought, and we were lining up for a soft contracted gig at that point, and we thought, oh, okay, this is gonna be all right, maybe. So they didn't really seem to know about anything about LMSs, and the whole thing had actually just started with someone that we knew who works at Spark, who was like, surely there's an open source version of some of the stuff, and I'm like, yeah, yeah, there is. That's kind of where that all started growing. Anyway, so, paid discovery was thinking right, something's gonna happen. Next slide. However, I think that people inside Spark were like, yeah, yeah, it's a really big deal. Yeah, and Acquia was like, yeah, it's a really big deal. Gonna add a zero. Gonna add another zero. So, when they actually found out how much money there was, which was like, close to nothing, I think it was like, you know, 150K licensed annual license fees. They're like, we can't be able to do that, that's right, we're gonna give you K. Give us a million dollars, we'll give you, well, contractually nothing, but we'll just give you full agile for like, you know, a million or two. So, we're just like, the music was going down. It was all falling apart in contract negotiations and we were like, oh God, damn it, it's all over. Next slide. I'm gonna do it, I'm doing fine. Right, so Spark was sitting there like going, damn. Okay, we've got six weeks before we have to pay the license again. Do you wanna switch on a Pinho? And we're like, what, on our own? And we're like, okay, if the conditionals we had to accept, we had the basic contract on their standard contractor terms, not on Acquia's like 150 pages of legal doom. Sorry, Acquia, if you're around. Yeah, Dallas is from Acquia, but he's a bit, he knows what it's like. No, Acquia's amazing. No, we had a good chat with several people from Acquia afterwards and they thought it was an interesting learning process. Anyway, so they came, Spark Edge was direct and we sort of set it late to Acquia and they're like. So, next slide. So we're insane, we said yes. So we had to, after contract negotiations, which took three days, we had five and a half weeks to replace three different LMSs in production, starting from zero. So this was where we had to flip to. You just click through. Sorry, I can't click through now. Right, so the main thing was like, your 10 year old piece of shirt, are you getting exactly that to go into production again? Because that's what you would have paid for if you'd renew the license. So that's where the contracts start up. So that's all we have to compete with is 10 year old LMS software. I made it loads easier. And we just switched on, we thought, okay, we switch on Acquia, it does everything, all the features match, we just pitch it out and we just import the content, you get all CSB exports. Next slide. And then this is our usual Pantheon, Pantheon Trello, what's the stupid means? This is our general approach. We thought, yeah, 12,000 users, we'll just import them, 108,000 user reports. Yeah, we can get more CSBs, we'll just import them. No problem, next slide. So at this point, and it's cutting off here, we're like on the skinny end here, right? So we're just like, yeah, great, we'll just switch it on. We haven't modified the pinion, we'll just switch it on. Excellent. Okay, cool. Now, the whole thing is breaking my slides, mate. I can't even read anything. Yeah, just drag it on. Yeah, that's good. So it's sounding good at this point, but promise one, knowledge is power, promise two, power corrupts, conclusion therefore, knowledge corrupts. Next slide. These are actually, as stuff melted down to various degrees, these are means from the Trello board, which we were sharing with the client. So the only from his opinion step team were they knew PHP, they didn't know Drupal, and their development approach was barring a tunnel through solid rock when they could have taken a train. So next slide. They've rewritten huge chunks of Drupal, like in Thinlayer, had no idea anything works. Stuff that we thought was used was actually hand coded PHP reports because they couldn't get the truth. So there was a lot of pain, and we had like five, six weeks where people were doing a same hours. But next up, we did launch on the date, and we had lots of challenges with what the opinion of the data model was, what Spark data model was. The team, the internal Spark team dealing with the project was too big, which is where the stupid memes came from. We started introducing more and more stupid in-jokes, and the more people at Spark couldn't understand the in-jokes, right around the chain. We were... RIP! RIP! RIP! RIP! RIP! We've got to the front of a no idiot song. Awesome call of fire. Yeah, yeah, yeah. So, yeah, we had a lot of kinds of surprises. A lot of UIDs that were strings which didn't actually have the, oh, it's lowercase t. It's an uppercase t here, and basically I asked this product owner now, which is the second product owner, can I say that you're a little bit confused? And he says, sure, what large corporation doesn't have these problems? So the big challenge for us was we were used to dealing with companies that were like a scale smaller. I mean, when we talked to a company, we thought we were talking to a company, but actually it's a giant, an arcade community of different departments that barely communicate. So the main assumption is just because that's what you say, who knows what they're gonna say. So once we stabilize into that, next, oh yeah, Spark Security versus Google Cloud, you're dealing with like 20 years difference and definition of what's standard or what's safe. That was a major challenge. Gotta keep going, next slide. So we had to go to the next level. So few people noticed that the bald guy had changed. Ha ha ha ha ha ha ha ha. Good. Okay, next slide. So by this point, we're kind of up to here. We've launched, we've got a support contract. We've got a continuing development project. And that was the point where, okay, now we've, we've, we're on there and now we're extensible, right? So suddenly we can let go, we've wanted to be able to export this and we've wanted to be able to do this report for years. Okay, we've just added a view or we've just added this block We're starting to actually get, like, nature triple running. Next slide. This is pretty much we're getting some next level there. And just go straight on. So every time it does seem like things made sense, we just had to just change up the next level. Next slide. And then finally, things were, like, going really well. It's amazing how much progress was made just through stupid memes. And I'm making things at this point. Then I'm all from the internet. Next slide. However... So I'd been running the project up until this point. I went on holiday because I was... Because you'd earned it? Yes, because I'd earned it in more ways than one. So we went through another couple of project managers and I ended up taking it back. So then we had some bumps as it started to get too big, as we didn't have enough handover, and we had some bumps. So bring it on. Next slide. At this point, we've got this massive fat done about a year. We actually started in February. Started in February. Launched April 1st. We've come through April 1st, April 4th day. It was the D8 launch, because we planned to spend a year on D7, just because we had a feature set, feature complete LMS in D7, which was a pinion, but a pinion had no D8 port. A pinion had a D8 port about six months, nine months into it. And then we started building all this extra functionality of parallel LMS, which was based on how they wanted to do things, not about how cornstone their legacy system or our pinion works, wasn't scorn-based. Anyone knows what a scorn is? Yeah. So that's an international shared content object relationship model learning thing, and that's what sparked running on. We had about 1,000 scorns in 108,000 records, probably more like 300,000 now, 12,000 users. So we've got this live thing, but we're like, okay, we're not going to start building any really complicated features in seven. We have to start building eight. We'll just take the D8 pinion port, and I'm not really running it. But then this giant tornado features, collides with an April 1st launch date, and again, yes. And then it doesn't work. Next slide. So I get onto the project again, and I had to like, well, first thing I want to do is have a decent meeting. Okay, next. But it was really unpleasant. And it was a lot of confusion. So next slide. But gradually, there are a series of stupid memes that I started to like, make everyone communicate. Nursing a pen of the content, not being congruent with itself. Yeah, exactly. That's the whole point. That's what the first one is, youthful scandal. Just continue the challenge. Next slide. Okay, cool. This is one of my favorites. We had massive problems with what you think is a scorn. Isn't a scorn? Because the fundamental of a scorn is an XML manifest of what everything is. Unfortunately, the way different software products which were claiming to export scorns weren't scorns, and we're introducing extra manifests in different places. Lucky Git repo inside of Git repo. And everything was exploding. And we're like, well, we don't have to support it because it's not scorn contractually, but it's not a scorn on which is a thing. We don't have to support it. But we eventually came up with this 15-set procedure, how to clean up all their legacy broken scorns. And then they're like, this list is long. So therefore I made this. Yo, dog, you got scorns in your scorns. Just unzip your zip and zip back that zip without the shit. Which is basically what the 15... This is all cloud-facing. It's like, great. It's great. It was a really great team to work with because the people who've got anything done were ridiculously funny and could actually get this done. There was various other people who were very process-oriented and very important and couldn't follow it. It was too complicated. And just using stupid jokes to filter out anyone else that was following it was very useful. Next slide. That's one of my favourites. So you don't just get over that we just got too big. We started hiring more contractor developers. So we had to have much more rigid trailer structure. Where as stuff ping-ponged between from X equals to the person in X equals back to X equals, back to Spark, back to the person at Spark. Pinging it back. Especially considering their SAP team was based in India. Their business intelligence team didn't talk to their SAML team. And so in terms of whose fault it was, that would expire for quite a while. So we needed structure how that was happening. We had to... One of the main problems was that if Spark was messing up, our team would cover for it. So that would draw on two, three months. And eventually when we didn't have the feature, then it would be like, yeah, but we've been trying to code around the fact that your data's wrong. And that's because of the problem. Whereas then we switched it to, if they didn't match their own spec, we didn't build anything. We told them on day one, we're not going to build this. You've broken the deadline because your data's wrong. Based around your own rules. That really helped. Also, we got to the point where we rigorously mixed what branches, what features was linked to what sections of the contractor. We realized it'd be a huge gap because if we go click on to the next one, I think we're going to get... Next one? Next one, I think... No, go back a bit. Go back a bit until I get to the arrows. I want some arrows. Yeah, that's it. Yeah. What we got to here, you see how big this is? That's the D8 pinion cord. That's first was that first. We've got that huge fat thing, which we didn't actually factor on porting. And in fact, that was harder to port because a lot of that was existing, D7, VW, Sanctiols and D8. So what we did most during this period, we just paid for it ourselves and covered it. And then once we'd actually made that exist, which was expensive, if it was a good strategic decision, then they started paying for everything again. So basically making the money back to the point where we'd forgotten to ask for the funding. They couldn't make the funding appear because that's not how the contractual structures function. You're waiting like six months a year, maybe two years in some cases to make money available. So if you're too stupid to ask for something a year early, that's your problem and you have to pay for it. Anyway, let's get back to where we were. Time got fighting that way. No problem, I'm nearly at the end. I don't go back, don't get to the monkey. So yeah. So by this point, we'd also included links to all their business intelligence systems. So go forwards, dashboards for about one and a half thousand front line call center staff with all their metrics, then getting processed and related to their learning records. So they could get like instructions about what extra learning they had to do based on how they're forming with different aspects of interacting with customers. And we also had a parallel learning system. We also had an extra 3,000 people that are subcontractors that also needed to access the system for legal compliance. Because a lot of this training isn't just like, oh well, we've actually just given some people some training. A lot of it's to do with legal compliance or I'd say compliance in terms of what people actually have to know how to do in terms of get access to their backbone network. So we just extended it to a whole class of non-SAML people. So we went from like 10,000 SAML users to probably an additional 3,000 to 4,000 part of registration users and another 200 subcontracting companies which are now paying spark to access the system that we built. So this is now becoming like partially self-funding. Amazing. Next one up. But we had some like vicious technical problems. One of my favorites was a group permission scaling. James, that was fun, wasn't it? Where basically a pinion had hacked the permission system to bypass any access checks for group content and the way we built a feature and that we were getting 20,000 to 30,000 different lookups per page view. And when we were looking for slow queries it weren't any because queries are relatively fast. It's just that there was like 20,000 to 30,000 of them. So what we did was we we just rewrote group, didn't we really? Oh, we applied. That should be a bit of a problem. Yeah, we just like, yeah. But this was one of the memes at a time because they didn't want anyone to have the rights to delete so we couldn't bypass access permissions which then meant this massive form was covered. So we just put the delete option back by doing a permissions bypass. And it's the void. Next one. And that's my last one. Any questions? I've got two minutes. Well, I was going to suggest that you use the last few minutes maybe a demo. Yeah, sure. Unless anyone's got questions otherwise I'll default to demo. Live. Demo. Live. Demo. Do you want to see some stuff? Yeah, sure. Yeah, sure. I'll keep you tuned. I'll keep you tuned. Okay. So here we are. Hello. Well, just give me the, let's give me the incognito window test. Oh, yeah. Oh, this is the resources. No, I've got a bad line. Cool. Here we go. That's good. All right. So Tom, is there something behind the computer to go through? Okay, cool. So we're on the Dev site at the moment because the test site's got a whole bunch of dumb content changes that I made up the pre-deployment tests. But it's identical to what's going to be on the live site tomorrow night. And basically you've got three sign up from a computer as a whitelisting system. Basically found what domain, like Downer, Chorus, a whole bunch of companies you can whitelist register, which is stored inside the Drupal database. That's if you've got an existing Drupal database login. And that is your sound market. All right. I'm going to go through the sound system but just give you a sense that's how you get into the system. And that's what you see if you're not authenticated. This is my admin account. And most people will see this stuff which is a picture of them. That's my happy face. And say you can find a course and go like, oh, hey. I need to do the price course. It's running slow because it's on a dead environment but it's reasonably perky in the production environment. And then you get an option of starting a storm thing. And that launches a storm. You go through there in terms of learning systems. Great. And I just go through that price of course which I won't show you because that was the average confidential information. But if we go back here, then I'll really breach it because you can see that course recording, so you rewrite all of the opinion stuff and pretty much fought. We're not really on opinion. Because it was just... Have it actually logged into anything yet? Yeah. I hear it's been logged into us. Yeah, so this is my admin account from LinkedIn, put in Lonnie, put me to tap. Okay. Sorry about that. So this is like... No, this is all like user data. So this is all like that. This is course recording. This is the... Doesn't matter. No, you're filming me. Got that. This is the learning catalogue and this is all the stuff that you can basically search by stuff that you're into. That's what search thing goes through. So it's basically... What we've done is like... Fill in LMS with the CMS. Because it's just an object model. And all of a sudden they're like, wow, this is totally better than anything on the market. So the LMS market is... It's super funny. If we go to a place in performance dashboards, anything else on the community particular ones to see? Well, that's totally fine because I'm running out of ideas. Sure. It sounds like I'm based in... Can you... Screen banks really? Use content across different courses. Yes, but they don't choose to. But yeah, we spent a lot of time trying to optimise what their content model was. But then we realised that that was part of an intern culture and what they really was was something to enable their current culture. So they're actually like, they've got one school, the learning thing. We've also built all this extra functionality for internal content. So don't use... And we've got this extra functionality for video-based content. So they've got team of people making scores. They export them and we import them and then we just record the data. We affect access to them. We affect medications around getting access to them. And we just sort of say, okay, is that how you want to roll? We'll do that and we'll just enable you. Which keeps them happy and keeps them out of play. And keeps us reasonably happy. And we've got a dashboard. Let's see if we can... The system does support reusable modules. So you could have a set of questions that would occur in a number of courses already. They just choose not to use them. Any other questions? Why don't you go there and I'll come back to the video? Sure. Before we go into questions, thank you, John, for presenting on that. So, Oland's free to be phoning in. He's not here yet. Okay. So just do Q&A. And then when Oland arrives, we'll have to transition to that because he said he had to be gone within 20 minutes for Oland. That's fine. Yeah, that's fine. I'm here, Alex. I'm here. Sweet. I'm off this. Oh, good. Well, good timing to wrap that up then. Let me just cancel the screen share. Oh, my God. Got something with that. I didn't realize I had to give them the call. All right. Well, that is something. Can I just do a quick round of applause for how many people have actually joined? This is amazing. Okay. And in the interest of time, we are just going to have to do this. Just a cool 15-minute picture. Yeah. Oland, we'll put ourselves on mute now. And if you could take it away and give us the Drupal Association office. Okay. Thanks, Alex. So I'm obviously not Philip and I'm not talking about Raspberry Pi. Unfortunately, that had to be shuffled around and I got pulled in at the last second to talk about Drupal South. Those of you that don't know me, Owen Lansbury work with the Drupal South Steering Committee, also on the Drupal Association Board. You might have seen me at Drupal South in Hobart. In terms of housekeeping, if you do have questions, just throw them in the chat window. There's a little link to that at the bottom of the Zoom screen there. And I'll put a couple of links in there for things that I'm going to talk about. So apologies. This won't be as humorous as that last one. And I haven't drunk as much beer as the Kiwis to get through my little session here. So just to kick off, for those of you that aren't aware of how Drupal South is now structured, last year we put together a steering committee. And the purpose of that is so that we can oversee multiple activities and events in the longer term and have a bit more continuity than we'd had in previous years. We're actually governed by Linux Australia. So we report to them on our financials. They provide us with bank accounts and all of our accounting procedures that we need to go through. But then our link to the Drupal Association at a global level is if they have policies that are relevant to us adopting at a local level, then we adopt them. And a good example of that is the code of conduct for our events. And then the other thing is that we've got good interaction with them at a global level. So there's a local organizers or event organizers working group at a global level and Chris Keane's involved in that. And that's basically sharing best practice across events and things like that. So I'm just going to talk about how we've been listening to you so far. And the major thing that we did at Drupal South Hobart was run a bunch of buffs for different audiences to get input and feedback about what people are finding is important for them. And I've just posted some links to some blog posts that we wrote after those events that go into more detail about what was discussed. But just in summary, we had the first ever time that Drupal South sponsors had sat down together and talked about what's important to them as sponsors of the event. But also for their businesses focused on Drupal more generally. We also had a local organizers off with people that run meetups and training and other local events. And one of the outcomes of that is this right here. So being able to amalgamate our meetups into something that's a bit more regional and high levels of attendance and more feedback and interaction and you might get just in your local meetups. And then the final one was an event organizers boff where we talked about what's been working well at Drupal South, what hasn't, things that we could be doing to improve the format of the conferences themselves and then other events that we might start looking at. So feel free to read those blogs in your own time I'm presuming you probably haven't already. And all of that then fed into a strategic initiatives document that we've put together is the steering committee. And I'm putting a link to that in the chat window as well. And I'll just go through that in a little bit more detail just so that you're aware of where we're focusing our efforts. So after taking feedback from people, getting input, what we did was a process of prioritizing where our focus should be in terms of what's going to have the highest impact versus what's going to have the most involvement required to get things off the ground. And this document basically outlines in order of priority what these initiatives are. So as I said, the primary focus of the steering committee is to ensure continuity across events. And that involves things like selecting teams to run events in different locations well in advance, giving them guidance and sharing knowledge about what's worked well at previous events, having standardized tools in terms of accounting and reporting and using the same website every time instead of building it from scratch each time. And then more functional things around maintaining databases of who's sponsored previously, who's attended previously, how to reach out to them. And I think we've obviously got our Drupal South events, but we've also got Drupal Gov as one of the events that we're overseeing. And we may have other audience specific events that we start rolling out over time as we get a bit more bandwidth to focus on those. And I think the overall goal for us is, yes, we do want to grow attendance over time. It's not the only measure of success, but it is definitely something that we can point to and say, yep, over the past three years, we've grown by 10, 20% in terms of attendance, and that shows that we've got to thrive in community and then engage in community. The other thing that we've talked about, and this obviously came out of the boff that we ran in Hobart, is how do we provide Drupal Meetup small accounts, community training and sprints with financial and operational support? And I think that the message here is that we want to be able to facilitate communication between the various meetups, and there's now a Slack channel that's been set up for local organizers to communicate through, and that might be things like, hey, has anyone got any speakers that can speak at our meetup as well rather than doing a call out in your own local area? Common tools. So if you are needing to promote your event, we've now got a platform through Drupal South.org to do that through the official Twitter accounts, those types of things, and feel free to reach out if you need to use those. And then I think the important thing to convey here is if you are looking at running local events, please reach out to the steering committee for funding for those. So the way that we've been running our Drupal South events, we have been very fiscally responsible and we have been generating reasonable profits over the last few years out of those, and we have access to those to then distribute back into the community where we think it's appropriate. So if you're looking at running a local camp or you're needing pizza for your meetups and those types of things, please reach out to us. I think in terms of meetup funding, we're probably going to move to a standardized model whereby each meetup gets a fixed amount each year and you can spend that as you see fit. And we're just working through with Linux Australia to work out what the model around that might be. And then the next thing to talk about is annual sponsorship packages. So this is a very early stage at the moment, but now that we have a calendar set up of... We've got two big events locked in in the next 12 months. We've got some other initiatives starting to get traction. We raised this with the sponsors at Drupal South Hobart and there was generally a good response to if we offered an annual sponsorship package would that be something you're interested in as a sponsor? And that obviously simplifies things across the board for everyone whereby we can say these are all the events and initiatives we're running in the next year. Here's a price for you to have exposure at those rather than us coming back to you each time and asking for more money. And there's a whole bunch of ideas around what those types of things might look like in terms of exposure. So obviously the events, but if we're starting to run promotion at non-Drupal events and being able to feed leads through to our Drupal South sponsors then that's something that we're starting to look at as well. Regional marketing initiatives. So this is something which is probably going to take a little bit longer to get off the ground. But what we are looking at is how can we grow the message about Drupal in technology media and across social media channels so that there's more awareness of what's happening with Drupal as a product but then also as a community. And I think at the moment it's very ad hoc in terms of what those communications look like. And if we're solely relying on the Drupal Association to do that at a global level it's not necessarily talking to our local and regional audiences about things that they're most interested in. So there's a few initiatives that we're starting to look at that are listed there. And then one of the things that we're starting to look at in terms of budget is whether we should be looking at bringing on a marketing coordinator in a retained capacity. Obviously as a paid engagement but to have someone whose sole focus is to be promoting Drupal on a continuous basis. And essentially that's a market development activity so that the more people that are aware of Drupal the more decision makers that have got Drupal in their consideration mix that's then feeding down in terms of RFQs that are coming out that companies that we work for can respond to win and then obviously drive growth of the market as a whole. One day decision maker summits is something that we're also looking at. And in my role with the Drupal Association Board I'm actually involved in the coordinating team for their executive summit at DrupalCon Minneapolis. And the idea there is that if we get the format right that's something that we can start rolling out internationally as well that would have Drupal Association backing so that we'd have an official event that's targeted at key decision makers, CTOs, CMOs, CIOs, etc. And that those summits become a way for us to really push Drupal as a very viable option for them to be considered. So that summit in Minneapolis is going to be run in May and then I'd say shortly thereafter we'll be able to start looking at how can we run that regionally. And I think just so that everyone's aware it might be a case that we run one in Auckland or Wellington or Sydney or Melbourne it wouldn't necessarily be a national event probably quite small very targeted in terms of who we want to attend that. And then the final thing on this list is engaging with the Asia-Pacific community. And this is a kind of broader goal for us to be able to start engaging beyond our region a little bit more. And the first step of that was I was up in Tokyo a couple of weeks ago met a bunch of different community organisers bunch of different companies that are operating up in Japan just to get a sense of where they're at as a market and as a community and to find out what types of things that we might be able to share with them both as Drupal South or as the Drupal Association to get their communities humming a little bit more effectively. And then also understanding what are the nuances between markets within Asia-Pacific that we need to be aware of. And of course the first question was when will Drupal Con be run as an Asia-Pacific event? And my answer to that is probably not anytime soon but it's a nice aspiration to have in the longer term. And having said that that's definitely not going to take any focus off us running Drupal South events at a regional level. So feel free to read through that in more detail. Feel free to make any comments or contact us if you've got ideas that you think that we should be focusing on. And I think one of the things to point out for this audience is we do want the Drupal community to be reaching out to other technology communities in a more active way. There's a lot of complementary technologies that Drupals are natural fit with whether that be front-end frameworks or LMS style functionality that we just store. And one way that we think that we can drive that is by having really good people who can speak about Drupal who can then go off and talk at other conferences, other meet-ups and things like that. So if that's something that you're interested in, please reach out and let us know. And I think what we'll move towards is just compiling a list of people that might be available to speak. If we hear of an event that might be appropriate, we'll reach out to that list and see who might be available to speak at those types of things. And likewise, if you hear of events that you think Drupal should have a presence at, then reach out to us and let's see if we can coordinate something around that. Then just specifically in terms of major events that we've got coming up. So the first one is Drupal Gov being held in Canberra in early November 2020. And that's going to be run as a one-day event for sessions. We're going to have one day of a code sprint after the day of sessions. And then there's talk that we'll be able to hopefully time it so that the Gov's CMS mega meet-up is then held on the third day. So if we can pull that off, then it'll mean that we've got three days of really kind of focused Drupal-related activities and content all happening in Canberra at the same time. And the local event organises for that Achille Bandari from Salsa. And he's also been assisted by Kim Phan at this point in time. Again, if you're interested in helping with that event, they'll be looking for volunteers and putting out a call out for volunteers. And then there'll be calls for session proposals and things like that, hopefully within the next couple of months. And then the next big event beyond that is Wellington in early March 2021. And Alex and the X-Equals guys have put their hand up to facilitate that as local event organisers. And again, there'll be more communication coming out about that once we get moving with things. But we do have a fantastic venue already booked in. And it'll be quite quick once we kind of get moving with that as well. I do have a note, but I can't even read my own handwriting for the next thing. The other thing that we've set up is a career pathways working group. So one of the big things that came out of both the local organisers boff and also the sponsors boff was how we're growing new developers into the Drupal community. How are they finding out about Drupal? How are we training them up? How are we then offering them potentially internships with companies that use Drupal? And how does that then lead to a career in Drupal? And Cy Hobbs has set that working group up. There's about six or seven people on it from around the region. And they've just had their first month of looking at the types of initiatives that they might be able to get moving with. And I'd say that at a certain point, they'll be making more public announcements around what those initiatives might be and how we can all help with that. I've talked about the executive summits that we're likely to run. And then at a global level, we've got DrupalCon Minneapolis coming up in May. I think the sessions that were selected were just the speakers were notified in the last couple of days about that. And I know that there's a few Australian New Zealanders that have been selected. And then DrupalCon Barcelona will be held in mid-September. And their call for session proposals hasn't come out yet. The other thing of the things that Drupal Association is working on is a contribution recognition working group. And for those of you familiar with Drupal.org, there's Drupal.org slash services section that lists all of the companies contributing code to Drupal. And this working group assessing what are the measures of contribution that should be recognised is definitely not solely code. And there's recognition of that. So what are the other things like event volunteering, speaking at events, sponsoring events that would contribute to those rankings in the services listing? And then the step that that is then leading towards is a restructuring of how companies are represented on Drupal.org. So at the moment, it's a real mishmash of your listing in the services rankings. You might be an organisation member. You might be a supporting partner. You might be a sponsor of different events. And they're trying to consolidate that into a single approach. That's probably not going to look dissimilar to kind of gold, silver and bronze preferred partners or supporting partners so that it's clearer to the market around what companies are contributing the most to Drupal and who should you be talking to if you're wanting to get your projects built. And a much longer term ambition that hasn't had any real thought put into it at this point in time is a more generic Drupal developer certification programme that's not tied to any specific vendor that the Drupal Association would facilitate. And again, that would be moving towards an approach whereby if your company has a certain number of certified developers, if you're ranked at a certain level within Drupal.org, then your profile and recognition would be ranked accordingly. And just as I wrap up, if you're not already a Drupal Association member, you can become an individual developer member or an organisation member. And then obviously there's their supporting partner programme. And that just gives you more profile at a global level. I will wrap up. If you do have questions, we've probably run out of time, but feel free to contact us through DrupalSouth.org. There's a little contact button you can send an email and that'll come through to the steering committee and we can then talk about that and get back to you. And then most of us are all on the Drupal AU NZ Slack channel. So feel free to ping us directly if you wanted to talk about anything there. Who's actually coordinating this meetup? Wellington is coordinating, I think. Good one, hand over to you. Yeah, I'm happy to take it from here on. But firstly, just want to give you a massive thanks for that recent sync breakdown. Thank you. I think the planning office is incredible. They have you here giving us updates from the DrupalSouth committee while we've got all these different people phoned into the same video call at the same time. That's absolutely amazing. Yep, and feel free to ping me if anyone's ever got any thoughts or ideas. I do have to step off, unfortunately. All right, right to that. Thanks for having me, Don. And this is sort of global cat herding, so bear with us here. But I think next up is going to be Vladimir from Brisbane. Vladimir, are you there? Yep. Can everyone hear me? Oh, fantastic. I've got to say, this whole IT setup has been bloody flawless so far. Yeah, touch work. Touch work. Yeah, touch work. Thank you. Hey! As soon as it works. Yeah. All good. So, Vladimir, I'll let you introduce yourself. But otherwise, thank you so much for making time to speak to us tonight about tokens in DrupalSouth. They're a proprietary company. Excellent. I'd be a bit bigger fan. How do I share things here? There you go. Big green button. Can everyone see that? Yes, I can see. Yes. Thumbs up. Excellent. All right, so my name is Vladimir. I'm in Brisbane. I'm going to share a few things. I'm doing every Drupal Global Training Day. And first time in April, we're running it online. So feel free to sign up or pass anyone. The topic for April would be intermediate platform development. Also, organizing Drupal Can Bar and Bay. We are trying to make it more Dev Day kind of event based on the feedback from last year. So finally, the venue has been confirmed. We've been bounced twice. So it's the 27th of June. We're in Bay at Saturday. We might extend to Friday, like we did last year. There's enough people interested in becoming to Friday, but at the moment, just one day to track kind of event. I'm trying to do a lot of hands-on sessions. So feel free to ping me about those. And without further ado, I'll jump into tokens. I had a few issues with my Chrome, but I'll try to do a lot of them. So if we're not working, I have a couple screenshots. And if the screen is not loaded fast enough, just let me know, I'll try to do this. All right, so tokens. If you haven't heard about tokens, you probably installed the module called path order before. And when you install a module called path order, you actually are required to install tokens. So if you try to install path order, you say, yep, I need a module called token. You download module token. We actually go to the module token here. You can see there's only help. And it basically gives you a list of placeholders. And that's what tokens are. So they've been there from in triple five for a very, very, very long time. And kind of made their way there quite useful. And I'll show you a few use cases where I can use them properly and see if you can actually use them in your next project. So the first thing, as I said, path order requires triple token module. So if we'll go to path order settings, path order looks after URL, kind of pre-g URL thing. So if you go to a particular content, if you go to a recipe like this one, there you go. Chrome's playing up again. You can see the URL right here is recipes slash chowder. Obviously you can insert it manually. But to make it more automated, that's the path order module. So if you go to search in metadata and configuration and into URL analysis, there we can configure patterns. So the list of all the analysis are here. But if you click on patterns, by default, you won't see anything here. So I'll just select stuff ID for recipe and add a new path for the pattern. From this particular case, I will be targeting recipe content type. In case anyone is interested, I'm using the umami demo thing. And it's the message. And I'm using Clare on the back end, which is a new admin thing. So to ask you the path pattern, and you can see from my auto pop-up, I can use a few patterns. I know that the recipe pattern is recipe slash. And then it actually goes for a token. So if we don't know what token is, of which particular token, there is a helpful window. It's going to pop up. Basically the same thing we saw in help. And here we would go to the node because recipes are the nodes. And we're looking for a title. If you're looking for an ID, for example, recipe slash kilavanna slash pp3, that's the way to go. I'm looking for a title. As you can see, you can scroll further. So here we go, node title. You can insert token here and it will be processed. And yeah, I'll select all languages, save pattern here. So now every time I'll go and create or replicate the recipe, I'm going to click on edit all my latest recipe and click replicate. That's something like on salad. I don't know what to call salad in Spanish. Sorry, but we can do that. You can see the URL change recipes from salad. Now tokens are quite a serious tool and make sure you use the right one because sometimes it can give you very, very unexpected behavior if you're using the wrong token. So actually before that I was playing around and I put just for all the nodes except recipes, I put current page title and that actually gave me very weird result. For example, one of the pages, it actually picked up the title of the edit for. So if you look at Drupal Cambyron by here, actually the title picked up was create basic page. So make sure you use the correct token for the correct entity. So if you use the taxonomy, you use the taxonomy name. If you're using nodes, you use node title and so on and so forth. Just make sure. So if you see some gibberish in your LSS, then yeah, feel free to poke around and see if you can regenerate them, which is quite easy to do again, configuration, search in metadata, URL LSS. And from here, we have bulk generate where we can pick up specific entity and just regenerate all URLs if you really want. So in our case, if I want to change the pattern for page and articles instead of current page, I put node and ID, save it and go to bulk generate. Regenerate all the content. Unfortunately, you cannot pick up the specific content type, generate and go to the content. So NAD is there. But you can see if while I'm hovering over the content, it's still cached so that I know the URL, which is create basic page. But now it's actually displaying node ID. So it just has ID 20. And English appears there because it's a multilingual website. So mommy's multilingual too. All right, so let's play with something more interesting. So usually you would see copyright block on the bottom. And you obviously doesn't want your client to see what the website that says copyright from seven years ago. Or you'll probably create something like custom block. Place it on the bottom. Make copyright 21. And you put foolishly another copyright here. And then we probably want to put it somewhere in the footer, all the way to the bottom. Let me just put it in the file. Same block. So it would be good if you can use a token or actually have a current year there. That would be great. So if we look at the moment, now homepage, you can see it's copyright 2021. So if I go to my tokens, to access list of tokens, I can do it from the modules page, appear, go to help. And the first thing I'm going to do is a current date. And if you go currently custom, I know according to php documentation, custom year would be Y. So I'll just copy this to the token. Go to my blocks. End of my copyright token here. Same updated. As you can see, it's actually here. So to help us to actually process tokens, cash issue again. There you go. So look at the source tokens that are on today. It's not being processed. So in order to process token, there is a module called the token filter. So token filter actually allows us to put a token filter on one of the text formats and process. But it's, you probably have seen, it's already enabled over here. So the way to enable the token filter is you could go to content authoring, text format, and editors. And because we're using full HTML, I'll just configure full HTML. Just to make sure it's actually quick and easy. So the first you'll see there's a button here called token browser. It's actually browse particular token. And edit your viewing. But if you look for the token, you can see there is a replace global and entity token so there are values. So if you select that, maybe drag it to the top if you want to over the filters. Save it. I'm just not sure if we need to save this particular. Oh, but if I refresh that, copyright question, oh, if I got to change it to a year, I cannot access my tabs. Right. So here go replace token with a year. Save that. So we have copyright 2020. We can actually use tokens, you know, to place in a specific block. And do that. Although we are on the note page, keep in mind that if you place something like a note token, it's not going to be processed because it's actually going to be called from block entity and block entity have no idea if it's loaded on note. So if you put a note. And it's not going to give you anything. I ran, but I actually haven't experimented with it. If you if you use entity, some sort of entity tokens, you might get lucky, but I didn't go that far. So we'll quickly go again to list of my tokens. Let's see what sort of entity tokens are there. Yeah, I'm not going to do that. Anyway, if you feel an experimental, you really want to get the melody from that. You can do it. But if you say note ID here, the first page should just be. No, it didn't process it because it couldn't replace it. Okay. So yeah, keep in mind that the tokens put in there, they either global tokens or block specific token. So yeah, feel free to jump there. So to finish it up, I'll just mention that there is a module called meta tag, which heavily relies on module and before the configuration of the meta tag is actually heavily involves tokens. Manage defaults global. You can see there is a lot of tokens are used for the global seconds for meta tag. So meta tag is actually a heavy user of the token module. A few people mentioned that there are tokens in views, but actually different tokens they use now to replace holders. So for example, if you have a view of the content and if you want to display how many results are there in your header, it's called replacement patterns. Available global token replacement patterns. Actually it is token here. So in fields it would use the way things appear for the results. So there's a page count. I can see their page, photo rows. I'll save that and go to our content. And I can see where it is. But you've got the idea before view. So it should have a header. There we go. Maybe it was a cache. So total records 42. And we can use tokens as well as views. Again, this is just the introduction to how to use tokens. You can go a bit more creative. You can go a bit more, you know, actually define your own tokens. So but that's pretty much it for today's presentation. Thanks for listening. If you have any questions, do let me know. Someone has a question. What was that search module you were using there, Vladimir? Search? And go to the topic. It's a new team. It's a new admin team, Claro. So that has that option. Can you go back to admin interface? It works similarly to coffee. Coffee. No coffee. No, okay. So yeah, I got I got the question. Yeah. So this was particular. I was using coffee. Yep. Well, that was coffee. So this go to was a coffee. But there is also a search as of Google 8.7. I think it's enabled with this search provided. I'm not really sure, but I think it's provided by admin toolbar. I still find coffee is a bit more, you know, Mac and the feeling. So it does have this spotlight interface, whereas the search, which again, I think it's the tool bar provides more results, which is sometimes if you're looking for pages with a lot of results, it actually is search provides more results. And again, I think this is an admin toolbar, but coffee, I just enabled admin toolbar. Hey, Vova. I have a question for you. Is the other token supported by the language or how does that work with language? Good question. We are multi-lingual theme. Let's quickly have a look at the extent. Let's see if there are any multi-lingual. I actually haven't noticed any difference with the token patterns, but let's just so. So we have multi-lingual nodes. So there's no language code. So if you know how multi-lingual is structured, there would be two different nodes, node IDs, really. So if you look at the structure here in U-Mummy, there's a Spanish recipe and there is a, so here's a Spanish recipe and there is a, and there's a English recipe. So it depends on which one you actually can keep the language of the particular node. Is there anything more specific you want to find out? Oh, good. Vlad, are Sarah and Wellington going to need to wrap up in just a moment? Because we are running a little bit later than you guys, Sarah and Dylan. If people would like to do more Q&A, I think that's a fantastic idea because that was a really good presentation. I want to quickly, from our end, just say thank you and talk more about it. Not only is it interesting content, but it also proves that we can effectively make this trans-Tasman content-turing work, including when it's technical. So yeah, that's really great. I would like to start sort of wrapping up on our end, just because it is getting late and I know people need to catch trains. So yeah, I wanted to say again, just a huge thank you to everyone who's able to participate. I can see there's dozens and dozens of people, potentially from all around the world, we don't even know. So this has been a very successful experiment. I'm a huge thank you to local media organisers in Sydney, Brisbane, Auckland, Canberra. Why don't you give everybody who joined in just to post on their Wellington trip or weekend page? That's a fantastic idea. Just so we've got an idea of who was actually in attendance tonight, we would love it if you could just write a one-liner, just saying who you are and where you came from. I'm going to put a link to that right here. Boom. If you're a member of media.com, please jump in, just leave us a comment. I'll give us any feedback on how tonight's content-turing session went. We'll read through that and report back to the committee. But yeah, otherwise, just again, huge thank you to all of our co-organisers all around Australasia. Big thanks to Tom Tugirds and Auckland for providing the Zoom link tonight. Thank you to the Wellington Google Meetup sponsors, have a great next week, all. And likewise, thank you so very much, Adam. Thank you very much, Alex, for being here tonight. It's been great. Well, thanks, Roy. Much appreciated. Well, we are going to put ourselves on mute and we'll start wrapping up. But if you guys want to keep talking, we'll hear you in the background. So, otherwise, a few things. Last question, please. And one last question to Tom for Vanja. Which is, what do you think, do you think there's ever going to be a Drupal 8 or Drupal 9 port of token alias? I actually haven't used token alias myself. Because we're going to have the token alias project page for a laugh. It's just my last joke. So, Drupal.org project token underscore alias. That's probably probably the best, yeah. Oh, yeah. You can put it on here, Tom. Sorry, screen cheers. Oh, it's going to go to there. There you go. Yeah. Very good. All right. Good stuff. We're going on mute. Thanks again for having me out. See you next month. We'll try this again. See you. See you. Come on, see you. Don't cheer, you know. What's the matter with you? It's like you're on the screen. Sorry? You're on the screen. I was, but not now, because the camera is not facing me now. No, it's Ruki or Ajiz, probably. No, since we're doing a kind of joint on it well, can you tell us a bit about the session started at five? Yeah. Thank you.