Hey, this is Jonathan. I just wanted to film this really short case study video for you to show you the type of things that we're doing for this client that we help run the advertising for. And so that if you are running any type of business, right, and you acquire customers online, I want to show and like share with you everything I know about online marketing and how you can kind of replicate the same results that you can that we did for this client, right? Because it's all about systems. It's all about structure team, right? Doing proper ads properly and like doing it properly as well. So knowing your metrics and knowing your numbers very, very important stuff. Okay. So let me just get right into it. First show you exactly the type of results that we're going for and as well as how you can replicate it and the methods and strategies to be very, very transparent with you as well. Okay. So right here, like I'm just going to refresh it one time just so that you can see that there's nothing that I'm hiding or anything. Okay. And you know that the numbers are real as well. Okay. So it's refreshing right now. And let me just change the date. Okay. So these are live sales, by the way. So it's just increasing all the time. Okay. So for example, if I come from April 28th all the way to like May 28th, right, we did $800,000 a month right here. And if you can see, right, we scale up to around what $39,000 per day, but then afterwards it dipped as well. So I'm going to kind of show you and explain to you why it dipped. And it's not because of marketing. It's because of like logistical issues and stuff. Okay. So like you've seen the title at this point. And so 57 days in one million. So I'm not, I'm not kidding with you. So if I go to like the 27 day, right, that's a million dollars right there. So one million dollars and 57 days. And you can see like the slope, right, in terms of how much we scale from like a small to the $3,000 a day all the way to like $40,000 a day. Okay. So I just want to show you the stats behind me as well. Okay. So let me first explain to you why it went up all the way and then why it went down. Okay. So why it went up all the way is because like we're just scaling the S band and scaling the ads. Right. So if you understand and know the metrics behind the business, right, you put in a dollar in how much your role is coming out, right? You definitely understand how fast you're going to scale. Okay. The reason why it dips down is because where you scale too fast, right? And then logistics cannot handle, right? That's where this comes in. So for example, right here, right, we're running ads on Facebook and Instagram. And so there is Facebook page score. What this is is basically when, when people buy from your website, when people buy website on Facebook, right? And then they will issue basically a survey to your customer saying how was your customer service experience with this business right here? Right. So in this case that we were doing fine right here, 3.9, whatever. And around 4.2, you can see on May 6, right on May 6, we're still trying to scale. On May 6, we're still trying to scale out the expenses stuff, but there's a bit of a delay. So once the logistics start cannot keep up with the actual demand of the sales, right, then the sales just dip all the way. Okay. And when that happens, it also affects our ad span as well as well as affects the reach of the ads. So making our ads less profitable and decreasing the raw as a result. Okay. So you can see here, that's why the sales are in a sense starting to slow down a bit. And that's kind of hurting our stuff. Right. So the reason why is that is because so let me show you like a bit of a macro perspective, right? Everyone starts from somewhere and there's no such thing as a business who is like churning out these levels over time. Right. So keep in mind, you can grow very, very fast. And I think you'd be surprised with the numbers. Okay. So for example, these, this client that we worked with, right, we started working with them since October, 2019. And in September, they were just a $5,000 business, $5,000 a month business. So can you imagine the growth scale right here? So in September, it was $5,000, right. And then the first month of working with us, right, we scaled it up to 94,000. Okay. So you can see 94,000. And if you just give me one more day, right, you can see here, right, it's a $5,000 to $100,000 per month right here. So you can see. Yeah. So like I want to give you another macro perspective where, okay, so like there's the lockdown situation happening and stuff like that. And so if when you look at it and the macro view, right, the reason why we were not able to scale at first, it's not because of our ads or whatever. It's because the stock was just stuck in some place in China and they're unable to actually bring it out of China. And so like my client was like, okay, we can't just let this thing happen to the business, right? You can't just not sell and not try to scale just because there's this situation here. So in this sense, like we started scaling and decided to do so just because like, hey, the stock is either going to come at a later date anyway. So might as well scale now, get the money first, get the cash first and get the sales first. And then afterwards think about fulfillment later as well. Okay. So that's kind of the background about the entire business. And I hope this gives you an idea as well. Okay. So what happened between like the April, April and May? Okay. So I'm going to show you a day by day, the ad spend and the breakdown as well. So to give you a sensing of how fast we can scale. Okay. So I want to show you the backend first, which is the email marketing. So keep in mind, these are ads. We're going to pay traffic here. We're paying for our message to be in front of people. And so we can scale aggressively and that's something you can control. The backend is email. And basically you can see here, right, for the month of $800,000, 16% of the revenue is driven by email. So $131,000 in sales right there. And that's pure profit, right? Because you don't pay Facebook or Google a single cent to acquire these customers. So these are your most profitable customers. And yeah, basically the email list is very, very important to protect as well. Okay. So you can see here, we set up a few very, very simple abandon card sequences, welcome series, accounting for in the Cleville email marketing software. And then we also sent a few really simple emails basically based on the occasion and the holiday as well. Okay. So like I'm not an expert email marketer by any sense, but like you still can get these results if you set your flows, automations correctly. And that's basically the backend of the email. All right. So this is, okay, let's go on, what's called on a day by day basis. Okay. So for example, let me show you so far on April 13, right? It was like 2000, 2000 in sales.  So is it April 13? Yeah. So give me a second. So if I come in here and if I go to April 13 and I just update, right, on this day, you can see we started really, really slowly. Give me a second. Yes. Okay. Can you see that? Yeah. So we spend $469 today to get around what two K in sales. Okay. So for example, a four to five day stretch, for example, the first, for example, the first $14,000 a day, which is an April 19, right? So on April 19, you can see here, for example, April 19 from 460, we scale up to 1.9. Okay. 1.9. So we're slowly and steady rising, right? 18 K day, 24 April, 24. So you can see April 24, right? 2.5. Right. And then let's go a bit 24 K day, May 3rd. Okay. May 3rd. May 3rd. That's 4K. Right. And it rises up all the way from like six to six to eight K. So all the way up, for example, at our peak, right? At $39,000 per day, right? Keep in mind, once you scale up, the ad spend, right? The rewards will decrease. And that is a given because your messaging is not as targeted and the rewards is not as good, right? But definitely if you can keep profit into the business and keep your ads profitable, you're still going to run them nonetheless. Okay. So $39,000 a day. And this is May 17. Okay. So for example, on May 17, how much do we spend on this day right here? Okay. So we spend around $7,000, $8,000 right here. So you can see a very healthy four plus row S and keeping the metrics very, very consistent as well. Okay. What we are trying to do every single time we increase the ad spend is to basically push out and duplicate the look-alike audiences. So you want to launch new look-alike audiences so that you can get into a bigger reach, right? So for example, imagine I was in the perfume niche, right? And then there was like, okay, I can't think of something else. Okay. Like fashion, right? Then you want to go into a different niche such as perfume fragrances, right? So you basically tap onto a different audience and you expand the type of circle that you can advertise to. So for example, on the outside level, right, you're targeting 3 million people. But in a sense, you're the targeting another part of the 3 million people because Facebook only gives you a percentage of that 3 million people. Okay. Hopefully that makes sense to you. And so by expanding your reach, you're constantly finding new customers and leads into the business. And so you will never run out of people, right? So trying to be broad is better than ever, right? On the outside level as well, we do more than 1 million in terms of the broad targeting. And so that allows us to scale our budgets, right? So if you can see here, right, our budgets will never dip below like what, $100 per day? You can see the campaigns that we're running, right? Anywhere is from more than $100 per day to like 1,175K per day. So very, I won't say it's high, very, very high budgets, but it's like high budgets enough such that each campaign is pulling significant amount of reach to the each, significant amount of reach to the campaign. Okay. So people want to talk about like CBO, whatever, CBO tactics and media buying and stuff. And so CBO, yes, we do use it. And if you can see right here, right over this section right here, $200 to $300, anywhere below that, right, I won't use a CBO. And the reason is because CBO is distributed on the campaign level. So the budget Facebook optimizes, right, is to segment and then distribute it based on the campaign level into the ad sets, right? So if there's not enough data on the ad set level, then there's not enough at the top, right? So I would generally for CBO, you go and do ads at the budget optimization, ABO first, and then on the testing phase, and then you duplicate that into a CBO. And so on the CBO, you know exactly that's a winning ad set all the time. And so if there's any metrics that do fall below that KPI, then you understand you can cut and kill. Okay. So hopefully that makes sense to you and CBO try to run high budgets, right? Facebook is very good at optimizing now. So if you can push budget and data towards it, it will go and find the correct customers for you. Okay. Hopefully that makes sense. All right. So apart from that, let's see what else can tell you. Okay. So if you can see here, right, according to my columns and stuff, this is my personal favorite arrangement of what the metrics look like and stuff. So if you want, you can just pause this video right now and you just copy me and stuff. But basically you can see a link clicks. Everything is pushing towards the bottom of the funnel. So everything to the right, right? I can see at one point of view of like, okay, uh, increasing metrics to the purchase, right? So, uh, our boss here, uh, ATC unit purchase, ATC, uh, checkout, initial checkout, and then website purchase. And then afterwards is the row S, right? So every time I come in and look at the ads, right? All I see is I scroll to the right and I see row S, right? That's all I care about. Okay. The, I think people are too inundated with the data where they see too many things at one time and they can't make a decision based on that, right? Because all they see is too much data and then they, they, they, in a sense, it close the judgment as well. Okay. So another thing I want to kind of teach you is of how we meet it by, it's like, um, you can see here, right? All our campaigns obviously, okay, uh, that's OXG, TOFU, OXG, MOFU, that kind of thing. It's segmented towards, um, basically the temperature of the traffic. So the temperature of the traffic determines the campaign name, right? So this is very important because if there are so many campaigns running at one time, it's really difficult to see what's working and what it's not, right? So if we optimize for one metric, for example, okay, I, I give a last 30 days spent. Okay. Can you see here that on the TOFU level, um, um, that is, um, the top of the funnel, right? Top of the funnel means cold traffic. Okay. And cold, uh, cold traffic, I can see it's $53 per purchase. Okay. Another thing is TOFU, TOFU, TOFU, then BOFU and MOFU. So can you see here, MOFU is warm traffic. Warm traffic is like pitch, pitch views, um, website visitors, uh, Facebook, Instagram, Engagers, people who watch a video, as well as BOFU is your etiquettes and initiate checkouts as well. Okay. And probably a post-purchase upsells. Okay. And if you can see, right, um, on the MOFU level, the cost of purchase is $25 and for the BOFU is 17.1, right? On TOFU is 45, right? So it makes 100% sense that cold traffic is more expensive than warm traffic and warm traffic is more expensive, uh, than, than cold, uh, than hot traffic, right? So like this, right, you can really see from a perspective where it's very easy to optimize where, okay, if this MOFU, which is the warm traffic is actually more expensive than the actual TOFU, then it makes no sense whatsoever, right? So, um, stuff like that is like, uh, very, very little things, but it also cuts down your workflow when you try to meet a buy at the same time. Okay. Hopefully that makes sense to you. Um, yeah. So, um, in terms of like how to vertical scale and horizontal scale as well. So if, if you realize, right, um, our, our increasing skill is not really, uh, consistent, right?  It's not like, um, we're plus 20% every two days or so. Okay. So it's, this one, if it's how fast you want to scale and how fast you can scale, right? So for us, it's like, if I see the metrics from the macro perspective over like a three day span, for example, okay? So if I give it, okay, put it performance, for example, 19 to 22. Okay. And then if I see the rest is extremely strong. Okay. So I can see here, right? Uh, what 9.96 is what? Okay. So 9. Uh, okay. So I'm just purely looking at the TOFU level, which is cold traffic, right? So cold traffic here is, is a tree, uh, 2.85, um, 3.06, um, 3.1, right? Anything above trees, extremely strong already because, um, even though it reports on Facebook, it's a tree, right? On Shopify and on your actual conversions is probably a four. Okay. That's, um, different ad accounts have different behaviors. So, uh, just keep that in mind. Okay. Um, this one, you got to have to fill it out as the ad buyer. And so I can't really tell you for, for this, for this specific one. Okay. That's how, kind of how I see the metrics. And then if that is very, very strong, right, you can just duplicate that, just duplicate and increase the budget, right? Increase the budget and vertical, vertical scale, uh, as hard as possible. Okay. Um, even though you want a vertical scale, right, do you realize we have different campaigns, uh, running at different budgets as well? That's because you kind of want to spread out the risks of your load here. And you don't really want to, um, put all your X and Y basket, right? Uh, one campaign is driving the entire, entire thing. Right. So, uh, having multiple, uh, different, um, assets per on horizontal scale allows you to spread out the load so that your conversions, right? Uh, uh, don't just die with one campaign. Hopefully that makes sense to you. Okay. Um, let's see another thing that I can kind of show you and tell you about. Okay. So, um, another thing I want to tell you is, um, if you're running code traffic, right, you need, um, and you can scale at this level, right? You can scale at, like, uh, very, very fast. Um, the reason why you can do this is because at the top of the phone, which is code traffic, it needs to be profitable already. Right. So, um, our, our KPI or minimum KPI, right? Is that minimum, it has to be a two times row S on code traffic. And the reason why is that is because we can scale very hard, very fast. And we are known for certainty, certainty that, um, on warm traffic is going to be extremely profitable, extremely profitable. Okay.   So another thing that you can kind of use is as well as automated rules. So for example, in automated rules here, you can go into managed rules. And if you see, um, this account particularly, particularly, uh, previously we were using automated rules, but now we aren't. And the reason why is because it's very hard to manage, uh, that when, uh, Facebook doesn't work itself. Okay. So even though we try to turn it on the automated rules, sometimes it does not trigger and it's very, very difficult to manage as well. However, if you do still want to try it out and it actually works on your account, right, you can, um, you stop right here and then you can go and see yourself. Um, you can try different things. Right. So for example, how we do is like, um, if the Royce is more than 2.5, you add the budget by plus 20% increase the daily budget, but plus 30%. Okay. Okay. Hey, can you see here? Then if there's, there are stop loss rules, for example, like, um, if Royce is less than 1.8, right, then you spend more than 40 so that a statistical, uh, significance to your data, right, then you decrease, uh, sorry, then you turn off your ad set as well. Uh, yeah, it sets this one is turn off ads as well. Right. So there are multiple layers where you can stop loss and you can risk manage in a sense. So you are not spending as much as well. Okay. So, um, hopefully this gives you an idea of the automated rule section and, um, yeah. Okay. So, um, apart from that, let's see what else I can teach you. Okay. Yes. So like I said before, every time you optimize, uh, for Royce and stuff, always look at the most bottom of the funnel metric. Right. So don't, um, there's a lot of data that's coming. You see cost per click, uh, culture rates, whatever, whatever. Okay. Don't worry about that. If there is purchase, if there's purchase, if there's lead come through, uh, don't worry about the rest of the metrics. If the purchase for us, it looks good. It looks good. It doesn't matter. What are the other metrics in the game? Okay. So, um, yes, uh, apart from that, I think I covered pretty much everything, but okay. There's, I guess, one more thing that I should say is like, um, even though, um, you're, you're running at, right? Um, all you look is data. Keep in mind you are selling to human beings, right? Human beings are behind the screen. Uh, if you see here, right, a bit insane, uh, our reach. Okay. From, just from April alone, April alone to May. Um, okay. Overall, by the way, uh, I think it's like 4.6. It's 4.6. Okay. Uh, I think it's a bit more than that. Okay. So spend, spend 220,000 over, uh, over a million dollars in sales. So over four times. Okay. Four times. Okay. And then, um, if you can see, um, what's the code? Uh, yes, uh, cost purchase. Yes. Oh, for, for, in terms of the reach, right, it reached over 10 million people, which means that they are like 10 plus million people who have seen our ads, but have not bought from us. Right. So the, the warm traffic bucket is, is massive. When we want to do retargeting, we can do just push it through the moon basically as well. Okay. Uh, yes. Okay. Um, yep. I think that's pretty much it about the ads side. Yes. Uh, the human being things. Sorry. Uh, yeah. Okay. Uh, yes. You're selling to human beings and keep in mind like, um, even though you're pushing, ads and data, you keep seeing everything here, right? Um, you are selling to people, people, trust people, and you've got to optimize the funnel, uh, page speed, optimization, um, uh, page optimization, plugins, increasing average order value, uh, funnel optimization, um, everything from the creative, the video creative needs to be entertaining and engaging and stuff. And, uh, okay. Let's see. Uh, yes. Copywriting as well. Copywriting is extremely important. Call it the target audience and ensure that people know and understand your ad and stuff. Okay. So if you do not call the target audience, you're, you're basically wasting clicks at that point in time, because not everybody is a buyer as well. Okay. Um, I prepared a very short PowerPoint here as well. So I'm going to show you the metrics behind the business so that you can see the entire thing. Okay. So what we actually did was in terms of marketing channels, right? There's Facebook and Instagram. And then we also did some email marketing as well. So you saw the email marketing there. Okay. Um, the entire funnel is like this. It's nothing secret. So I just want to share it with you. So you can see here, right? Hopefully I zoom in a bit. Okay. Can you see, um, it was like product page and then a product page to the checkout and to the purchase. So very standard e-commerce funnel, uh, Facebook and Instagram, the traffic source. Okay. Let's push notifications as well as SMS list over here. And then there's email pop up website. Okay.  So send traffic back to the site. Okay. On the checkout part, there's abandoned, uh, abandoned card checkout sequence. And then after here, uh, there's introduced the new product, which is basically looping back to increase the lifetime value of the customer. So you can upsell them different things as well. Okay. And then, uh, yeah, that's basically pretty much it for the funnel. And as you can see, right? It's like, um, once you understand how the entire macro thing and the perspective works, right? You understand what levels you can pull to really grow the business fast. Okay. Let me show you the entire thing here as well.  And if you can see from the time we work with them, okay. So, um, give me a second. So from all the way from October, all the way from October is round, uh, 1.6, 1.6 mil. Okay. And then on ad span wise, okay. Okay. And then on, on ad span wise, you can see, um, okay, 12, okay, 355k. Yeah. 355k sales. Okay. So, okay, it's a bit adjusted from here. Right. So, um, yeah, uh, because I edited this slide just now as well. Okay. So, um, then the product costs around 37%. So definitely should drop that down in the future. If you want to pull more money out of the business as software costs is 3k, net profit is around 600, 670k. Right. ROI is, uh, in terms of, uh, rose is 4.6. Right. And the net margin is 41% as well. Okay. And then, uh, I think like, uh, we did our job well for, in terms of like, uh, doing the marketing and stuff, uh, but in the future as well, definitely want to try to increase, uh, reduce that product cost, right? So you can, uh, have, have more profit into the business.  So you should have some sort of leverage to ask them to, hey, can we reduce product costs as well? As in the future, right? We want to introduce more email marketing, build out the flows even better, as well as do Google ads. Okay. So Google ads, like, I think YouTube ads is a big blue ocean right now. There's a lot of, uh, traffic right there. There's a lot, very few advertisers are there as well. So we're going to try to tackle that market as well. Okay. So, um, hopefully, um, you've enjoyed this case study and stuff. And if you have really any questions, right, please do and put them down in the comment section below. Uh, I try to genuinely answer any of them. Um, yeah. And please, I guess I'm just going to ask you now, uh, like the video and subscribe, uh, to the channel if you want and stuff. Okay. Um, yes. If you want to work with my agency, you can go to wg-media.com slash application slash form. Okay. I'll put the website link below as well. If you want to check it out and yep. Okay. So, uh, that's basically pretty much it. Um, I hope you really take this information, uh, with you and so that you can really use it for yourself because, um, like I've, I've, I've spent a ton of time in, in, in Facebook ads and learning all this and stuff. And so, uh, I want to give it to you for free so that you understand, like what it takes to actually get, get to this level and yep. Okay. So, um, that's pretty much it. Thank you for watching this video. Um, I really hope you enjoyed it for yourself and yep. I'll see you in the next video. Uh, yeah. Okay. See you soon.


Hey guys, what is up, welcome to my channel. It is that time I am going to be ranking all of my Pat McGrath Labs palettes from worst to best. These are always my most requested videos. I like to do them about every year or so, give or take. And I'm finally sitting down to do the Pat McGrath video after the Bridgerton palette just launched so I could squeeze that in. There are a few palettes that I have that I'm leaving out because they've been unavailable for more than two years. There's a couple palettes in here that were available like two years ago, but anything that's from a really long time ago that I haven't mentioned on my channel for a few years now, I'm not mentioning. But we still have 24 palettes, so that is a lot. If you're new here, I review Pat McGrath products on my channel. Every single palette that comes out, you can expect a review from me. So I have a lot to say and I have a lot to talk about. So let's start off with number 24, my least favorite Pat McGrath palette in the collection. And unfortunately that goes to this guy. This is the Mothership Sublime Golden Opulence palette. This came out a couple of years ago. And to be completely honest, I forgot about its existence, which I think goes to show that this deserves to be in last place.  It really bugs me. But anyways, the color story in here is just fine. Like I like it. It's nothing special, but it's wearable. I'm comfortable with it. But it's so boring. I don't even think about using this palette. And I found the shadows in here to be a little bit more dried compared to the formula that Pat McGrath has in our other palettes. So I just feel like the quality is a little bit down here. I don't love the color story. I don't ever wanna reach for this. I don't ever think about this palette. Here's the thing, it's not about palettes. Pretty much every single palette in this video, they're really, really good. You're truly asking me to choose between my children. This is just my least favorite of all the ones that I have. It's still good, but I forgot about it. Number 23, this one is so pretty, but it just does not give me what I want. This is a Celestial Divinity Luxe Quad and Fleur Fantasia. This was from their holiday collection a couple years ago. And here is what this one looks like right here. There's just a little bit too light on me. I mean, if you like that light look, this is really pretty. It's a style, it's a look, but it just doesn't give me what I want. It's not bad quality. It's good quality. And I like the light, fresh spring look that it gives you, but I don't really ever wanna reach for it. I rarely do, in fact.  I like all of these palettes, but this just fell at number 23. I don't need to explain myself further, it's just there. Number 22, I have the Celestial Odyssey Luxe Quad in deep space divinity. So here is what this one looks like. This is actually from this year's holiday collection. And honestly, the quality in here is really spectacular. I just don't love the tones in here. I find this to be a kind of boring palette. This like blue, brown shadow, pretty much every brand, I feel like if they do a duochrome, it's this one. And then you just get a red, which I don't love really warm tones. You get pretty brown and champagne shades, but you guys know Pat McGrath comes up with some really pretty color stories. So this one isn't my favorite color story, and that's that. Also, I would like to add, you will notice the quads in smaller palettes are going to be towards the end and then the mothership palettes are more towards the top. I mean, I'm sorry, there's no way a quad is going to beat out most of the mothership palettes. You know what I mean? It is what it is. The quads are still really good. Coming in at 21, we have the Eternal Eden Divine Rose Luxe Quad. So this came out in a Divine Rose collection. And this is ranking down here simply because I did not want another rose palette from Pat McGrath. And while this is nice, I have not reached for it too often. It's since it initially launched. And the reason I haven't reached for it is because I didn't need to, because I feel like I have so many other rose tone palettes from Pat McGrath. So this one definitely gets lost in the sauce, okay? I don't think about this one too often. It's very pretty nonetheless, of course. I just don't reach for it very often. I should. Honestly, I'm looking at this and I'm like, let me give her some love. Coming in at number 20, we have the Celestial Odyssey Luxe Quad in Bronze Burialis. Look at this. Again, super duper boring color story, but it is a color story that I do feel quite comfortable with. The formula on this is so, so good. It's so creamy. But again, I have a lot of these tones in my other Pat McGrath palettes. So I haven't reached for this one at all. And this is a newer one. This did come out in the most recent holiday collection and I do love it. But as a Pat McGrath collector, this was not a quad that I needed at all. I like this better than Deep Space Divinity, which is what I showed you earlier on from this collection as well. It's so boring. Pat McGrath played it so safe with these. I'll give her credit where credit is due though. That formula perfection. Okay, number 19 here. We have the Mothership. This is a baby mothership. What is the name on this? Rose Decadence. Yes, you'll see a theme here of many, many rose-toned palettes. This one is very, very pretty. I like this one. The quality here is, again, a wee bit more dry than what I'm used to from the formulas of Pat McGrath. I really noticed this and that golden opulent set. They just were not up to snuff with the rest that Pat McGrath has, but I really like the tones that she put in here. I know they're those rose-tones that are very repetitive, but they are very, very pretty. So this just, I like it, but it's another rose palette. Coming in at 18, I have the Riscay Rose Quad. So yet again, another rose palette. This one, what I love are these two formulations right here because these are not formulations that Pat really has in many other palettes. This is a completely new formula. It's super glittery. That in of itself, I think, makes this palette worth it because of this formula. You also have a really extremely, almost cream eye shadow right here. It is a powder, but it feels like cream. I'm not too partial to the matte shades that she chose in here. I don't know, I wish we could have done like a periwinkle shade and a navy would have been cool. So I don't love the colors she chose, but all around, I think it's a very well-rounded quad, really, really pretty, kind of unique when it comes to her quads. You'll see, but I really do like this one a lot. 17, I have the Celestial Divinity Luxe Quad in Interstellar Icon. This one is so pretty, particularly for the blue. I really love it. And then I also love putting the shade all over the eyelid. I'm not too crazy on this shade and then this shade, of course, is really pretty. It's not a quad that I really want to create a whole look with. I find myself reaching for these shades individually, but it is really gorgeous, kind of grungy tones in here. You have this cool purple-blue shift, which looks absolutely gorgeous all over the eyelid. So I really, really like this one. Number 16 is the palette that I am wearing right now. Can you see this? I love this look. And this is the newest Pat McGrath palette. So this is where the Bridgerton palette is going to land. I love, love, loved this. Oops, when I first got it, but the longer I've had it, the less I like it because I feel like it's not as versatile in the looks that you can create because you have two pinky tones which you have a billion of and you're always gonna use these as your crease shade for the most part because they're the base matte shades here. You do have this matte as well, which is all over my eyelid, which by the way, I did film this look so it should be on my Instagram or will be up very, very soon. This is an amazing shimmer and I love this blue lid topper here, but I found a lot of the looks that I created with this palette really did look the same. But nonetheless, I love the colors in here so I keep reaching for it because even though I'm limited, I feel like in the looks that I can create, these are colors that I really, really enjoy playing with if that makes sense. But it's not Pat McGrath's best. Coming in at number 15, I have a Blitz Astral Quad from Pat McGrath. This is the Iconic Illumination Quad. I believe it's still available on the website. I don't know, but this one, oh, it's so pretty. It's those basic neutrals, but honestly, the formulation in here, so they're the Blitz Astral Formulas and then you have one special glitter shade. I have found myself reaching for this for my neutral looks super often. I especially love these two to put all over my lid for a neutral look. There's something about these shimmers that are still wearable, but they really amp it up. And then of course you have this gorgeous versatile glitter shade that really is truly special to Pat McGrath and makes Pat McGrath such a special brand. So this is by far one of her very best quads. The formulas in here are really great. I love the neutral tones. It's a way to get Pat McGrath in a more wearable form, really great. 14, we have the very first and my least favorite mothership, but of course it still is really, really great. This is the Decadence Palette. So this is actually one of my newer palettes. I just recently replaced my old one with this and it's not a palette that's from the mothership line that I'm jumping for joy with, but when you feel how smooth and creamy these shimmers are, it's unbelievable, really. So I grabbed this a lot of times for lid looks. Like there's no mattes in here, so I do normally reach out into other palettes when I use this. These are like liquid metal on your eyelids. They're that formulation that will swatch the whole way down your arm, so creamy. This mothership palette lacks the Blitz Astral and glittery shades that I love from Pat McGrath which instantly shoots it to the bottom because it's the only one that doesn't have them, but it is a superb, superb shimmer formulation. I also am really not entranced by the color story in this one either. I don't feel too inspired by it. It's just not my typical tones, but the quality, mm. Number 13, we have the Blitz Astral Quad in Ritualistic Rose, another rose one, but these Blitz Astral Quads, by the way, are the best quads that Pat McGrath has ever had and I think the most worthwhile because it's four of her super special formulations. This is the formulation that Pat McGrath is all about and again, it's another boring rose palette but I think the rose tones in here are special given their formulations and I love how this one is a little bit more purpley and then you have a really glittery pink and then just two really neutral shadows that are very easy to wear. So this is a quad that I often reach for just because it has those tones that I'm very comfortable with in my favorite formulation from Pat McGrath. So this one is just gorgeous. Number 12, I have the Sublime Palette. So this is one of her 10 Pam Motherships. I actually just filmed yesterday my beauty buff tutorial which is my monthly membership that I have on YouTube and every month I create a tutorial for my beauty buffs exclusively and this month we chose the Sublime Palette and I really love this one. It's just not my favorite color story, I would say, of all the mother ships and what they have to offer. You'll see what I mean. These are the Blitz Astrals that are out here in the corner. The green is so fun but I'm not gonna reach for that too often. This shade right here in the top right corner is my favorite, it's like a beautiful golden pink but other than this shade, to me the palette isn't something that I'm inclined to reach for color story wise. It's great for the neutral tones, it has those options as well but you'll see what I mean when I talk about the other Pat McGrath palettes that are available. This is just where I happen to fall but I do very much enjoy it. 11 is the Big Holiday Palette from this year. This is the Mother Ship Mega Celestial Odyssey Palette. Now if you are a beginner in Pat McGrath but you really wanna dive in without necessarily breaking the bank for the 10 pound palette, this is the best value I would say. So this isn't my favorite color story from Pat McGrath. I've expressed my feelings on this before. I don't feel the most inspired by this color story. I don't like the mess that she chose but the quality in here is absolutely insane and again that value that I'm talking about and I'm not saying I can't get pretty looks with this. I've created numerous looks that I love with this but for me it takes a little bit more brain work to create a look for some reason with this palette. So I don't jive with the color story as much as I do with the other ones but it's still freaking awesome. Don't get me wrong. All right, let's get into number 10. This is the OG Divine Rose. So this is the first big Divine Rose palette to come out. I have mine in limited edition pink packaging which I love so much and this one is so neutral. You can see it has those rose undertones to it but you see how many pink options Pat McGrath has. Compared to those pink options, this one almost looks brown compared to those. It's very, very neutral and you have really pretty clean shades. This is a palette that I would recommend for a first timer for Pat McGrath if you are a more neutral wearer. If you don't experiment with color and glitter and all of that, this is a good way to get a more wearable formulation while still getting her blitz astral formulations that you're not going to feel overwhelmed by. For me, it's too boring. If I'm reaching for Pat McGrath, I'm reaching for something that's a little bit more daring which is why I don't reach for this one as often but it's a really great rose toned wearable palette. Definitely one of her best sellers and for a very good reason, I totally understand why. Let's get into number nine. I believe, is this our last quad? No, it's not. But this is one of my favorite quads. This is another blitz astral quad. So remember I said those blitz astrals are the best of the best. And this one I love because obviously it is the most colorful one which I think really tops off any special look that you're creating with Pat McGrath. She, believe it or not, doesn't experiment too much with color. She creates pretty wearable tones of colorful shades but this right here I think is the most that she's gotten out of her way to create a colorful palette. And so I rely on this when I want something a little bit more extravagant from Pat McGrath whether it's to pop this shade on the lid, to pop the blue on the lid, to pop the deep, deep purple. Of course she went a little stifled with the gold but I actually also really like this for creating a look in of itself which is very odd since they're all blitz astral but there's something special about this quad that I absolutely love. That's one of my faves, obviously. Number seven, we have the Mother Ship Midnight Sun Palette. Now this one of course I love, guess why? If you know me, you know it's because of the purple shades. I also really love how earthy this palette is. So this palette, if you get rid of these right here, it's one of those more earthy toned shades which I think makes it so wearable for many of you guys but you can still get some really grungy, smoky eyes with this half of the palette as well. You have an option to warm it up. You have a bronze shade. I love this kind of green tone right here. The purple's really, really fun to add in, believe it or not and even, let's take the purple out. You can see it actually is quite a neutral palette. It's for a little bit more deeper tones. So for example, like the Divine Rose, that's like a neutral palette but it's more rosy. This one is a little bit more grungy if you ask me but how beautiful is this earthy toned palette? I really like this one. I don't reach for it as often as the others that are going to come after this but it's a gorgeous one especially if you like those kind of neutrals. Coming in at number six, this is the best quad that Pat McGrath has to offer in my personal opinion. This is the Venus and Fleurs Voyeuristic Vixen Quad. There's something so special about the formulation that's in this one. So you get one mat and three shimmers. So two of which are going to be true shimmer metallics and then another one is a really pretty glittery formulation. I wasn't in love with this palette when I first got it because I was like, ah, we have all of these tones from Pat McGrath already but the quality in here is truly unbeatable. There's something that's so special about this and I reach for it all the time because of the look that it creates is just so pretty. You don't need to put the glitter on and you get such a pretty easy quick eye makeup look that looks like you spent so much more time but of course, your girl likes glitter, pop a little bit of the glitter on. It's stunning, it's a duo chrome glitter. If you were to get any quad, this is the one that I would recommend. I think it's her best quality and most well-rounded quad. Number six is the Mothership One Subliminal, a very slip-on palette if you ask me. It's always been one of my favorites. So you're going to like this if you are into cool tones or are looking to add more cool tones into your collection. So take a look, look how work-friendly this could be. And you can see, runs very, very cool but I do think, I mean, cool tones are more popular now but when this first launched, there were not a lot of cool tone palettes in the market so this fulfilled that for many years which is why, well not many, but for a few years which is why this has always been in my top. I also think they have some of the best Blitz Astral shades in here. This palette is the best for layering. You can layer any of these shimmers over like the brown or black and it's just going to transform these shades which gives the palette so much more versatility. You can create so many different looks on multiple occasions. I've layered this over the navy, I've layered this over the black, I've layered this over the black and this over the black, this over the brown. The perfect palette for layering and it's just so fun to play with. It is essentially kind of one of the more boring mothership palettes from Pat McGrath but I actually find it to be one of the most versatile and fun to play with. Coming in at number five, we have the newest Pat McGrath palette and I did not expect this to end up being one of my top mothership palettes. I obviously liked it, it was so, so gorgeous but I didn't think I would use this as often as I ended up using this this year. So take a look at this. You can see we have more rosy tones which I think was a little bit off-putting to me. I mean, there's so many rose palettes here but the shimmers in here, I can't stop reaching for them. I think there are the prettiest shimmers. So this palette is one of my most used from Pat McGrath this year. So take a look here, I mean, even though, yeah, we have more rosy tones, they perfectly complement the shimmer shades in here which are the things that I go for, okay?  You have this really crazy sparkly pinky one and then this crazy sparkly purple one and then the rest are just in the background. It's about these two for me. So I reached for this one a lot. It also has a really fine multi-chrome shade in here which is very good quality as well but it's those two shades on the end that really push this one to the top for me. Number four was at one point my all-time favorite Pat McGrath palette. It's falling down, you know? I've changed over the last few years in the makeup that I wear but this is the bronze seduction and this is another one that I recommend for first timers when it comes to investing in a Pat McGrath palette because it is a huge investment, geez.  But how pretty is this? I'm looking at this and I wanna pull this out again. I love that she has different tones of like a plum, a dark brown and a warmer brown. You have some bronzy shades in here, of course and then you can really play it up. Well, first of all, look at the base shades right here. Great for every day. She always does this with her mother ships but then you have these fun colors right here. You have like a green to pink shift. You have a white to green shift in here. You have a classic really beautiful rose and then you have a really warm shade which this cranberry and plum together are fabulous. So this palette has created some of my favorite everyday looks. This is a palette that I go for when I don't want to be too crazy with my makeup but I still want that rich, unique Pat McGrath look. So this is the perfect line for me between wearable but still a little bit more bold and so many neutral lovers also do really enjoy this palette especially if you love a really rich eye. It's also a stunning palette for deeper skin tones as well. So this is one of my favorites. I believe it is one of her best sellers and for a good reason. It's definitely one to consider also if you are looking to purchase one of your first few Pat palettes. Number three, this is truly such a personal choice but I love the color story so much and I love the quality in this one. This is the Celestial Divinity Palette. So this actually has two palettes in here that Pat already had launched. She had a limited Star Wars collection come out a few years ago and there were two palettes. This is one of those palettes and then this is one of those palettes. I actually used to have them. They are my moms and I was perfectly happy to pick this one up. I love the color story in here. It's because it leans so purple that I'm very drawn to it. I love that we have this green punch in here and this red punch in here. It's one of my favorite color stories from Pat. It's a really great formulation. I feel so much more inspired from this palette than I do the Other Mega Mothership palette that I shared with you and I think people like this one but most people prefer the Other Mega Mothership that I showed you. This palette makes me feel so much more inspired and I feel more comfortable with the tones in here. It's very odd, but I do. Okay, number one and two.  This palette I'm about to show you was the number one but ultimately I decided it did not fulfill what I wanted to be number one, okay? The reason this was almost number one is because it truly was the most used Pat McGrath palette by me and one of my most used palettes of 2021. This is the Mothership Divine Rose II palette. I have never looked at this palette and went this is my favorite palette but I grab for this palette all the time. It really just has those tones that I'm looking for and I didn't think that it would. I really always have liked this palette but I've never looked at it and gone, wow, this is the palette for me. This is my favorite palette. But dang, I just keep reaching for it and it's just, it's inexplicable. It's, I can't explain it. Why do I keep grabbing for this? I can tell you I love to use these two shades as blushes and I just think the pink and gold are such complementary tones. I feel comfortable with this color story. It's that color story where it's like, it's not completely boring. It's not brown like Divine Rose I and Divine Rose I will look very brown compared to this. It's Amped Up, which is what I want from Pat McGrath but it's still comfortable to be worn. I love that there's a multi-chrome in here which honestly I don't really like this multi-chrome but I just like having it. The shimmer right here is super stunning and it's just within a comfort zone for me and if I want to use the Pat McGrath formula and I'm going somewhere in public I don't want my makeup to be crazy, I grab for this. So yes, Divine Rose II almost hit number one but I didn't feel satisfied putting this at number one because I don't look at it and completely melt to the floor.  I believe this has been my number one before in a ranking. What belts my heart? It's not as used as Divine Rose II but when I think of Pat McGrath and when I want to reach for Pat McGrath this is the type of palette that I think of where her genius as an artist really shows through in this palette. So this is the Mothership III Subversive Palette. It's always out of stock and for good reason. It's by far I would say the most unique palette in this line as well. If you can get ahold of it, it's so unique. So take a look at this. It's really, really a deep palette but it is so fun. You can create so many different looks. It's extremely versatile. This also just like the Subliminal Palette I feel it's so versatile to layer shadows with because it has this black and this brown and this glittery black. You can do so much with the end here with the green, the purple blue, the white pink and this like rose gold pink. It's just my favorite. I want to go further into detail about this but I can't other than it's just the perfect Pat McGrath palette in my opinion and I really, really wish she would launch palettes that are a little bit more risky like this because this is not a classic wearable palette that she creates. You know how normally when I cover this you can see how wearable the palette is? This is deep, this is smoky, this is rich. It's more artistic and editorial and that's why this has to be number one. You guys know I'm such a strong Pat McGrath fan. I love her makeup line. I love the products that she comes out with but this is what I want from her. This is why I follow her as an artist. Anyways, there we have it. Those were all 24 Pat McGrath palettes that I have ranked for you guys from worst to best. Let me know what you think of my rankings. I know a lot of you guys use this as guides to purchase your palettes so I hope this video was helpful for you and if you aren't subscribed to my channel make sure you are because I have a Natasha Denona rankings coming very soon as well. Thanks for sitting this one through with me and I will see you guys in the next one. Have a good one.


So first of all, if you take photos, please share it on Twitter, and you know the hashtag, right? Oh, no one has told you. Hashtag Drupal South is where you could follow the pictures and event and connect to people who are in the same event or maybe the same venue, and also if you take a photo, it's good if you could just tweet it. So maybe, okay, they don't have a Twitter hashtag, the Twitter mention here. That's fine. So hashtag Drupal South and I think we also, yeah, Sparxy is there. I will tweet right now. So if you follow the Twitter stream, you will see the hashtag, ready to go? Yeah. Okay. Cool. I'll let you introduce yourself. Morning everyone. Oh, thanks for coming along to our session on a module a week or how I learned to stop worrying and love the open source. My name is Dave Sparx and it's my pleasure and my privilege to introduce some members of the Sparx team who have come along to talk about our experiences with this little initiative that we kicked off. The clicker stop is working. And that's the talk folks. Possibly, possibly, there should be a next part. Welcome to our talk this morning. So what do we do? So what do we do? We asked ourselves that question a lot as we went through the process. We came up with this initiative three months ago, possibly on a Friday night or definitely after work and definitely over some beers. But the idea was one person pushes up one Contrib candidate at least one a week, every week for the rest of the year. Keep it simple, right? We thought that's pretty simple. How hard can it be? One Contrib a week. And another question we asked ourselves a lot, why did we do that? Why did we commit ourselves, commit our company to that course of action? Well, we've been doing Drupal since 2007. We've always worked hard to try and give back, sponsoring conferences and meetups, individuals contributing on their own. 2014, 15, we organized the D8 sprints in Auckland and Wellington. But collectively, the overall effort and the impact was far short of where we wanted to be. Local community sprints, getting people together to push Contrib up, that was really hard. A little bit scourging sometimes, not much progress. People who are used to getting stuff done and making the code fly found it really frustrating to not make the code fly. Client work, we're a professional services agency. Client work usually takes priority. I've been selling web dev by the hour for 20 years and we're a pretty classic client services business. We always felt like a small business and not putting the client work first. It felt like a risk. And change is hard. We've been around 11 years. Some people on the team have been there the whole time. We've got a number of people who work here, five, seven years.  I didn't feel like rebooting my company and starting again. But how do you introduce some incremental change that actually takes and makes a difference? We've tried lots of different things to make changes and the small changes always fall off the fastest. How do we do it? How do we do this modular will be initiative? Well, it's my prerogative to leave that to the team to explain. All you need is a tech guy, all you need is a tech guy. G'day, I'm Dan. I'm a Drupal.org moderator, documentation maintainer, stuff like that. I spend a lot of time in the queues talking with contributors from all over the world. I spend hours a week trying to get Drupal folk, contributors, potential contributors to collaborate, to clean up their codes. And to find ways to plug things together. I back a bunch of project applications saying, yeah, that's cool, but why don't you just join forces with that other thing? So with that in mind, our tagline probably makes you cringe. We've got lots of modules. We don't need another module. But the point is that adding yet another module is not really the goal. There's too many modules out there. And Drupal, it's long been the case that just choosing which module out of the plethora that there are out there is actually one of the real skills that we bring to the table. We don't need to add to that confusion. We've got lots. We've got thousands in Drupal 7, thousands more coming up in Drupal 8. If you're watching the queue or the tweets or whatever, there's something like five new Drupal 8 modules coming out every day. We don't need another module. That's not even counting the sandboxes, the unofficial stuff, the things that go up on GitHub. And that's a lot of modules. We've got a lot of modules as well. I went through the Sparks code base, and from all of our legacy clients, aggregated over the last decade at least, 4,400 different custom modules. Not all of them custom, some of them are devs or branches of genuine contrib stuff. If you're here for the talk that was just given previously, they talked about 160 different custom modules in one doc root code base. That's pretty scary, but we're just as bad. We've got so many modules out there. So there's chaos out there. There's a large amount of each to their own. Everybody's fighting for their own thing. We're a medium-sized dev company, I guess, by Australian standards, probably a small one. And I think this is seen in many other agencies. It's certainly evident in the sites that we inherit from other folk, other agencies. People have written their module once, dropped it into the project, and left it there to rot. This is only going to get better if we start to cooperate. We already have the code. It's not a supply problem. It's a distribution problem. We need to set it free. So module a week is not necessarily about writing new modules. In fact, that's the bottom of the list. It's about liberating the existing ones. We need results. We need deliverables. So I started with the manifesto. We want measurable achievable targets. We need this to socialize it to the team, to say, have you succeeded? Have you not? We needed it to socialize it to the producers, to say, we want to put some time aside for this guy to do this, and at the end you will get a result. So the results are things that will achieve progress. If you take an existing private or written once for client project, make it open source, boom, you've got to win. Somebody gets the yeas on the channel that we talk on. If you take a Drupal 7 module, make it a Drupal 8 upgrade, that's a win. Boom, we're winning. If you take something that's in dev out there, maybe in Contribland, maybe it needs a bit of testing, a bit of pushing, a bit of thumbs up, RTBC on it. Take a dev to stable, we're winning. If you take a sandbox, make it promoted. Some of us already have sandboxes and don't really feel like it's quite ready for the public. It's OK, get somebody else to test it, get it promoted. We are winning. That's what we're trying to do, that's what we wanted to do. However, it's hard. The hard stuff is not the code. We're already good at that. We've got a bunch of professionals, PHP developers from way back. Writing code is not hard. The hard stuff is shifting to a reusable by default sort of a mindset, and that's what it's all about. So there's a few key points that will actually help us. The first one, you've got to get it up there, you've got to get it out there, you've got to get it public, you've got to get it seen. You've got to get it witnessed. It's got to be public or it's not open source. The second thing is, the stuff that we wrote was dirty, dusty, and grimy. We needed to polish it up. We needed to make it shiny. We needed to make it attractive and get attention to it. This is a really important part of the open source side of things, often neglected. You can't just put it up for free and say, yeah, it's there. You've got to say, and it's good, and you want it, and you want to pick it up and play with it. Make it shiny and chrome, polish it up, be proud of your code. That's something that doesn't always happen with stuff that you've just written once for a client, stuff that you don't expect anybody else to see. Doesn't happen. Even harder part is pushing it through the issue queue. You've got to write documentation, you've got to write explanations, you've got to write instructions on how to test, instructions on what it's supposed to do. If you're going through the full Drupal.org project process, we know that's pretty painful. If you've got any project application stuff in the queue, talk to me, I want to help you push it through. I do have that magic button, but I will be hard on you at first. So pushing it through the issue queue is really, really hard. So all that hard stuff, we did do. We have team members who each have their own story. They've each had a little different journey, so I'm going to hand that over to Deewa. Hello, everyone. My name is Deewa, and I'm a member of the Sparks Backend Development Team from Auckland. I've been a member of Drupal.org since I was 16. I'm actually a second generation Drupal developer. I have over 150 commits to Contrave Modules. While working for Sparks, I've picked up maintainership for two abandoned modules and also contributed to four projects myself. So while we've been neglecting open source contributions a little bit, they haven't been entirely forgotten. So I was the first to volunteer for the Modular Week Challenge. The main targets of our efforts were to find an open source Contrave Modules, which we had already built. And in my case, we had already built a completely custom implementation for the Photoswipe Library for Sabira, New Zealand. And yes, it was another slideshow module. At the time, our designer had come up with something that the existing Drupal implementation of the library didn't quite support. We were pressed for hours, so we went for a quick custom solution with a couple of theme hooks and a few JavaScript tweaks. So for Modular Week, I decided it was best to extract those customizations, create a dependency on the existing Photoswipe module, and so Photoswipe Extras was born. And I'll show you what that looks like in a few minutes. Extracting and rewriting the code in a usable manner, I'm gonna go back one, sorry. Extracting and rewriting the code in a reusable manner took a whole lot more effort than the initial implementation. And while looking for the best way to do this, I realized there were a few things that had been done that weren't exactly by the book. So it was good that we decided to clean this up before something went wrong. Now, it was Friday, where's the code? Dan had to remind me that Drupal Sandboxes are free. It's better to have something up that doesn't work than absolutely nothing at all. And part of the process was to get our development out in the open. I needed a good reminder there. Another tip that I can share is I started using the issue queue on my Sandbox to track what I was working on and what I needed to work on, and the team started using that to get feedback as well. So before I move on, here's the, starting halfway through the GIF here, sorry, don't wait for it, there we go. Before we move on, here's the Photoshop extras module in action on Sabaru. You can see the masonry in there, the zoom in on click when it opens. There's a custom toolbar on the right-hand side. And we have video playing supported as well via YouTube. And all of these things were not supported in the existing Drupal module at the time. So with the Sandbox and the basic features in place, it was time to get some feedback. So within minutes of sharing my Sandbox URL with the team, the feedback started pouring in. Can you expand on the module description? What does it do? What makes it different? Where's the read me? Yeah, I'd actually forgotten to write a read me. And as people coming back have done code review, automated code review, nice looking through functions, saying hey, that was a nice thing you picked up there. Here's something else that needs a little bit more work. Now the Photoshop extras module requires a library, it has a dependency. There's also a couple more modules that were needed for other features like Masonry and video. This is where SimplyTestMe came in. I could provide a link to the dev team and everyone, including the managers, the producers, and even the designers, could get a vanilla Drupal 7 site up and running with all the tools to get testing. It took a little bit of figuring out how to get the URLs working nicely, so I'll share that with you now. You replace name with your project name or your sandbox ID. You can add as many modules as you need via query parameters, especially handy for things that aren't dependencies, but that will expand on your module. And also patches, you'll definitely be wanting to test patches, very good for SimplyTestMe. Finally, some key things that I'm taking away from this experience so far. As I mentioned at the beginning, get those sandboxes up early. Keep track of your development history. Commit early, commit often. It's hard to do contra by yourself. It'll take others about 10 seconds to pick up on obvious things you missed, and they'll also find gaps in your documentation without any effort, because they don't have the burden of prior knowledge. And lastly, try to do things right the first time. It's a lot harder to extract code later and open source it, and once you get into the right mentality, you'll be planning and writing your code with contributing in mind, and you're gonna save yourself lots of time and headaches down the road. Now, a sixth member of our team was supposed to be here to share his experience as one of a few who did their first open source group of contribution as part of this experience. He wasn't able to be here. So Dan's gonna come in here and fill in those gaps before we move on to here Hayden's perspective. So I get to put on a different hat and say, hey, I'm standing in for Jing. Jing's another one of our Auckland developers. He hadn't done open source at all before, which is why I think his story is an interesting one to share. He took the shortcut to promotion. If you're aware of the Drupal Project issue queue, promotion can be hard and you can get pretty tricky. He succeeded. What he did was he took an existing piece of work that had already been written for the client, or different clients two or three times. The fact that the same thing had been written for different clients two or three times was a bit of the problem. So he successfully discovered what the problem was. I'm gonna skip over his slides, I can't do them justice, but what he did do was identify that this was right for plug-in, this was right for something that should and could and should always have been reused. What happened in Jing's story is that he succeeded. He took an existing module, so and normally would stop here. We've written something for the client, it works, it goes into the code base, never gets touched again. This is actually the beginning of his journey. What happened after that was he got it up into a Drupal.org sandbox, success. We've got some real user testing, we've got some tire kicking. A few of the other team members, sort of like said, do this, don't do this, said, this is actually pretty cool. We're doing a payment gateway. We need security reviews. You need to know it works every time. You need to know you've got some really good error checking, so a couple of eyes on that really helped. He got his project application review in there. A bit intimidating, a bit slow sometimes. He got it in there, he did it right, he took feedback. People around the world started looking at his code. Plugins, they're really hard to test. He got some testing done. He got approval from the previous module maintainer and this is where the magic happened. There was already some payment gateway stuff for this PXPay, DXPay. For Drupal 7, he did it for Drupal 8. He collaborated, we socialized the issues, we talked in-stream and out-stream with the original module maintainer, got the thumbs up. Big win, he got promoted. He got promoted to being an official Drupal.org project maintainer from woe to go. Huge success there. That's Jing's story, everybody's got their own stories. Making it happen, making people work together, that's the story. We socialized it, we talked to other people, we didn't just make the code, didn't just put it up there and say it's cool, we socialized it and getting people to work together, well, that's one of Hayden's jobs. Hi, everyone, I'm Hayden. I'm a senior producer at Sparks and I'm here to speak a little bit about what it's taken to manage the process of creating a module a week, how we've solved the concept of the team and how we've worked differently with our clients while still paying the bills at the end of each month. Now, about 10 or 11 years ago, I had my first taste of Drupal and I was on the other side of the table then. I'd just been into a demonstration with some developers that were providing some sites for us and they were talking about nodes and taxonomies and views. The first time we'd heard this and I walked out of that meeting just not understanding anything they talked about and it's what you don't want from a client, zero understanding. At Sparks, we try our best to speak in plain English to our clients, understanding their requirements, asking what they want to achieve, why they want to achieve it, then crafting some nice codes, pretty sweet pixels to live what they asked for. Now, for five, six, seven years, our clients felt special during this phase. They thought we were these code magicians tuning out special websites just for them, sites that were unique and a point of difference and in reality they were and that's a problem. I think we've got a super talented dev team at Sparks. We've created some strange and magical sites using Drupal from home energy rating systems to one of the first media paywalls in New Zealand. There's some cool stuff but the problem was that we were often reinventing the wheels somewhere in the process on almost all of our projects. In hindsight, our Achilles heel had been the fact that we were using open source but we hadn't fully embraced the open source mindset in our dev team. Our dev teams were working in a fairly siloed manner. They were looking at the requirements that I provided from the client. They'd go away themselves and look at a module or a set of modules to try and achieve the result and if they couldn't find something themselves, they'd create some custom code. Any collaboration we did was often after the coding had been done. That meant the feedback they were getting was fairly one dimensional. It was based on the code work that had already happened and how that achieves the goal rather than starting before we started coding and trying to find a nice way to do a bit of reusable code. Now getting a team to fundamentally change their approach to writing code isn't easy. I'm not saying the producer role at the start of this process is like herding cats but let's just say it took some time to get everyone singing from the same song sheet. There's still an individual research phase we go through but at the earlier stage we try and get the dev team to work together. As we've sort of mentioned, we use GLIP as a messaging tool across the company and we use it really well. We have specific channels per job and per project like module a week. At this point the devs get together in GLIP to discuss what we have to achieve, the modules that they've looked at, the modules that we have available on our own sector distribution of Drupal and then we work through to try and find a solution or see if there is scope to create a module that will be useful to a wider audience if it's not there. An important part of our thinking at this stage is the necessity to create a new module. If there's nothing available and we aren't sure if there's a wider audience for a new module, we'll go back and look at the client's requirements, what they want to achieve and see if there's a way to convince them to do it differently that we'll get the same or at least a similar result. Clients can be understanding when you explain the downstream costs of hacking or maintaining custom code. As a producer it's important to give your client just the right amount of information to let them make educated decisions. They don't have to understand the code logic but in plain English the functional process, the benefits as well as the all important time and money factor. I recently had my first real world experience of module a week changing our day to day dev process. We needed to incorporate the Google Places API into a web form for Sabara of New Zealand and this wasn't available out of the box. So the team decided to create a module that would expose the API field as a web form component. You can see an action there. I explained to the client how we were going to handle the dev and that it would add a day or so to the timeline because that's always pretty important to them. They would create the module independently to the site and then integrate it back as we would any other contra module. They were on board, they're a really cool client and they were strangely excited to be contributing to our new approach. They understood that on many occasions they've benefited directly from contributed modules being available to add new functionality to their site and this was their chance to contribute back. I caught up with the client last week and they said they felt a bit like a patron of code. They were able to pay for work that was going to be given back for others to use. It's a great thing when a client has the understanding to come on the journey with us. That's not always going to happen and that's a simple fact. Clients don't often care about a CNS. They don't care about the code, the way it's written and in many cases I can appreciate that. I'm not going to try and force that information on them but if we're able to impart a little understanding of open source, why we work in this way and the big picture benefits for them, it helps the client make good decisions and allows us to make maintainable and sustainable websites. So next up I'll call Marco for his own unique journey. Hi everyone, my name is Marco and I'm working in Sparks for three years as a backend developer. So as Dan said before, we have too many modules out there and why we have had modules? Well, I'm going back because it's interesting that that's part. I wanna tell you why you should still contribute with a module or a sandbox. For example, my recent contribution was a module called SVG Taxonomy and this contribution is from a solution I made a couple of years ago, maybe one years ago for a client which was looking for an interactive map of New Zealand where the region to be used to filter products over the country by the region. So and I've got what I think is a beautiful idea and instead of writing a custom code for achieving that, I've used built-in tools. I've used taxonomy terms and I've created a vocabulary. I had custom fields for my SVG markup and then just add to this vocabulary the regions as turns and for each region the piece of SVG markup in it, I was able using views and some tricks with the field wrappers and markups to render the whole country and all of these and you can play with this straight with this markup to make the region linkable and things like that and you can easily interact with your views using Ajax and do what you want actually without writing any line of code. But this is a great idea. I thought it was a good solution for this client. It does work. You can see it is working as there. You can find some example or reference of that project on the sandbox in Drupal. But anyway, I've got frustrated when I've decided to share it. How to share something, how to share a module when it's made without code. This was my frustration. Well, you can still do that. So you can contribute a module as a concept. So you can create, you can contribute with a sandbox with for example, you can build a wizard module which does some automation to configure other modules or you can create a module which does some example contents for other existing modules. Maybe you can flick some dependencies to get these modules when you enable your example content modules or you can use futures. Futures especially in Drupal Center is the best tool to achieve that. And or you can put out a sandbox just to tell about your idea. So the sandbox could be something to explain a method to achieve something you can put or you can contribute with just documentation or whatever. So don't be afraid to contribute. It's there as Drupal.org is also there and works very well. You have also benefits in that. You can have free tools as we said and as you know maybe you have with your sandbox it comes with a Git repository. You have a beautiful issue queue system. You can have comments, feedbacks and other things. Plus it's easier to share and reuse if you are okay with your module will be easier to be plugged in another project. So and also you can improve your credits and reputation in Drupal of course if you got promoted or just to have an extra credit on your profile about your contribution. And also you can have feedback and reviews from other people or in our case internal feedbacks. But yes these are the benefits to do that and if you want to try this module this is the sandbox page and you can use the simple test me link to try it on the flight on simple test me. Thank you very much for your attention. So how's it going? You might ask and thanks for asking. It's going really well. We've posted great activity from something that's bubbled along there's a grudging activity that happens in the background. Contrib is moved to the front of our dev process and not just our dev process but everything else we do. Our project management approach, how we talk to clients, how we cost jobs and how we manage jobs. For me as a manager and a business owner the most exciting thing is in 12 weeks a change in thinking right across the team. This is a company that's been chugging along doing much the same thing for 10, 11 years.  Amongst the dev team a very mixed level of confidence working on Drupal.org putting themselves out there in open source. Confidence up a million percent. Well done guys it's amazing to see people rise to a challenge and change how they do stuff and change how they've been doing stuff for 10 years. Here's our very sophisticated tracker that we use. Google Doc. We thought 12 weeks we'll try and get 12 things done. At the moment you can see it's scrolling down. We've got about 22 things in our queue at the moment from those 12 weeks including stuff promoted all the way through and there's a backlog of people wanting to add stuff to this. I'm not pushing them along right I'm not chasing them with the stick saying Contrub, Contrub. This is all coming out from the grassroots and it's happening. Anything that happens without any input and effort from me that's a win. Are we happy you know? Are we happy as a team? Yeah I'm super stoked you know? I think it's fantastic. Sure there's been a lot of stress. It hasn't been easy rewiring how we do things. You know it hasn't all been hearts and hugs. There has been some swearing and there has been some messages typed in all caps. But you know, but no more than usual right? It's just about different stuff right? It's transferred the discussion from reviewing and assessing the client's wisdom and intelligence to talking about collaboration and code dev. It's brought the stress inside but it's made us solve the problems inside as well. Most importantly, well quite importantly from my point of view, the commercial imperative has been met right? We've been going for a long time we're a client services business, we're a cash flow business. We depend on people to pay us for our work right? So I can pay these guys for their work. Happy clients, paying the bills, awesome. But I think that the surprise to me the unexpected benefit was that although the work is more front loaded with discussion, the code comes out better at the end. Less rework, less refactoring, less errors, less client complaint plates. So from a commercial point of view, very effective. And again, unexpected, I thought it would be a grind. I thought that in three months we'd get stuff done but that it wouldn't necessarily generate momentum. My experience is that change takes a long time and a lot longer than you think it would. But with this, you know, the right time, the right idea and the right mindset from the crew, immediate gains. Better everything in a few short weeks. Better code reviews, happier clients, all good. What next for us? Well, like puppies, Contrib isn't just for Christmas. We originally said we were gonna carry this through to the end of the year and see how it went. 12 weeks in already, all our new work is getting done like this, right? Everything from client discussions to specs to costings is based around all our code being Contrib or core, right? No more custom code. And that's a big deal for us after 10, 11 years. We have been around for a long time. We have a lot of sites. We've got 100 or 150 sites kind of under our maintenance. Sometimes we don't touch those sites for years. Sometimes the clients have spent thousands of dollars building those sites. And they don't expect to spend thousands more. But our goal is over the next kind of six months, transition all our legacy support into the same approach, right? If we're supporting your site and we're supporting custom code, that stops. There's an end of life on that. There's a sunset on that approach. Yeah. Yeah. Well, it has been such a win for us, right?  We're not supporting those sites anymore. We still need the money from our clients, right? Because these guys don't contribute their time. Some of us do. Some of us do. No, to be fair, they do. To their fear, they do. But yeah, we're transitioning all our legacy support into the same approach. Whoops, didn't hear that slide. Because for me, as a business owner, and for us as a team, doing the Modular Week initiative, it's not just to feel good for the community. We're not just doing this to support Drupal. We're not doing this out of any kind of great altruistic desire to give. We have a lot of charity clients, but we're not a charity. I feel that with Drupal 8 here and now, the way the web is going, the way that Drupal is going, this is a commercial imperative, right? If we don't do this, if we don't take this opportunity and grasp the needle and do it, then we will not be here for year 12 and year 13. It is not credible for a single developer coming one off the ruck to build a substantial and significant website anymore. We've benefited a lot from the Drupal community. It's changed how we do things and what we do. And I think that unless you understand and accept that you need to work like this, to have a future in the web world, to be a champion for Drupal as a great solution, building websites for clients, you just have to do this and we're committing to it. 2017, no more custom code. Yeah, and that's that. Any questions? Oh, yes, hello. Inspiring stuff. You touched on it briefly, but how have your clients reacted to this? The clients that we do discuss it with, they know, right? We sell Drupal and we sell authentic in the Drupal way, right? Not everyone comes to us asking for a Drupal website. They just come to us, I want a website, bro. And, but we explain to them that it's core, it's Contrib, it's open source. We're using code that's put out there and we take the time, you know, maybe over a coffee or a beer to explain to them how that ecosystem works and why it's good for them. And I think that it's hard to touch on this, you know, everything in a short talk. But the key thing is it's not just a dev initiative, right? It's not just saying, hey, you devs, you do this and the rest of the company trucks on the same as before. You have to filter everything back up to how you broker that initial engagement and how you cost the job with the client and how you explain to them how the costs are gonna fall. And if you get it right, it's better. And you say, hey, it's better. And they go, sweet, we'll do it. And if they say no, miss the job. There's no shortage of work around. Hello. I was gonna say thank you. It's great, it's really good to see you. There's a lot of stuff, a lot of modules and people want to help. And module maintenance is involved in helping you get the job done. Then you are showing up, you know what I mean? With the, it's like, you're gonna put everything on Trooper and all that you work on. That's your own custom code, right? Yep, yep. So what if it's like commercially sensitive stuff? It's really, well, I mean, we have had this issue, right? We've got clients who've got like, hey, here's this big NDA, right? Or, you know, government clients who have a lot of security concerns. But I don't see that there is anything in the code that is, you know, that is commercially sensitive.  No one else is doing it. Yeah. We're not really arrogant enough to think that we're doing anything that no one else can do. I don't think that there is- I don't think you're client one thing, but I'll take it. Yeah, yep. Yes, they do, yeah, yeah, yeah. I'm not, I'm not thinking- No, no, no, no. We've had a lot of talks about this. It's a big one. No one else is doing it. Yeah, the reality is there will always be a little bit of that. What we have is guidelines, you know, no custom code isn't in there forever ever. There will always be something that just doesn't fit in the box for whatever silly reason and you commit it and you say, the client made me do this and maybe that shouldn't necessarily go up. We have encountered these, you know, client thinks that they're a special snowflake and they echo their, the thing that you're building is theirs, that will always be a reality. We'll address that as we come to it. It's not a mandate, it's a, we really, really want them not to think that they're special. Yeah, yeah. And putting that to what you said, you start by, to find the value. So in fact, it's the second year of school, truthfully, that's like six million dollars worth of software about the time you can pay them. Yeah, yeah. And it's, I mean, again, it's that commercial discussion, right? Because a client is buying a website off you, but then they are also buying the responsibility and the requirement for support ongoing. Yeah, nobody does on the floor. I mean, we look after sites for five, seven years and we look at stuff that we wrote two years ago and like, you know, self loathing, you know, go, whoa! You know, why did I do that? And this is a really obvious blunt instrument for just dealing with that, right?  To give you a different perspective, client side, so I'm from Brisbane City Council and in our digital roadmap, one of our principles is open source community. And so we actually have briefly go out with the agencies we work with where we say that we expect that the modules that will be developed will be contributed back to the community. It's, you know, awesome. We've found that our clients tend to connect polarized towards two extremes, right? We have our not-for-profit and our government agency clients who have a mandate and are really happy to push open source and, you know, it's not their money so they don't feel quite, you know, they have more of a public mandate. And then we have our more commercial clients who don't care, they just want a result, right? They're paying, you know, for a result and that issue of proprietary IP or special methods was more of a fear than a reality for us. And then, you know, it's like any client thing, right? If it comes down to it and the client really objects, it's about a discussion and then a decision about your relationship. And for us, the cost and the tiers of maintaining a massive legacy code base, it's just not worth it. Just not worth it. Still a very quick point. It's been very, very inspiring and, you know, we don't tend to make, publish many modules because we don't tend to write many. I like yourself more of a white hat than any constant. But we have realised a lot of things through for us is to contribute our things, especially through late. And I'm just wondering if you've got a strategy on that. No. Have you thought about it? The whole theme discussion is that's just a whole other can of hornets. So... How have big communities involved in this? Like, local communities on the grand scale? How are they contributing more to them on your work? Is there any use cases that you've seen in doing what you are not pleased with your work? Yeah, I think you're providing a better approach. This is the best offer in various cases. So, I think that this is a very policy that you can come in and have a right to make it. And I think for the local community, like, I'm an anti-couple, I don't know all these kind of things, and these things kind of come handy for me. This is the reveal. LAUGHTER Like, hey, this is a great story to tell. Sorry, one minute. Six weeks in, it was hard, you know? Tears and yelling. Because it was a change, but you just pushed through and it was good. And I think my last comment is it's really nice to get the feedback. So thanks for that, and thanks for saying cheers, because my take, coming out of the end of this, is to go, why didn't we do this, you know, five years ago, ten years ago? I feel, I felt ten years of shame, right? For like, for 12 weeks of glory. And I would never go back. I would never go back. That's the last question. The last question. Beyond Drupal, what's that? LAUGHTER No, it's just been, you know, other tools you use in the development process. Yep. So I saw a great talk at WebStock two years ago, with Brad Frost, I don't know, look it up, the talk's online, give it away now, and he just said, open source, all your shit, everything.  You know, he's one guy that's really inspiring, but you go, hey, that's a challenge, you know? Documentation, training, how-to's, we'd love to do more of that stuff. But it's really hard to do good stuff for other people. It's easy to do good stuff that you're satisfied with. It's really hard to do stuff that satisfies other people. I finished this because I'm really enjoying it. What I'm suggesting is, because this is a great conversation, and we do really need this in the community, we may propose this as a buff for tomorrow. So tomorrow we could put a buff. What is it? So we could all, those people are interested, we could all come there and discuss this, and also we could continue discussing this as well, but we just need to officially finish this session so we could go for lunch. So two things, if there is someone from Brisbane or Gold Cross here, please come and see me. I want to get some ideas. Second, you could get your lunch from there and bring it to the balcony over there, if it's not raining. Okay, thank you, and yeah, be quick to sit down. Thanks everyone.