So it seems like everybody up here has a nickname so Dr. Stedman everybody's been calling him steady and everybody calls you topper Which I love that's amazing. You have to tell me that story how that happened maybe after the interview This will take a little while Natalie so give me a little time on that witness. Let's get into the interview Please okay fair enough, but you and dr. Stedman have a very long history and you've been friends a long time Can you talk a little bit about how you met sure? Actually, I was at the United States Olympic Training Center back in 1977 When I arrived it's very interesting the sports medicine director at the time said listen topper There's a doctor over in South Lake Tahoe that comes over and visits the athletes. This is the summer of 1977 He said you've got to meet this doctor His name is dr. Stedman and this sports medicine director at the time said he's one of the most unique doctors He has ever seen from the standpoint of not only the profession and knowing what he's doing But he connects with people like he's never seen before and so the first time I met dr. Stedman Instantaneously, I said he's special. Wow, and that ended up growing into a working relationship. Correct. It surely did I was fortunate enough to be at the Olympic Training Center part of the sports medicine staff for the for that of the US ski team one thing led to another Met my partner John Atkins in 1978 summer of 78. That's another story. I love it. It's a great story We won't we don't have time and that led to the fact of 1982 and looking at moving to Really to Colorado Springs Training Center from there 1984 John Atkins asked me to become men's trainer for the US ski team and I was privileged and And it was great. And so I look at that and again. I'm getting my dates. Excuse me 1982 Asked me through 1984 this area of olympics. Pardon me. We won't have a test after this So don't worry. No pop quizzes. I promise. I'm just using my white hair as excuse. So excuse my dates here I get a little mixed up, but it sounds like you've seen so much over your career and over the time that you've worked with Dr. Stedman, what are what are some thoughts that you have on his legacy? Well, I think one of the things that at the time when we started very interesting enough the term sports medicine came about and everyone wanted to use it because it was kind of a catch-all term and Truly I look at one of the first pioneers in sports medicine as Dr. Stedman And I truly mean that not only with athletes, but just with the regular person the individuals that came to see him and he had that that that knack and he was always special that way because he could interact so well and Not only that he had a vision and he was he was he was a physician that always looked ahead What what can be better? What can be changed to make it better? And he is a truly pioneer in sports medicine what sounds as though you are both kindred spirits and thank you so much for taking a Few minutes to talk about it. Absolutely. I want to say thank you very much to the Stedman family They've been just heartfelt for my partner Jai and I and they mean a great deal to us and steady God bless you my friend. We love you. Thank you


Hey guys, what is up? Welcome to my channel. For today's video, I'm going to be talking about the worst makeup products of 2021, the products that did not work for me. So if you want to see what they are, you want to talk some trash, then just keep watching. Hi guys, if you're new here, my name is Morgan. I am a Barati Knowledge enthusiast. I just love knowing anything and everything about all the new makeup on the market and sharing my thoughts with you guys. And while I try a lot of great, amazing products, there are some products that just don't work out for me. So these are the products that I just wasn't feeling this year so far.  I just wanted to let you know if you like the products that I am talking about, that is okay. That is amazing. I am so happy that it worked out for you. We might have very different preferences in makeup, different skin types, all of that. That's why there are so many different brands and items on the market. These just didn't work out for me and I'm going to explain why I don't like them and why they don't work out for me. But again, just because I don't like a product does not mean it's not good. It could very well work fabulous for you. So if you disagree with me, I would love to hear it in the comments down below. Alright, so the majority of these products are more high-end. I have a couple affordable options in here, but for the most part, the high-end options are in here because we pay a lot of money for them, so I expect greatness from them. So those are mostly the reasons why this is all high-end. You know, if it disappoints me, I pay a lot for it. It shouldn't disappoint me. But the first item that we are going to talk about is an affordable makeup item, but it was so big on TikTok that I had to put it in here. This is the NYX The Marsh Mellow Primer. First of all, this is actually pretty expensive for a drugstore item. I believe the full size is like $17-18. That's a lot. For a drugstore primer, NYX really be playing with us. But I did get a travel size, which was great because this does literally nothing for me. I just don't understand. I do believe a lot of people said that this was smoothing to the face. I don't notice any smoothing really happening. That being said, I don't have the biggest pores, but if anything, I feel like this dries my face out. There's no hydration to it at all, and it just kind of sits on the skin. It's an added step that really has no benefit to my makeup routine. And again, remember, I am on the outskirts of this. Most people seem to like it, but I cannot figure this product out. I cannot get it to work. I think one of the most disappointing products this year. I just feel like these products were not on their A-game are foundations. There actually are way more foundations that I tried this year that I didn't like, but these are the ones that stood out to me that I was like, these are not good. So we're going to talk about the two that I'm wearing. So the first one is the NARS Soft Matte Complete Foundation. So many people love this. It looks horrible on me. I look dry like the Sahara Desert, and I've tried all the ways to apply. I've taken all of your advice. I just don't like it. It does not look good on my skin. It's very, very full coverage. It just looks so dry and heavy on my skin, no matter what I do, no matter how much or how little I put on. I can't get it to work for me. Now, I did mix it today. I am wearing it on my face with the Huda Beauty Glowish Multi-Due Skin Tint. So this is the next product that did not work out for me. If you want to see my video of this on its own all over my face, I was a sweaty, greasy, oily, disgusting, looking mess. And yeah, I don't like this either. First of all, this was my mistake, but the color completely off. This is light medium. It's more so of a medium shade if you ask me, comparing it to what other medium kind of toned products are. The finish of it is way too greasy, oily, and glowy. I wish they would have marketed this as something to mix with other products as opposed to wear it on its own because it's a bit much for me. I don't really like it. I do have dry skin, so I thought I would like it. I don't. It's way too dewy. Now, I was able to make this work. And actually, I mixed these two, and I feel like these really counteract each other and all the things that I don't like about them. Because this is so dry, this helps add some dewy-ness, some glow to the skin. This is a little bit too light, and this is way too dark, so it also created a good color for my skin tone as well. This has way too much coverage. This, I mean, this actually has decent coverage, but it lightened up the coverage. But I still feel like this is overtaking the hood. My skin looks a little bit dry right now. But I will say, putting them together, I don't hate my base. It actually looks quite perfected, so together these two look good. But when I'm done with these, I am not repurchasing either of these. They don't do much for me. They're tolerable together, but on their own, I can't do it. The hood is actually a bit more versatile. I'm happy to mix this with other products. But still, you pay a lot for this, and it just doesn't work the way that it should. So that's why it's more disappointing for me. So keep in mind for a lot of these products, it is possible for me to make them work. I created this look. I like this look. My makeup looks good, and it's with the products that I really didn't like. It's just the journey to get there, you know? If I'm paying a lot of money for a product, it should work right away. I shouldn't have to adjust my routine for a lot of these products. I do feel like I had to adjust my routine too much. I don't return makeup items too often just because the waste that hurts my soul to see them just throw the item in the trash. At least it has a little bit more value in my collection for what I do. Bad products or I can give them away to somebody who might like them. So that's why, if you're wondering, I don't return these items really, I mean, I'm very lucky to be in a situation where I get paid to purchase these products and I can help other people. Most of the time, I don't return makeup for that reason, and it's just going into the trash if I return it. Different if this is not your job and you do not get paid to try the products. So that's my rationale for that. Okay, let's move on to the next product. And this is mostly because of the price. So I could not get the Westman Atelier Vital Stick Foundation Stick to work out for me. This is in the shade Atelier 2 in case you were wanting to try this out. This looks super-duper dry on my skin. I don't really love the way that it blends out. I just feel like it sits on top of the skin as opposed to like blending into my skin. You can just see it like sitting there. And this is a very, very pricey foundation. And I have a lot of other foundations that are around this price range. And I'm not afraid to spend money on a good foundation. Some of my absolute favorite foundations are very pricey luxury foundations. But I do feel like luxury foundations if it's a good one has a very special soft look on the skin that I don't find with a lot of other foundations. So I'm not afraid to throw down some money for a good luxury foundation. This is not a good luxury foundation in my opinion. It did not work for me. So this one is probably the most affordable foundation I'm talking about. But I didn't like it. And that is the Sephora Collection Best Skin Ever Foundation. Now I did just recently do a full face of Sephora Collection. I tried a different foundation. I heard this was Sephora's best foundation. A lot of people were loving it. It wasn't for me. Again, just like all of the other foundations that I'm mentioning. You can see I have a pattern here. I do have more normal to dry skin. So you might actually like the foundations that I'm talking about. But this also made my skin look very dry. And again, it looked a little bit cakey on my skin. It looked like it was sitting on top of my skin. Now this isn't the most full coverage of the ones that I'm talking about. It actually probably gives the least coverage minus the hood of beauty skin tint. And yeah, it still looks like cakey on my skin despite it being a thinner foundation. Now I've heard a lot of people who do have oily skin really like that. So that might be the downfall here. I just don't have the correct skin type for it. But I don't know. It's just when I wear it, it just doesn't look good. It looks like I'm wearing a not good cheap foundation. So yeah, not a lot of concealers came out this year. But there was one that I just didn't like. I don't even know that this came out this year. Maybe it came out last year. But anyways, I've not been liking this. This is the Marca Jacobs Extra Shot Caffeine concealer. It's supposed to have caffeine in it to wake you up. I don't know. I feel the same. I've been wearing this on my under eyes and the wear on this is just not very good. And you can also wear this as foundation. It's kind of marketed as being able to be used as both a foundation and a concealer and I have used this so many times. I'd argue this is actually one of my most used concealers this year because for some reason I was like, I'm going to make this work for me. I was determined and every single time my under eyes just did not look good. There's something about it where my under eyes look very dry. It sinks into my fine lines upon initial application. I'm always like, Oh, it looks okay. I mean, right now it looks fine. But at the end of the day, I I've aged 10 years after wearing this. So this just it doesn't work for me. I don't like it. I'm not a fan of it. I tried really hard to get this one to work for me, but it just doesn't I'm going to get to setting powders, but I actually want to go to the cream blushes first is because that's the order that I applied them. And so many cream blushes came out this year powder blushes as well. But cream blushes are what brands seemed to be pushing out. So there were some amazing cream blushes to have come out. But with the vast number that have come out, there also is a lot of ones that I didn't like that came out. So the first one that we're going to talk about some of you, I know my fellow Natasha stands, you guys know I'm in a stand. But I wasn't going to sugarcoat this review. I didn't like the Natasha Denona puff paint liquid blush serums on my channel. You know who you are. I have Natasha fans. I have Pat fans and every time I say something a little less than positive people try and tell me how to make it work. They tell me how they love it and I'm wrong. Like I these aren't worth the money in my opinion. So they're workable. I can make them work. I personally just feel like you have to work too hard to make them work. Now where I like these are with something really light like a skin tint. So if I'm going for a no makeup makeup kind of look, I love my milk makeup skin tint. And then I'll put these on top and they are perfect. But I can also manipulate any of my other cream blushes to work with the skin tint. So I feel limited in where and how I can use these particularly the shades. I believe this is nude and then this one is Daria. Why can I not find the name on here? I feel like the name is not on here. But I believe this is nude and this is Daria. Anyways, particularly these two, they really just disappear on the cheek. I feel like I have to put so much product in my cheek.  And they have this weird way of me not being able to tell if it lifts the foundation underneath or not. Like I feel like I can see my skin underneath. It doesn't move the foundation to make it look bad or break anything down. The way that it sits on the skin, I feel like I can see my skin underneath, which I don't like. But anyways, these are so extremely sheer. I feel like they just blend away. And again, they really only look good with skin tints in my opinion. That's the only way that I will wear these. And even then I shouldn't be limited.  This is the one that is visible, but it looks really, really scary. So that goes to show you how sheer these are, that it takes a color that looks this dark to be able to show up. So I like this one, but the other two are pretty big disappointments to me. We're going to go over the second cream blush that I'm wearing on my cheek that I layered over top of the Natasha, because you couldn't see them. And that is the rare beauty melting blush in the shade nearly neutral. Now this, it's beautiful. It applies beautifully. The problem is, in 20 minutes, I feel like it disappears. In order for it to stay, I definitely need to set it down with a powder blush, but I just don't want to have to do that sometimes, you know? I layered it. So I layered this, and I layered this on top. And I feel like my blush is fading away by the second. Now, it looks like a nice subtle blush right now. I prefer a lot of blush color personally. I put on more blush initially, and it's already fading. It just doesn't last long enough. It's a really gorgeous blush, and I really enjoyed the formula. But if it doesn't last, there really is no point. So that's kind of why I don't like this one. Okay, this next one, I do realize it's partially my fault, or majority, my fault, that I don't like this. But I just need to talk about it, because I spend a lot of money, and I can't return it. So let me complain really quickly about the Chanel multi-use stick in Print & Ye. Now I have two of these, and I've learned I don't like the Chanel multi-use sticks. First time, Shea Maneuse Chanel. I did not like that formula. Second time, with this one, Shea Maneuse for buying this same formula. But these guys have literally no color. Since cream blushes were so in style, I thought that this would be a gorgeous sheer cream blush. But in all reality, it's just like a balm stick. And I feel like they don't really advertise it as a balm stick. And they have a lot of shades of these, which also makes it more confusing for me. If they had one or two shades in these balm sticks, fine. I get it. Yes. But the fact that this came out on a collection of like four other colors, not to mention I got tricked the first time with it in another collection for a color that I thought was going to be like a bronzer color. They both show up exactly like this. So I just think the number of colors is a bit unnecessary. For me, where I use this and how I've been able to make this work, get a little bit more use out of my money, is I just put it on top of my cheek to give kind of like a dewy glow. Since this one is a little bit more pink, I put it on top of the blush and it does give a beautiful kind of highlighted dewy effect. But nonetheless, I was disappointed by this, okay? My fault. I do realize that. But I want to warn others, okay? It also feels sticky on the skin and doesn't set down and my hair sticks to it. I just remembered that's also why I don't like it. So I still don't like that formulation. Not for me. Last one. This was a discovery in my ELF cosmetics video where I did a comparison between my favorite high-end and luxury products to some ELF products. It wasn't my first time trying the ELF monochromatic multi-stick, but it really laid down the fact that I really don't like this product. It is a more affordable product. It's only $3. My expectations for it weren't very high. But with the sheer number of amazing blushes and ELF has a nice cream formula. I have some cream products from them that I really enjoy. Just with that, this is not good. Now it looks beautiful, right? It completely destroys your makeup underneath. I don't know if you didn't watch that video. Just like everything on my cheek disappeared. There was this huge line of demarcation between where the blush was and it got into a fight with the powder and concealer that were underneath it. It just wasn't good. Now this is a multi-use stick. So I used in the example since I couldn't put it on my cheek, on my lips, and it also didn't look good on my lips. It looks super dry and not nice. So don't recommend these. Tempting. I was really hoping this would work out. A $3 cream blush stick. Sign me up, but not when it's this formula. Okay, there are two powders that I really, really, really did not like this year. And the first one is the Tatcha The Silk Powder. I do believe there were a large number of other people who were not a fan of this. But this, I feel like manages to make my makeup look like worse. I put it on this side and I feel like, see my eye looks a little bit more sunken in. My concealer doesn't, it just doesn't look good. You can see it breaking down faster than the other powder on the other side. It just manages to make my makeup look worse. I don't know. I have very high expectations for Tatcha just because they have some of the most beautiful skincare products out on the market. Primer is absolutely amazing, so I was so excited for this. I thought this was going to blur all my troubles away. It certainly did not. This does not do any favors to my skin and for the price you pay, you know? So the Tatcha though, it's so bad that it's making this next powder look good, but it really isn't a good powder either. That is the Beauty Blender Bounce Soft Focus Gemstone Setting Powder. Now you can definitely make this work based on the quantity that you used. So this is what I'm wearing right now. It doesn't look half bad, right? It's a fresh application. It doesn't wear the best, but the thing that I don't like the most about this is if you apply, they got a normal amount of powder. I don't even want to say overapply, but if you apply a normal amount of powder, it creates this white cast on the skin that's really unflattering. It's supposed to have a glowy finish. That's why they call it a gemstone, all of that, but the glow it gives, I really don't like. You know, if you want a glowy powder, look towards hourglass. That gives a more flattering shine. This one almost builds up and creates a white color on your skin, and it's not very cute. And if you apply everywhere, it just, you look weird and oddly shiny. Again, you can see it compared to the Tatcha right here. It looks better. It's holding the makeup better. I used a very, very small amount. That's key with this since I've already bought it. If I use a small amount, I don't mind it. I don't mind the sheen that it gives, but again, you just got to work too hard, and I'm just not, I'm not here for it. Okay, let's move on to an eyebrow product. Now this is a drugstore product. I didn't hear a lot of hype about it, but it's just like, terrible. And Maybelline has a lot of other better brow products, so this one I don't quite understand why it's so bad. I did get this in a PR package, and this is the Maybelline Tattoo Studio Long Wear Brow Pencil. There were so many amazing brow products that came out this year as well. In fact, best year for brow products, in my opinion, just comparing it to all those other products. This is horrible. So this is way too creamy, and it doesn't even create a good line. It looks chunky in the eyebrows. It looks uneven in the eyebrows. It's way too creamy. And again, when you just try and draw a line, there's, it's patchy. There's like some clumps of dark eyebrow pencil, and then it skips. Everything about this, honestly, is terrible. I guess it's long wear. I don't know. I don't even care to really test the longevity of it, because the application is not good. Not good at all. Okay, the next product, it doesn't work bad function-wise. It's fine, but it's hard to apply, and that's why I don't like it. And that is the Makeup by Mario Master Eye Prep and Set I have mine in the shade Light Concept. I really like it. And as far as how it holds the shadow, all of that, it does a good job of that. But application, I just feel like I'm tugging and pulling on my eyes. So there are two creams in here, and then there is a powder. I definitely recommend using your fingers to apply this to warm up the product, because these creams have already dried out so much. I don't know if it has to do with the packaging. Normally, with cream products, you want to screw them in nice and tight. I think of like a MAC paint pot. I originally had sort of a feeling like that, but it's dried out, and I really have to dig in there to warm it up to get it to spread on the eyelid. And even when I apply it to the eyelid, I'm like pulling and tugging to get it to even spread out. I usually have to use a sponge to kind of press it out. And then you set it with the powder and everything's fine. It's just the act of spreading it out on the eyelid.  So I don't really recommend this.  This wasn't it for me. Okay, so I'm actually going to move on to lips now, and then we're going to finish with eyeshadow palettes. But again, I'm sorry. Mother Pat, please forgive me. You guys know Pat McGrath is like probably my favorite makeup brand, but her liquid lipsticks that came out with her Divine Rose collection. I do not like these liquid lipsticks. There's a lot of bad liquid lipsticks out on the market, and Pat McGrath is in there. There's something really unflattering about her formula.  And that is typically the nature of liquid lipsticks, but I feel like this one is even worse than most other liquid lipsticks, and it feels very drying. The positive to this liquid lipstick formula is that it's very thin, but how could it be so thin yet still feel so drying? Like my lips are begging for hydration right now. They feel really, really dry, and it's not flattering on the lips as well. It's just not the liquid lipstick formula I would go to. If you're looking for lip formulas from Pat her lip glosses are amazing, her lipsticks are amazing, her lip liners are amazing. Not so much her liquid lipsticks in my opinion. All right, I hope you are ready to talk eyeshadow palettes. I pulled out a few. I mean I've tried some bad eyeshadow palettes. I'm pretty forgiving with eyeshadow palettes. I really feel like I can make them work, and all of these you can absolutely make work. So we're going to start off with the one that I am wearing on my eyes right now. It's actually two different palettes that came from the same collection. These are actually one of the first palettes that I tried in 2021, and it really was a bad start. So these are the Dior Trio Bleak eyeshadow palettes. So they're different than the normal quints and palettes that they normally come out with, because it is a trio, and let me show you both of them. And I absolutely had to pick these up because I mean the embossments on them are incredible. Now they both kind of look the same. So that was also a battle I had, but the quality on these are terrible. Now you can absolutely make them work. Right now I am wearing the Pure Glow Trio, but do you see how dark this shade is? Look how light my eye look is. I dug in here so hard with my brush. I got zero pigmentation from this. This shade, the top shade in both palettes, it's fine. It's a softer shade, whatever. The middle shade, again, you don't get too much. Looks like almost nothing on my eyelid, just a little bit of glimmer. And then this shade really just drags this palette down. It's a weird sticky formula, like nothing I've ever experienced with an eyeshadow before. It feels sticky and it gives literally nothing. And the fact that there's two of them makes it even worse, because these look almost identical on the eyelids, given the nature of the formula, because the formula doesn't really show up. So again, you can manipulate it, you can get a half-decent look, but this doesn't, it doesn't look like what you should get from the trio. It's nothing like the regular Dior formula. The regular Dior formula for eyeshadows is beautiful, pigmented, soft, smooth, all of the above, everything you could want in a luxury eyeshadow formula. Not these. They are horrible, horrible. And they're so expensive. So that's also why this is in here. You pay so much for three shadows and all three of them are kind of duds. Okay, this next one, it hurts me to put this in here, but I would be lying if I didn't put it in here. And like I said, 2021, a lot of people got mad at me in my reviews. I feel like I've more than ever gotten people telling me I was wrong and upset. I don't sugarcoat my reviews.  And this you can make work. It's actually a very pretty palette, but just knowing how great Viseart is, this was definitely not good from them. This is a Viseart Paris Love Letter Palette. And I hold Viseart very near and dear to my heart. They have been very kind to me as a creator, very supportive to me. And I feel like I've been very supportive to Viseart as well. But this one, it wasn't a hit for me. This shade crumbles into nothing. I wouldn't travel with this because this shade gets everywhere. And there's a couple of the shades that just blend away and they disappear. And because I know what Viseart is capable of, is why this is in this video. There's a number of shades in here that literally just disappear. Some of the shimmers are very disappointing. Like this green shade just blends away if you take a blending brush. So I don't know, there was something weird going on with a few shades in here. Now with the exception of the couple of shades that really don't work, everything else in this palette is completely fine. But it really is like the shades that you want to gravitate to that don't work, which is why this is a major disappointment for me. If you like the color story of this, you love a really soft eye, maybe you're very fair. I actually do think you will like this. I think there are definitely are people out there where this palette is made for and who will enjoy it. But for me, it just wasn't for me. I have plenty of other Viseart palettes that I much prefer. The next one, I'm really scared to mention this but truly it was a disappointment to me. And the quality is very good. So it's not that it's bad. It's just that I don't like it. The quality is good. I don't like the color story though. And that is the Natasha Denona Xendall palette. For me, this is just not what I like about Natasha Denona. This one has formulations that are more catered to people that do not prefer thicker, shimmery, reflective, glittery kind of shadows. For me, that's what I love about Natasha Denona and this palette doesn't contain that. It's more of a subdued formula. So that's kind of strike one for me. And strike two. I just don't like the color curation here. I find it difficult to try and be creative with looks without the looks, getting muddy. It's just not my favorite you guys. I don't like it. Again, formulation is fine. So many of you guys have tried to tell me different ways to use it. The reasons that you like it, all of that. I just don't like it. I've used it many, many times. It's not for me but I know so many of you guys love it and so many other people love it. So don't knock it just because I'm saying I don't like it. This looks like something that you'd like. I say go for it because the quality is great. That's just not what I like about Natasha Denona and not what I look for in a palette from her. Okay, we are on to the last and final product for today's video. And this one I know you guys definitely saw coming because I've made my feelings very, very clear. I was not a fan of the Melt Cosmetics Mary Jane formulation. I know my friend Heather Austin, she loves this. The shades are way too flaky for me. The mattes in here are completely fine but I mean you can already see the mess that is just in the packaging itself. It gets everywhere. It gets all over my face. I'm the type of person I like to do my face makeup first. That's my routine and I'm okay with a messy shadow. That's fine but I have never experienced anything like this. It not only does it just make a mess but this formulation finds a way to embed itself into my makeup and I can't get it off my face. It just, it makes me look a mess. I look horrible and messy. The shimmer shades for the most part. There's a couple, like these two on the end are terrible and then this one's really, really messy. The rest are fine. They're really pretty and the color story of this is really pretty but it's, it's a hot mess express. I look a mess. The color story, beautiful. Can you get pretty looks with this? Absolutely. The looks that I've created with this I really liked. It was the fact that everything else was so messy looking that I couldn't handle it so this one's not, was not for me. Anyways there we have it.  I cannot express this enough. These are just my opinions. Just what I've experienced with the makeup that I've tried and that I like with my makeup preferences. So let me know what you disagree with. I would love to hear which products you do like that I don't like. I think that would be a fun conversation and then there in the comment section. And that's all I have for today's video. I hope you guys enjoyed it. If you aren't subscribed to my channel already I would love it if you would consider taking the time to do so and I will see you all in the next one. I guess have a good one.


Here at Drupal South, our talk today is about how and why we created a modular distribution for Drupal 8 and covers our success and some of our pain that we've had on our journey so far. My name is Daniel, I've worked with Sparks Interactive since 2014 as a backend developer and I'm also the technical head of sector, our open source distribution. The Drupal 8 rebuild has been one of the most exciting things that I've been a part of in my career and it wouldn't be possible without the backing of Sparks. Sector has been really successful for us as a business and we only got this far through all the experience and pain of building sites for the last 10 years. For some of the background as to why Sparks chose to commit to sector and what we did before sector, I brought in Hiker. Cool, so sector in a nutshell. Sector is the open source Drupal distribution that's ready to go and easy to administer. It's built on a flexible framework, provides pre-configured authoring tools, content types, file management, everything you need and more.  It's just already done. Hiker are now supported by an awesome team in Wellington. We have everything from developers to testers to designers to content, everything with a great support by our Auckland office. Sector's been a four-year journey for us at Sparks and all the work and choices we've made have led us to where we are now with Sector Drupal 8. This talked more of multiple times while I was writing it, but it ends up being a case study on our sector experience and why we think modular distributions just make sense. In a few moments, I'm going to hand over to Hiker for a history lesson and some business stuff that's way above my pay grade and then I'll come back and talk about the technical details that are going on in Sector. At the end, if we have time, we'll talk about the contributions that have been made because of Sector and some of the sites we've built and how a modular distribution enhanced that experience. At this point, I'll hand over to Hiker. It's an absolute no brainer. Who wants to click the thousand buttons every single site? I don't.  You have a common tool box to prototype and iterate faster. A common editorial experience, a common customer support strategy, common test scripts, common test strategies and a shared documentation and editor guides. Now you will see this later because we are going to tell you how we met all of those boys in the Sector story. Now, why not contribute to an existing distribution? There are many reasons, different points of use and needs, governance, change control, small fish, yes, small fish, big fish, first an experience of Tenzin and Fragments in the global community, but there are many more. Now, the main reason is that Sector is older than most. So the sector story is four years old, but we started this whole process way earlier, and we were so far down the road when the other distributions came up that the only thing we know we needed to do was to open source, which we did. Sorry, I have to control now. Yes. We decided how we consolidate sites. There was a really interesting talk about automated security updates. We had the same problem in a little thing. You don't want a million different sites that work in a million different ways. Drupal lets you do all of these things, but do you really want to do this? If you reach 50 to 100 sites under customer support? Now, the project was called Nucleus, it was very basic, but the core is still what we are doing today. Nucleus and core standard control heroes, we love and you know that works reliable, and some customers, we did configure a lot. It was easy to use for the authoring tools and content editors, our clients, staff and boards, all done, but at this stage, we had no see. Around 2013, we committed to a full workflow using site building and display suite. Around this time, we also looked for a front end design system or framework, and we choose bootstrap. We moved our infrastructure towards Git and Agus, things that are totally normal now. We moved towards the search based solution on search API and so on, and we had one of our preferred cache solution. The project was quite ignite, but each ignite site was still a clone from a base site using Agus. So we had this core, which nobody was allowed to touch, without, oh, sorry, without reviews. But it was still pretty basic, plus you can't open source this. So there was also a time when Spark's lost the bit for the common web platform to service drive in New Zealand, because it was an interesting experience, we just said, okay, let's try and establish Google. Now, after all of these decisions were made, we still got heaps of RFPs for the need or the tinted at which to have a Google solution. So yes, we can totally do this, requirements look so specifically familiar, and we gathered all tools together, open source that the prototype was called lightning. There's some really good stuff as I kept saying in here. And so we needed to change the name. We learned a lot about namespacing. We need to change the name in the last minute to sector. They were just way faster than that. Okay, so sector second and lessons learned. This is our list. And this is where you have a distribution. Daniel is going to tell you how we did with sector seven. Thanks, Hacker. So deliver your sites quicker and with less risk. All the sites now have the same base, the same configuration we can trust, as long as a developer or a site builder hasn't done anything too funny. We know the basics are just going to work past, reduce your technical debt. We kind of missed this one. Yes, we reduce technical debt in the way that all the sites have the same base and are less custom. But sector in itself carried a lot of weight and a lot of technical debt. So we didn't quite achieve our goals here, not to our standards. Consolidate build processes back and front. In particular, on the front, we moved towards yarn, we modernised our front end tools, we added documentation and processes to use. Now, everyone at Spark, everyone using sector, they use the same tools. Pass. A common editorial experience. This was really valuable. We have a suite of sites, many sites that share editorial teams. We don't want them to have to understand five different admin back ends, five different range of content types. We want it to all just be scalable and shareable so that one editorial team can manage sites. Pass. Our editorial teams, they rave about this. So it's good. A common customer support strategy. It's a little bit out of what I do. But the customer support team, they know sector well. A lot of times they can just fix things without even needing to escalate it further. It just works well. So pass. Common test scripts and strategies. Again, all the sites have the same base. So the same test scripts, the same test strategies. We just build upon them for custom features that we build every site. Pass. And shared documentation editor guides. One of the powerful things about the sector is our documentation site, sector NZ. I reference it all the time. This documentation team has done awesome work open sourcing all of our documentation. Things no longer just really need to exist in one person's head anymore, which is always a problem with the way we do things. So pass. So despite missing one of our goals, we really liked what we did with sector. We're seeing a massive improvement in how we build sites, our processes and our efficiencies. It made sense to us that others might like this as well. So we committed to open sourcing sector in 2015. And we achieved it. Moving from closed source to open source was hard. We had Spark specific data, we had to do rounds of testing, rounds of removal, sign offs, everything. It was non trivial, as you can imagine. So after all that, the important thing is that sector 7 was successful. All things considered. But just to bring us back down to earth, there were things we did wrong and things that just didn't quite work the way we envisioned it. First on being that everything was too big. As part of development in sector 7, while in the closed source, we used a lot of contra modules to achieve the functionality we wanted. The first closed source version of sector had everything. Varnish, solar, media, workbench, maps, it had everything and more. When we made the decision to open source sector, we didn't really strip these things out, we just disabled them. This led to a bloated distribution and module security updates hurt us continuously just by the sheer amount of modules that were in the distribution. Features, not bagging on features at all, there was no other alternative in triple 7 and the team built an amazing tool. I mean, it was incredible. But partly due to our own implementation, it just caused us a lot of pain. We had the right idea of building a modular distribution in triple 7, but everything was just included in the base. So the benefit wasn't really there. Dependency how? Potentially a few people here have done this themselves as well. Because of how many contribs and features we had, things just, a lot of things end up relying on other things. So if you need to turn off a module, you can't or it's difficult because it's relied by four different other things or one other thing. This was a really big pain point with our developers in sector 7. It just was really annoying. Technical debt. To get around the features limitations, we had a lot of custom code in sector. If APIs changed or things broke, things had to be fixed manually and features had to be rebuilt. This happened often with contribs like password policy and web form and the last one is painful to make changes and hard to maintain. Long installation times, features prone to mistakes, long testing cycles just because of the sheer amount of content and config. Sorry, hi, Kya. Sector 7, that's enough. So sector at the age as we worked from scratch, technology-wise, the non-technology foundations might remain the same. So we had this huge head start. We just basically said our tool, oh yeah, sorry. We just said our tool. So now that we could actually build what we wanted to build in the first place, only better. It has the same manifesto, content-first, site building first, same business requirements, ready to go, easy to use, same functionality bundles, same user stories down to the same test scripts. So sector is truly modular. The main value block is the sector starter kit and the sector starter kit can be extended using sector add-ons. So every single add-on sits on its own through the project and the starter kit does what's next for it. Each element in the sector ecosystem follows the same principles. Now some of them are familiar while some of them go way further. So yes, you need some consistent approach to look at. So you need some really standard here. You need some display and store looks back to the starter kit. So this is all what Daniel does on a daily basis. But there also are composite installable. They plug and play. They have test-pented code review. Each add-on has at least two documentation pages on sector and site, one for site builder, one for editorial teams. You have the project pages on blooper.org and you have useful sample content and everything needs to have an online demo. So now Daniel is going to tell us how he cleaned up. Cool. Now that we've looked back at the history and some context, we can look behind the scenes at how we fixed the problems from sector D7. So this will talk about scaling by add-ons, no features, no dependency hell, less technical debt and a talk about the future. So scaling by add-ons. So as we talked about, the first problem was that sector 7 was just too bloated. Sector 7 had almost 100 contra modules. It did everything we needed it to do and more. It was just too heavy. Like I said before, security updates, they really hurt us. So it was time to clean this up. We moved some contra and config into add-ons and as we continued to trim the fat, we saw a 50% decrease or over 50% decrease in the amount of contra modules and as a side effect, we saw a 62% decrease in build size. Both these things will keep dropping further as we trim fat and really clean up our starter kit. Creating the add-on system was something we came up with early in sector 8 and it was my number one priority. We're really starting to see the results of this as time goes on. Add-ons will be covered more as we go, but the idea is simple. In the same way you extend Drupal, you can extend sector. And the last step is removing complex content types and unnecessary config from the profile. For sector 8, we removed everything non-essential and took the distribution back to its roots. It's got a core, it's got a theme, and it's got opinions on what the best practices for the start of a Drupal site are. Sector 7 had years of config and legacy come across from the close source project, like solar and varnish. Does every single site you use have solar or varnish? No. So we rip them out and in time we'll create add-ons. And the same goes for content types. Sector 7 had eight content types, including multi-pages, which is the old version of books, and a media gallery. Does every single site you build really need a media gallery? No, so that's what they went as well. So for a visual representation of what add-ons actually look like, let's have a look at a couple. So if we scroll to the bottom and we go to events, every add-on starts with a landing page. So it's a landing page and then it's got some content. This one here, it says with location map but since Google changed some of their policies and we don't really want to open source our key, let's just pretend there's a map. So straight out of the box you can see there's really nice design. We've got a couple of different displays with blocks. We've got a node view and as we scroll down we can see everything is nice. We've got good realistic sample content. That's what an event should look like. It'll let you see how things are and take them further if you need to. And then if you scroll back down to the footer and open up with a blog, it's the same thing. It starts with a landing page, it's got some nice designs some nice blocks, it starts with a featured blog post and then just keeps going down into some landing page style view content. So if we go into the featured one, same thing, nice style, well-designed good realistic sample content is the important thing. Links and all the links go to our documentation pages so your site builders and your content editors can see some examples and how things should work. And if we have time at the end we can have a look at some of our more complex add-ons like Media Gallery but I think by now you're really starting to get the idea of what an add-on should encompass. So the starter kit itself in the sector has been reduced to four content types. We have page and article, which is article on core, resources and promotions which both come from sector. The remaining content types from the starter kit in D7 have become or in the pipeline of becoming add-ons. This keeps our starter kit light. So for this talk we'll use sector events as our example. Sector events requires three contra modules. Address, geolocation and geolocation address link. In Drupal 7 that would have been three extra contribs that are bloating up the profile that don't need to be there because not every site needs an event. So when you have security updates in sector 8 when addresses a security issue, all the sites that don't use events just don't need to worry. It doesn't matter anymore. It's a win-win. So how are add-ons designed? Our golf add-ons is that their minimal impact. I think all of us have seen how to install a module sometimes. It attaches itself everywhere and then it's a spider web of trying to figure out where things come from, how to remove it. I didn't want that. I really wanted add-ons to be this little isolated bundle that you can just install and remove if you want to. So they're meant to be low impact. Plug and play. They're all just plug and play. You turn them on, they're there, they have content you just go. They can be extended. All config comes bundled in as part of the add-on and when I say here I say and not much more, I really do mean it. Our add-ons come with very little back-end code. Most of the time it's just minor install tasks to do things like set permissions or create site maps, things that aren't well-handled with config at this point. And sample content. This is really important. We have good, we have realistic sample content that's been made by our documentation team. People can really visualize what the content looks like and then they can start extending it and see what they want to do in the future. So I'm moving on to the technical side of things. I wanted to go over what the code structure of an add-on look like. So again we've got the sector events and if we start by going into config and into install and if we scroll down here all the config files that are part of add-on, there's about 30. Everything is just already done. Fields, content types, displays, views, vocabs, it's all just there. And I don't really know about you but I don't want to be clicking all of these buttons and doing all of this config every single time I need an event content type. It's just painful. It's easy to miss. Which one of us hasn't missed a checkbox, an eclipsed field set or not pressed save after doing a thousand things on a form. This just works. So while we're at it, let's go back to events and into the content. So this is using the default content module and all add-ons come with terms, pages, the newer ones come with also media and files. So everything's just there, out of the box and it works. So what I really wanted to demonstrate here is that this is 30 to 35 plus files that aren't part of the distribution anymore. They're in the add-on, the distribution doesn't care about them and if you need them, they're there. It keeps the starter kit light. And more importantly, it keeps sites that aren't using events light. And the other part of most sector add-ons are minor install tasks. So just really little things. You can see that we are granting permissions to content editor. We're granting permissions to content admins. And we are creating XML site map context for the event content type. With all things, like with all most of our add-ons, this is the majority of install tasks that are like of back-end code that's there. There's not really that many moving pieces that can go wrong. The goal is just to do everything that works and isn't going to mess with you. Cool. So the pros and cons of this really become more obvious as we go along. No mistakes. The config is all handled by the add-on and the awesome Drupal configuration system. There's no manually checking or missing boxes. We don't really have to worry about these things anymore. It just works. They're well tested. We use these add-ons at parks and as more people use them, or as with any module, as more people use them, they get tested as they go along. We open source our issue queues just using standard Drupal issue queues. So everything is just there. Everything works. They're tested. And the cons, they're also pretty easy. The add-ons are tied to sector, obviously. If you add sector events to Lightning, it's probably not going to work. And the last one is that things can break if major changes have been made to your instance of sector. Let's say, for example, you delete the body field. Maybe things aren't going to work. So at the moment, they really do require a pretty clean version of sector. We've actually done some kind of preliminary reviews to see if we can mitigate this. But at this point, that's just how it is. So when we first started coming up with the idea of add-ons, I think there was a bit of concern in the team that they would really begin to limit us, that using the same base would make sites follow a kind of cookie-cutter pattern. Everything would have the same look. We want our developers and our designers to actually enjoy their work and not feel like their creativity is being stifled by us. So the add-ons are fully extendable. I mean, they're mostly just standard Drupal configuration. You get all the nice stuff that comes in the add-on and you can do anything extra that you want to. So for this, let's have a look at two sites. Forest and Bird and Torture Learning both use the exact same version of sector events as their base. So if we start with Forest and Bird, we see upcoming events, the same one we saw before. We see a ton of filters. We've got one event per row with a bit of metadata based on dates, tags, an image if it's been applied. And then if we go to Torture, again, exact same upcoming events view. They've changed the label. There's a filter. And now we've got four events per row, required image, bit of meta, and this whole masonry-style layout. Both of these sites, they have the exact same base, but they look totally different. They have their own flares, their own special things, but the same underlying base. So no features. Like I said before, features was the best tool for its time. We bought modular features, but we didn't do it in the right way. And we had way too many features. At certain points we split content types up into a content type feature, a permission feature, a content feature. We had this great vision of the modular distribution. We just didn't quite pull it off in the right way. It made things hard to maintain and hard to keep track of. And to be totally honest, while I can pretend to take a lot of credit for the work in this, before removing the bloat, a massive chunk of this was solved by the amazing work done by the Drupal 8 team and the configuration management system. Changes are easier. I get less grumpy. And things just work out of the box. We clean this up as we go, but it just works with add-ons and the starter kit. And even better when you combine DrashCMI tools.  So again, this has really solved, let's say on day one, with how we decided to build Sect 8. It was an architecture issue. The starter kit only depends on the most critical modules for the installation of the profile. The add-ons, they only depend on the new modules that they bring in. And again, no more features. This was our real spiderweb in Sect 7. With features gone, a lot of the dependency hell just disappears. So with Sect 8, if you need to disable a module on a per-site basis, you don't really have to do this fight anymore or worry that it's not going to work. It just works. Less technical debt. Now you remember from the slides earlier, this was the goal that we just didn't really achieve that we didn't feel right about. So there are countless examples through Sect 7 codebase where we build and change really significant things on the fly to get around features limitations and where things just didn't work how we wanted them to in sector. This consistently led to issues where things broke. Where is it broken? Is it broken in a feature? Is it broken in custom code? Is it broken somewhere else in the module itself? It was just a really annoying debugging process. So in the demo, here's an example of this. Here we're building a password policy from scratch with code to get around a feature limitation. And at some point, password policy, we ran updates and they made this API change with the ID. And the feature broke and we had to figure out how and the fix ended up being this one-liner. There are countless examples of this. Plenty of annoying commits or potentially grumpy commit messages but in sector 8 will resolve this as much as possible. The only custom code we have in sector 8, we still have the install tasks but they're really minor and they generally only touch core or really well trusted contrab things like XML sitemap or remapping sample content. Cool, so on to exciting times, the future. There's a lot to be excited about as we move into the future. For me, the number one thing is adoption. We know that us and some other people are slowly starting to adapt sector but we really want sector to be used on a wide scale. We want to see adaption. We want to see people testing, building sites, playing with sector. Our governance module on sector in Z talks about how to get involved if you want to contribute back to sector but if there's something you'd be interested in but really our goal is just to have people playing with it, trying out the add-ons, trying out sector, giving us feedback. We want more people having eyes on it. So, we're finally moving beyond the beta status. Sector 8 kind of feels like it's been internally in beta for a while. The only thing missing is the 1.0 release and the big green tick on Drupal. We have a couple of small blockers that are stopping this from happening but we really want to fix this. So, the blockers are the... Well, one of the main blockers for me on a personal level is automated tests. We want sector and the add-ons to have an automated test and an automated test strategy. Hiker and I, we both really wanted this all fixed and the 1.0 release before this conference but there's this little annoying thing called client work that just kept coming up and getting in the way. As much as I want to work on sector all the time, there is still a business and we do still have to actually get paid. And the other future plans are to keep developing add-ons. Newer add-ons are always in development for sector 8 as they are needed by clients. Over the last year and a half, we've been making up the missing content types from sector 7 but others are being added to the pipeline as they come up. So, how we develop add-ons. We have a few different processes for how we choose new add-ons for the sector D8 ecosystem. The first is missing bits from the sector 7 version. Sector 7 could be complicated but it had everything. It had workflow, which me and Hiker are talking about tomorrow. It had embargoed content, it had multi-pages. It had editable views, paste from words, solar, varnish. It had everything. So, we ripped all those things out but we'll still need them again so they get added to the pipeline. And the rule of three, this is the rule that I follow. Well, the next two points actually go hand in hand. More than one client asks for a feature and the rule of three. My personal development process is to follow a rule of three which is a pretty classic kind of philosophy. If I've built something twice, I'm probably gonna need it again. So, that's when we think about turning custom code into a library or a module or in this case an add-on. So, just here's a quick example of our add-on pipeline. We have membership and feedback form. These two here are examples of add-ons that didn't actually exist in 7 but have been prioritized for our Drupal 8 clients. Multi-page and workflow, they're both from 7. They need to come to 8. We've actually built workflow in 8, which me and Hiker will talk about. And to make the list not massive, we'll just stop here. Contribute. It's one of our big things. If we see a feature that's having value not to adjust us at Sparks but as the wider Drupal community and adopters of Sector, we publish it. The goal here is to really have all this stuff open source. Open source contributions. So, this was a bonus that I didn't really consider too much when I started building the Drupal 8 version of Sector. Because Sector touches everything from nodes, blocks, media, site maps, everything in between, we've been able to fix bugs and raise issues in core and contribs like the list above. We've also found contribs that we think have a lot of value but have been a bit un-maintained as time goes on, like term condition and advanced form. It's given us an opportunity to take over the maintenance of those modules and keep working in the wider Drupal community. We're publishing Sector and working in this kind of sector world but we want to keep contributing to Drupal outside of Sector as well. On our documentation site, Sector NZ, we have a showcase page. So, on this page, we have a lot of our Drupal 8 and Drupal 7 sites that we've built recently, Heart of the City, Head of the Sector for Forest and Bird, the Ombudsman, Bird of the Year, and Child Youth Well-Being. Great, so that's everything we wanted to talk about with Sector. Do you guys have any questions? On the microphone? How can I add to the process of adding like, is it a contract module that I will add if yes, what happens to the configuration that we exported? So it's all just standard Dural published as contribs. So we have like Sector events, Dural published on Drupal.org. All you need to do is compose or require it, like any other contribe, enable it on your Drupal site, and all the configuration will just be there. Right, so basically it's...  No, so it is still like a task where you need to edit your composer and publish it, yeah. But we haven't done like an old. The only thing that we have done here is to add this block to the starter kit and this module to the starter kit because this is just how the demo works. But we haven't even fixed the buck with the maps because it's just... What you see is what you get. Yeah, that's what Sector looks like straight out of the box. Thank you. What about entering content? Are you using like the body field or Pyra for something like that because I noticed that you have different type of like list or images or different UI elements in the main content of the site. So how do you build that? It's all just using standard Drupal fields. So we have the body field which has our WYSIWYG and all of our like WYSIWYG toolbar and tools. But there's no... In add-ons there's no magic. It's all just Drupal config comes with Sector. There's nothing too scary going on behind the scenes. There's configuration documentation for the Sector add-ons. So it lists everything that is there. It lists all of the components where they are, what we have done. So basically all of this is preconfigured but we also tell you exactly what we have done. And we also further down we tell you if Daniel has done something, I think he has done nothing on the blog. Yeah, so he has done nothing on the blog. There is one where we have manipulated a tweak file. Do you remember that? There is the... Oh, that's the quiz, I think, which isn't public yet. So if you manipulate or if you require patches for additional contribution modules, this definitely requires an additional contribution. Oh, yeah. An example of that is the media gallery, actually. Oh, the media gallery. Okay, so let's go and try to find the media gallery. This is the site builder documentation for the media gallery. And yeah, so these are the contribution modules the trick list that add-on. Daniel also does some incredible stuff where he checks if you have already installed it because of reasons, because as I said, he wants Sector to be yours. So he checks that stuff. And then there should be a note about a tweak file that we have changed. No, it's a core... A core? Yeah, a core patch. If you just search patch, you'll probably be there. Okay. So there's this core patch that goes with that module because something didn't work. Yeah, so basically there's a core issue that we need to fix to make the media gallery work. But because we still wanted to make progress and we still wanted to publish it, we just at the moment have the little note that says if you want to install the media gallery, this core patch is needed as well. But the Sector team is actually working on that patch to get it into core. So I was just wondering about the anatomy of the add-on modules. What proportion of them is just YAML config files? I assume in config store folder, right? Yeah, that's right. And then how much of it is like, are there tweak templates as CSS or is all of that deferred to something else, like the base theme or... So it does, yeah. It does depend a little bit per add-on. Like most of our add-ons are strictly generally just config files, that little few install tasks, and then with CSS, a lot of the times for our really custom add-ons, our really common add-ons, we just add the CSS to our distribution and then just have them disabled by default and turned on or just there in the distribution already because our very clever front-end developer, he has built a modular CSS style that means sometimes for these add-ons you don't even need to add any more CSS. You can just use the stuff that's already there in sector. Yes, there is a base theme in the base distribution. Yeah, yeah. So in this case, Tom needed to put... But the CSS is really... Tom needed to put something in, so it has a dependency. If you want to look at really good, you need to use beta file. I also want... At this stage, I also want to explain something about the use of display suite and view modes. So every single add-on trips with a short teaser and a teaser display and the short teaser and the teaser displays they are built to work in any sector, starter kit view. So it's all really streamlined. So that's probably good segue to my next question, which is how... Have you had issues with config dependencies? So say for example, you've got... Let's say you wanted to add the workflows module, which is in core, right? So the workflows module has a reference to the content types that are part of it. The content types that are part of it are obviously dynamic because they change depending on the site. So scenarios like that, do you just ship stuff that you know is going to be there from the starter kit and then stuff that's add-ons from the events and stuff you just have to manually configure? I mean, if the site owns the configuration, it's not going to be a problem. Yeah, you raise a really interesting... And we talk about this tomorrow a lot. We are full. So workflows are most ambitious projects so far because we just do score, but in the score, most are really amazing work Daniel has done. However, so we are at the moment just in a bit of a... We need to get... Sorry, workflows was just an example. Has there been other... No, so far, so far, you don't need to take a single box, but I promise you that you don't need to take a single box because we ran into this issue with the workflow add-on. And we are not fighting the system, but for example, what Daniel was showing on the XML site map, there's a little install hook because we can't configure the XML site map that it should include this, so there's a little install hook and they're also install hook into the permissions management because everything is just consistent and it just builds on top and on top of each other. And just to say one more thing as well, like for example, we have a content audit add-on, so it's an add-on that really gives your editorial users a lot of control. It just provides extra fields and what we do for that one, because we don't want to attach it to content types, to all content types on install, because maybe you don't want that, we just provide a checkbox in the content edit screen that just says enable, seek the content audit for this content type. So out of the box, it's there but not actually attached and then you can attach it as you like it per go. We have time for the last question. Yeah, I just wanted to confirm that something like this, that ImageFX module is required and there is a patch. I'm assuming you are putting that in the compositor, Jason, off the add-on? For the core patch we didn't at the time, I think there was an issue, but the modules themselves, they're part of the composer, Jason, so you do composer require sector media gallery and that pulls in everything. So this one, media gallery, sector media gallery, it needs a core patch and it needs those modules. So the sector media gallery should be having a compositor.json and that mentions all this as well. Yes, correct. The core patch is the one really unique kind of outlier in all of the system so far. Cool.


Welcome to Think Tech Hawaii, Konnichiwa Hawaii, a Japanese language broadcast streaming live from downtown Honolulu and available on YouTube. I'm your host Yukari Kunisue and joining me today in the studio is Mr. Norio Okada, wrestling coach who was the first Japanese coach trained overseas athletes to send it to the school Olympics. Hello everyone, from downtown Honolulu, Think Tech Hawaii is available in Japanese. Hello, I'm Yukari Kunisue, a host of Hawaii. Today's broadcast is the first time in the world that a wrestling Olympic competition has been held overseas. I'm here at the studio with Mr. Norio Okada, who was the first Japanese coach trained overseas. Mr. Okada is currently in Hawaii and is the representative of the Ten-de-kyo. He is from the Ten-de-kyo Cultural Center. Mr. Okada, thank you very much for today. Thank you very much. Thank you very much. I was told a while ago that there are a lot of passers-by. This is the first time in Japan that a wrestling competition has been held overseas. It's a wrestling competition, isn't it? Yes, it is. The Olympics cannot be held overseas. That's right. It's a wrestling competition in the South of Colombia. At that time, wrestling was held in Colombia. Was it a fight? No, it wasn't. That's right. But it all started a little while ago. Before that, my master was Mr. Hanaharatsutomu. Mr. Hanaharatsutomu. He was a world medalist in the Tokyo Olympics. I see. He was a master in the Olympics for a year. He had already been in Colombia. Yes, he returned to Colombia. His master was the director of the Muhe Olympics. I see. I wanted to go to the Olympics again. Yes. Unfortunately, I couldn't lose in Japan. I couldn't lose, but I ended up in the 3rd place. You couldn't go to the 3rd place? No, I couldn't. I see. I was the only one who went to the Olympics. Mr. Okada was going to go to the Olympics in wrestling. Yes, in 1972. In 1972. You had been in wrestling for a long time. No, no. When I was in high school, I was boxing. Boxing? That's normal. Yes. I did a lot of sports. I didn't do a lot of serious things. I went to a university. I went to a Japanese university. I did wrestling. I see. I did a lot of sports until I went to college. After you entered the Japanese university, did you focus on wrestling? I chose the Japanese university to do wrestling. I see. You were a sports boy since you were little. Yes. I liked swimming and swimming. Since I was a kid, I used to swim and swim. I'm still young now. I was 70 years old.  Yes, this month. Yes, this month. How long did you want to participate in the Olympics? Tokyo Olympics. There is a new Tokyo Olympics video this time. In 1964. Tokyo Olympics was a strong event. I see. How old were you in 1964? I was in 2nd grade in junior high school. You were 15 years old. Yes, I was 15 years old. Did you have a desire to participate in the Olympics? No, I didn't go there. It was amazing. There were 5 gold medals in wrestling. You were attacked. Yes, I was attacked. I was born in 2nd grade. I started wrestling there. I wanted to participate as a world champion. Of course. You became a senior in junior high school. After that, did you participate in the Olympics in Montreal? Yes, I participated in the Olympics in Japan for 76 years. You went to South Korea when you were in elementary school? Yes, I went to South Korea on October 28, 1973. You went to South Korea. It's easy to tell. Of course, there were some people who spoke English. Did you have any problems with your language or cultural differences? I don't know at all. You don't know at all? I don't know where Colombia is. You don't know where Colombia is? I don't know if it's in Africa. I thought it was in South Africa. How did you feel when you went to South Korea? Of course, there were some people who spoke English. Mr. Hanahana, who spoke English, asked me if I wanted to go to South Korea. I said yes. I thought it was in South Africa. There were many ways to become a teacher in high school. My father wanted to work hard in the next Montreal. So your father was a type of person who raised you a lot? He was a father who didn't say anything. I thought I wanted to go to South Korea. How old were you when you came to South Korea? I was 24 years old. You were still single. What was your first impression of South Korea? Colombia is a country with a population of about 4 times as low as Japan. The population is 3,000 times as low as Japan.  Yes, I had a lot of land, but there was a small plane in the middle. I felt like I was going down there. You must have had a teacher, Mr. Hanahana. Did you first start thinking about the Olympics? No, no. At first, I thought it was a good place. You thought it was a good place. After two years, I wanted to go back to Montreal in 1976. You wanted to be a contestant. Yes, I wanted to be a contestant. I was a student at the time. But I grew up in Japan. I thought it was amazing. You mean in Japan? Yes, in Japan. I grew up with a lot of young children. Did you feel like you grew up in Urasimatarou? Yes, I was given up in Montreal. Then I went back to Colombia. Did you have anything to say to your children at that time? I want to live in Colombia in the future. I live in the same country as in Hawaii. Oh, I see. What I want to say to my children is that there is no sea in California. I see. If you don't have a sea, you can live in the same country as in Hawaii. You can think of Colombia as a country. That's right. I showed you the newspaper. Did you think you would let your children live in Colombia instead of adults? That was a meeting with some people. I wanted to live in Colombia for a long time. So I bought a disco. Disco? Disco is a disco? Yes, it's a disco in Japan. It's a big disco. I brought a big disco with a total of 52 seats. Disco was built. The people who were aiming for the Olympic Games were also doing disco. The wrestling was held in Japan 3 or 4 years ago. It was held in Japan when I was young. Disco was held in a restaurant.  At that time, I met Mr. Tetsuzo Ota. Mr. Ota? He is a lawyer. I met him and asked him if he was teaching me wrestling seriously. Mr. Ota was also living in Colombia. Did you meet him at a disco? Yes, I met Mr. Ota at a disco. He came to my disco. I think he came to my disco after I checked everything. I asked him if he was teaching me wrestling seriously. I also drank alcohol and talked about various things. I see. You did it when you were young. Yes. Mr. Ota was also a wrestler? No, not at all. He was a teacher at the temple. He was a teacher at the temple. Mr. Ota was asked seriously. Did you drink alcohol and talk about various things? Yes. I thought I would do it. I left the restaurant. At that time, it was about 45,000 yen for a restaurant. At that time, it was about 280 yen. It was about 180,000 yen. I went through the bank of Chase Manhattan. I spent about a month and a half to get money from Panama and Colombia. You spent about half a month and a half to get money from the boat. I see. I was told that I was going to teach wrestling seriously at the disco. I decided to teach wrestling seriously at the disco. I see. But I didn't meet the teacher at the disco. I see. You were focused on wrestling and wrestling. You were focused on the director. Yes, I was focused on the director. I was going to teach wrestling from a young age. How old were you when you were young? I was about 8 to 10 years old. You started wrestling when you were 8 years old? You were only a boy? Yes. You were a girl at that time. I was only a boy at that time. How did you get those girls? I had a homecoming. You had a homecoming?  I brought them home and took them to school.  I see. You were running barefoot. I see. We are going to take a short break here. And we'll be right back. Stay tuned. Hello, everyone, and welcome to the Think Tech Hawaii Studio. My name is Andrew Lanning. I'm the host of The Pretty Matters Hawaii. We air here every Tuesday at 10 a.m. Hawaii time. Trying to bring you issues about security that you may not know, issues that can protect your family, protect yourself, protect our community, protect our companies, the folks we work with. Please join us. And I hope you can maybe get a little different perspective on how to live a little safer. Aloha. Aloha. I'm Mellie James, host of Let's Mana Up. Tuesdays every other Tuesday from 11 to 1130. This show is meant to dive into stories of local product entrepreneurs and how they're growing their companies from right here in Hawaii. I'm so thrilled to have our show kicked off. And so please join us on Tuesdays at 11 o'clock as we talk to local entrepreneurs and hear their stories. We're back from break. I'm Yukari Kunisue, your host. This is Konnichiwa, Hawaii. Talking with Norio Okada, a wrestling coach in the studio today. Live, Oto dokesite orimasu. Think Tech Hawaii no Nihongo Bangumi. Konnichiwa, Hawaii. I'm Norio Okada, a wrestling coach in the studio today. So please continue to join us. Please do. We are going to show the picture here. So please show me a little bit. This is very wimmy-ish. This is the first time I went to the international tournament when I was in Japan. This is a Japanese tournament? No, I went to Japan. My back is in Japan. Japan and Japan are the national teams in Japan. I see. Are you about 18 years old? No, I'm 21 years old. 21 years old. I'm a university student. Let's show the second one. What is this? This is a local housewife. This is a small housewife. I'm a junior in Ooyama, and I'm a junior in wrestling. I see. After graduation, I ended up in Obikai. I've always been in Kanshi-cho. That's how I got to know each other. So you like wrestling, too? Yes, I like wrestling. I see, that's why I'm young. Let's show the picture here. I've seen this before. This is Inoki-san. I'm a junior in Ooyama, and I'm a junior in Ooyama. I'm the head of Japanese women's wrestling. I see. I'm currently the president of the Japanese wrestling association. He's a pro-wrestler. Inoki-san is a good guy. That's right. Let's go back to the previous story. When I was 8 years old, I raised food for kids. I collected them. I told them I wanted to do it. I told them I wanted to do it. I had a good feeling about it. I told them that. How many people did you collect? There were about 20 people. Do you know of any wrestlers? No, no. I signed a contract with Colombia. You were able to cut your own belly fat. Colombia is very cheap. I see. You were the first in Japan. Yes, I was. I grew up with them. I see. How old were you in the Olympics? I was one of them. Albeiro Garcia won the world championship at the World Championship in Cádiz. In the Swedish Stockholm tournament. From Colombia to Sweden? Yes. At that time, there was a boxer in Colombia. He was the world champion in the hit pampere. He lost the title and became the world champion in the sports tournament. He disappeared. At that time, my child became the world champion. Mr. Odessi was on the stage without flowers. It was a child's tournament, but it was a world championship. It would be great if he became a baseball champion in Hawaii. He would come to Colombia. At that time, I was in England. I was in the country without a visa to go to the airport. I couldn't go there. The foreign minister came to Colombia to visit me at the airport. I see. At that time, you became a national hero. A firefighter. When a firefighter came to Colombia at an event, a firefighter came to the airport. Yes. That's how I was happy. How many years did you train until you went to Seoul? I trained for 12 or 13 years. 12 or 13 years. I trained for 10 years. I trained in Jibara. When the world championship came out, the country in Colombia was all over the country. I see. From the ticket, money, to the soccer field. Mr. Odessi, you couldn't speak Spanish when you first went there. No. How did you communicate with him? He was a wrestler and a friend. He was a girl friend. He was a girl friend. He was a good friend. He taught me. I see. He taught me how to communicate. When I went to Seoul, I was so excited to go there. Do you still remember how you felt at that time? To go to the Seoul Olympics, I went to the Pan-American zone. I went from Hanada to Argentina. I had to go to San Diego. You had a plan, didn't you? Yes. I couldn't go to San Diego. I had to go to America and Cuba. Cuba was strong. Yes, it was strong. Canada was strong, too. Mexico was strong, too. But since I was little, I went to the World Championship. They were... They were calm. They were calm. They were calm. That's amazing. Even if you meet Japanese kids, they are not calm. That's the spirit of Okada-san, who came to Japan. He was able to train and train himself. Is that the reason? Yes, it is. Did you remember how you felt when you went to Seoul? Yes. I was able to join the Olympic Games. Of course, you went to the Olympics with the coach. Did you go to Colombia? No, I went to Uzbekistan. There are other competitions, so I went there. It's been a long time. But you were very excited. There were many famous athletes. For example, there was a big girl in the Sabachini, about 180cm tall. There were many athletes. I thought, there was a lot of money. You went to the stage of the spring, and what was the result? You were able to participate. I won three times. But the Olympics was the most important thing. How many children did you have? Four. One of them passed away. He passed away? Yes. Were there other athletes? Not the Olympics, but the world champion, Albert Garcia, passed away. The two of them became champions. Are there other athletes? They are still coaching. I see. They are coaching after me. They are coaching after you. They are coaching Victor, and they are raising women. They are training twice, and they are doing the Olympic Games. The Olympics are going on. They are coaching after you. They are coaching after you. I see. Okada was the first coach. Yes. He was the coach. How long have you been there? 15 years. 15 years. I am very happy to see that you have been raising women. I am very happy. After that, you came back to Japan. How is it that you are in Hawaii now? In Hawaii, I am with Renna. She is my wife. She is in the studio now. She is married to Renna. She is married to Renna. She is in the train station in Hawaii. She is married to Renna. She has been in Colombia for 6 years. Renna has been in Colombia for 6 years. How long have you been in Hawaii? I was born in Tokyo. You were born in Tokyo? Yes. Why did you come to Hawaii? I came with my father and mother when I was little. I came to Hawaii with my father and mother. How about you, Renna? My wife came to Hawaii when I was little. She came to Hawaii with her father and mother. I was 68 years old. You are making fun of me. I am your wife. How many years have you been in Hawaii? I have been here for a few years. After the solar olympics, I had a new high school in Tenri. I was told that I should become a coach. I was told that I should become a coach. In Tenri, I was taught that I should be a coach. I was taught that I should become a coach. I've been in Japan for 21 years. So you've been in Japan for 21 years? Yes. How did you come to Hawaii? I've always wanted to live in Hawaii. Really? Since you were in Hawaii? Since I was in college. Since you were in college? So you had a dream of becoming an Olympic champion. You had a dream of living in Hawaii since you were in college. That's what I thought. So you had a dream of becoming an Olympic champion? That's what I thought. You had a dream of living in Hawaii since you were in college. I went to Hawaii when I was in San Diego. In 1971. At that time, the students of Keio High School came to Hawaii during their junior high school trip. I thought that the high school students would come to Hawaii. That was at that time. If you don't live here in the future, the Japanese language will continue. I see. So you're working at Tenri now? Yes. What you're doing in Honolulu is I think many of you have heard about Tenri. Could you tell us a little bit about Tenri? Yes. It's Nuanua Avenue. It's 2236. It's a residential area. There's a library and a judo club. There's a judo club. I've never seen a judo club before. I'm a student at the library. I'm a teacher at the library. I'm a student at the library. I'm a big fan of Tenri. I've been using it for about $20 a year. It's about $20 a year. There's a large number of books in Japan. I'll be using it. If you don't know about it, I'm going to introduce more books in Japanese. Thank you for watching. I'm Yukari Kunise. See you next time.