Welcome back to another human-humane architecture show here today in our groovy boomtown of Honolulu, Hawaii in 1976 Which now you know who my co-host is today. There's no mistaking. He still has the same hair the same smile Amazing so welcome to show that he doesn't look like that That that was me Many years ago, but that's appropriate because we're gonna be talking about a house That was built and at the time that that photograph was taken mid 70s Let's just say 76 although the photo might be 75 but doesn't matter That's what I look like when this house exactly because number two is what we talked about in the last show This is 1975 what warehouse that's right by Steve owl And but before we and this project is very very directly related to this project here And before we dive into that with the next picture We're going to talk about the zeitgeist, right? Absolutely, and there we go now 1970 the early 1970s was a very tumultuous time in the United States Because for the first time as you pointed out the USA went through a big withdrawal of the energy crisis 73 and that was a big trauma I lived through that as a 20 year old and I can tell you it was a big trauma to go from Using a lot of energy very heedlessly just suddenly having to convert to conserve and a lot of people were stuck with cars that were Way too big and it got terrible gas mileage. So there was this quick try to in this particular case Create a small car and AMC American Motors Corporation didn't have a lot of money They had to take a regular sedan cut the back of it off and turn it into this sort of bubble-like car The AMC Pacer which was Cookie look at that. I think they even widened it a little bit made it even more goofy So we want to maximize the width of the yeah in a state. Yeah, yeah And it was I can remember going to a car show and actually sitting in one of those Looking at it thinking I should purchase this and keep it for the future because it's so unusual Which I did not do you should have you should I have enough of other stuff I guess I deal with okay bringing a car as well Okay, and I would say not that we want to make the pace a literal and an analogy to that to that project here Steve might probably not like that, but no, maybe he would but I mean it as a compliment because the cases are iconic They're really typical for their zeitgeist and the zeitgeist is the first time after getting bigger and bigger and bigger in America Everything it was like tight in the belt. It was talking about Jimmy Carter We don't want to go there, but these were all the circumstances of America being kind of sensitive about issues of Ecology and economy right absolutely, and that's the time that this house that you're going to show people Exactly, so the story is that Steve basically This was the first time his biggest project As a young architect and he had been renting ever since before that And so this was a time when he thought I could maybe own But not really because he was still on a small budget, you know the fee was moderate So he only had the money that he had for renting basically for buying something so I limited him To finding a very very cheap lot and build very very cheaply and the next picture number four shows us And we know kind of reveal yet where it is, but This is it. This is pretty much like a jungle and this is a steep hill So that was the only thing that he could afford and so what do you do? If you would start like they do it today if you have a lot of money you bulldoze that you level it You got to do a lot of land moving and landfill and that's going to eat a chunk of money, right? So that was not able what's not possible to do that So as we always tell I always tell myself my students and my colleagues is like restraints and constraints They're actually not a problem there and a tremendous opportunity to be get the creative chooses going absolutely for architecture That's really true. Mm-hmm and constraints in lots of projects do the same thing. Yeah, absolutely So the next picture demonstrates actually the project the project is a staircase a glorified stair a large staircase and it's one that is I love that too that's in the cold violation I'm a big fan of that is the ones who know me very well that You know, there's no guard rail and Steve and Irene told me that Basically generations of children and grandchildren were basically tumbling down Rolling down the stairs never breaking the neck and that gets us to they call this project a treehouse And if you think about trees the animals like the monkeys in a jungle, right? They don't have guard rails either, right? They just know how to go up and down the tree. That's right So they did in that building right pretty awesome. So you might think well, where do they live? Where do they actually do all do they sleep on the stairs? Do they like stare on the stairs, right? So the next picture here shows that and here Steve and Where whenever there's a landing there is actually a dwelling space, right? And so here you can actually see how close he then naturally is to that hill, right? You could just pick the leaves is that close right? He's literally living in the jungle correct, which is very very cool. It is it is and the next picture is that all these pictures basically We took at our doko momo event when Steve and Irene had us over Kindly and showed us the house and and told us the story. So everything. I'm telling is sort of repeating Recalling first what I heard from Steve and all right, so so that's that so you can see here There's a lot of people right so even though it's a small house You can you can have in these sort of landings in these sort of dwelling nooks you can have Significantly enough large spaces that you can that you can do with things very well Let me point out too that at the top of the picture on the upper left Those wooden trusses that wooden structure is something that is present in Ward Warehouse Yes, and it's also present in what we'll be talking about next week Which is another one of Steve ours buildings, which is the buzzest steakhouse in Pearl Ridge And it is very typical not only of his work that we have seen that I've become familiar with But also from the time period talking about the 1970s. So this if I'm not mistaken is Probably raw unfinished wood just stained. Yes, it's not painted because you've got the contrast of the white walls Yeah, the dark and that crisscross structure. Yeah, and the exposed structure is part of his work Excellent point and you know, we don't know the budget of the Ward Warehouse Exactly, but we know the budget of his own house this house here, which close which was close to nothing Yeah, so not only did the lot had to be very cheap But also the construction cost has to be really cheap and ever if I recall correctly, you know It was in the $60,000 range and 70,000 so the lot and the house basically the same but right something You don't even get a tiny house for what they call tiny houses.  How many how many children do they have? You put me on the spot. Okay. No, I'm just wondering how many people live there How many people he designed the house to hold? Yeah, yeah If you say children that means there were at least four people Yeah, yeah, yeah, yeah, these two kids and new adults. Yeah, yeah, no There were more and grandchildren, you know, so it was like a beehive at times I know which the house was able to accommodate because like in a tree You have birds on this level of branches and on this level one so you can pack them, right? Because you find your privacy when you go one level down or half level down that reminds me too and this is maybe a little far afield, but the the diagrams I've seen of Rainforests in which there are huge trees immense trees and there are different ecological levels within this whole structure This vertical structure of the amount of light the amount of rain What there is to eat and who lives where in that natural ecosystem of immense trees That's exactly what lives at certain areas certain plants will only grow up here certain plants will only grow down here Certain animals will only eat those plants. Thank you to Soda I will make this a required lecture from our current studio. We're dealing with that. So thank you for that lecture here I'm sorry. I appreciate it So that picture number 12 shows sort of the creativity and how ingenious the house is that a bathtub Basically is sunken into this if you can get back a number 10 for a second You know the the bathtub is basically sunken in into the into the ground and So you have to step down to get into this sort of trough And that function as a shower and a bathtub. It is yeah It is and there is other ones like that. So there's a couple of other ones So it's really amazing and obviously what we tell every client what we tell ourselves would tell our the emerging art Generation is you want to have natural ventilation in the bathroom? Everyone knows that whoever has an enclosed trap bathroom you get mold like crazy here in the tropics So as we saw here, you really want to want to have that But on top of that you have a view and we already Disclose the view because the view is behind us behind us right this minute That's so now basically most people who are familiar with Wahoo know this and you will explain as a little further where yeah So this is that this is a hill behind Lonnie Kai Lonnie Kai is a development a subdivision of the 1920s and when it was originally laid out when it was originally put up for sale The idea that the buyers the idea was that the buyers would be well to do people who would build second homes for Weekend retreats were going on vacation So a lot of the houses originally in Lonnie Kai which now is a very very upscale neighborhood Were very low-key small houses Yeah, and of course as you just pointed out all of the flat land would have been built upon and developed many many years Before Steve was able to purchase there because that vertical property was something that people didn't want to purchase and Honestly, if you weren't an architect to begin with it's probable that you wouldn't consider buying something like that because of the logistics Yeah of trying to build there and everybody as you said their first thought would be bulldoze it So we have a nice flat plane to build on and exactly and Steve did this instead Which you can see there are all these sort of landings. They're all these hovering balconies and lanays that Allow you to really enjoy the view you're literally like in the trees and You're out there in the elements and the next couple of pictures. So number number 13 is one where Our background picture again. There are some areas because it gets windy. This is the this is the the wind port side, right? So it gets very windy. So you have to have glass at certain parts To keep the breeze off But then in other parts like this one here, you got to slice view and sliced air this this house is entirely Basically naturally ventilated and it's brilliant because it's such a small footprint So you just have one jealousy on this side another jealousy on that side and you basically get get the get the breeze through What we saw a number of 15 is a is a very spectacular spectacular a special part of the house if we can get 15 back That you see here the jealousy obviously and there's another one just like that on the other side to the right And there's something very characteristic for for modernism. That's the glass corner that's when architects really want to show off sort of immateriality and and and being being and if you're afraid of heights you shouldn't get close to that to that window because it drops like crazy Well, you know when you say that it reminds me that I have read that starting in the 1930s as you It was kind of a cliche of modernism to have a corner window Mm-hmm, and that was a big deal because up until then every building had to be supported on all four corners So you always had a post or a pillar at each corner And once you started building buildings that could stand up without that corner post you took advantage of it and Put some glass right on the corner there So this had been something that got started as I said in the 30s and in the 70s You could make it absolutely clean and clear with just a seam of some kind of sealant To put those two big pieces of plate glass together and I have not been to this house But it looked like that was actually an entire sort of rectangle that protrudes out exactly And so with glass and then the louvers here and here and we will see them later How that sort of iconically looks from from the outside. Oh, yeah, okay. All right. And yeah So why don't we take a little technical Promotional break here and then we're going to be back with the soda and Martin and talking and showing Irene and Steve's treehouse. See you in a minute. My name is Calvin Griffin host of military in Hawaii We tears here on think tech Hawaii every Friday at 11 a.m Please join us. We'll be talking about issues concerning our military veterans community and other related issues that concern all of us Hi, this is Jane Sugimura and I'm the co-host for condo insider and We're on think tech Hawaii every Thursday at three o'clock and we talk about condominium living and issues that affect condominium residents and owners and So I hope you will join us every week at on Thursday and We appreciate you viewing our show aloha He stand the energy man here Thanks for joining us on think tech Hawaii and I invite you to join me every Friday on think tech Hawaii at 12 o'clock Where I give you all the energy news. That's worth talking about here in Honolulu and I love to talk about hydrogen So join us on Friday on my lunch hour here at think tech Hawaii be there aloha We'll come back to the Soto and Martin talking about Irene and Steve ours tree house in Lonnie Kai That's a very exciting story of young architect You know with their first big project ward warehouse, which was really zeitgeist II Then having this unique chance to build a house for themselves, but being constrained with close to no budget both for buying property and land and I should add that That actually even The because the land was cheap. It wasn't enough. He needed to talk his business partner into Basically teaming up with him and there's another house right next to it and that's his business partners house So they even need to be creative on that part now You know the thing that just came to mind as we were discussing this and looking at pictures of the site in the house There was something here in the 1970s called a pole house Which you may be familiar with in which it was a Structure not unlike this in that it was wood and it was natural which is what we liked in the 70s And it contained it was sort of built on Telephone poles so telephone poles or utility poles wooden ones were used as the basic framework for this and then you Created it around that and the the main one that was built was I say I remember a University of Hawaii project in Manoa Valley And it reminds me of this because it like the treehouse was associated very much with a lot of surrounding vegetation So you went into this natural wood house and looked out at and were among a lot of trees A lot of vegetation a lot of plants in a wet moist environment So again, this reminds me again very much of the 1970s, which is the time we're talking about And if you can bring back number eight for a second here I forgot to comment on something that you correctly said which is the sort of expressionism of structure The beams the wrong kind of that's right. That's right. Correct. Correct. Yeah, so here it is so We said, you know at word warehouse It was sort of celebrated in almost exhibitionist, you know way right whereas again here It was the pure necessity because once again budget did not allow I mean nor did one want to because of the That's the thinking of the times, right? So one wanted to express but also one needed to express I mean this house is, you know down to the small dollar Making something out of nothing, right? Right. So you had you had really little choice as to leave it raw and rugged and And and so it's it's you know, what warehouse might be a little bit more fetishized as you you know perfectly pointed out in the last show We talked about it was all about selling it It was as much about selling it as as much as what it actually was correct correct the image was really part of that Yeah, yeah, the image that was stated I was also going to say in the photograph that we just were looking at of the of the kitchen look at the bench and Look at the countertop and look at the structure. That's above that That is raw wood as well. I mean, it's got a it's got a finish on it. Yeah, but it is a thick Heavy substantial pieces of wood which are displayed openly and honestly as pieces of wood and they're not pretty Dup, there's not a formica. There's no granite top. I mean that wasn't really very very prominent at that point anyway But he's again saying look this is the raw wood that we are using as its natural self. Yeah Which is very appropriate if you think about the context again and setting that's right You're in nature. So you don't want to oppose nature You don't want to come in and bring the tilts with other carbon footprints with other BTU's, you know And also you want to build I mean the big thing today is like healthy homes, right? I mean, it's about we all breathe Their families exactly fewest adhesives fewest outgassing chemical materials That was not much of a that wasn't as much of a concern in the 1970s We didn't know about it as much, but certainly that was we were more into naturalness, you know being real Absolutely, so the picture of 16 is Again, there is this multitude of places where you can get exposed to the outdoors and And you can also get up on the roof and the roof isn't to be permanently occupied But when there's a beautiful sunset They went up there You know the stairs goes all the way up to there and you got to watch you don't hit your head I remember and then you basically lift up this little Sort of the term sort of self-made comes to my mind in a very appreciative way that You know, this wasn't off the shelf these days architects sit in their office And they have all these binders in the back and then they pull and say oh this product There's this product So this is basically all from scratch and this makes the house so special, right? And I don't think even say when you say custom home, that's a term of these days I don't think this does the house credit. I would say it's self-made in a very sort of passionate way So this this lid is basically, uh, you know coated or covered with if we go back to 16 with this acrylic So you see like, you know, it's it's sort of the smoked So it it it reflects the heat and doesn't get too much heat gain through there But it's translucent so you can you can look you can look through And and so it's it's all and you just like, you know, go up there and lift it away And you can get out there and have have a most spectacular view of the suns that I can figure and even, you know When the sun is still there. It's just absolutely fantastic. So, you know, you were saying it's among the trees I would point out. It's actually above the tree. Oh, that's good point And in the view that we're looking at with us be that we were looking at it is higher than the palm trees So you have an unobstructed view the trees are around you and behind you But in front of you. Yeah. Yeah is the open view and this is a picture I'm very critical of because that's how most People would start to Describe the house and I think it does the house the least justice because This is what we traditionally call bird's-eye view or this is you know, and and but um Yeah, we're not birds and I would say this is when we say bird's-eye. Well, this is the vulture view And I mean this is the view the profession of Realtors no offense took and that's actually was how the house was was marketed because Steve and Irene Got to the point where they say they want to retire more and they want a more Accessible home for their needs in their part of this part of their life So they were looking for Someone who would sort of take over the house and We visited as doko momo and we were very worried because it's a very special house, right? It's in a house that doesn't really have traditional bedrooms all this terminology that doesn't have a stair with a guard rail That doesn't have marble countertops all these things that people Think they would need now which we highly question here in the show because as one sees you don't need them You're actually better off if you don't have all this stuff But this is really sort of avant-garde It has always been avant-garde, but it had stayed avant-garde, which is like, you know great a great quality So the next picture is the uh 18 which uh picture we took which is small But uh actually is exactly the illustration for what you just said before This is the house above the trees, right? Is the big tree above the lower trees You have that in nature too, right? It is. Yes, you do. That's right. And also too That you pointed out when we were talking beforehand. It is a weathered wood structure So there's no paint on that. There's no artificial surface that you see absolutely You see natural wood that has weathered to that grayish appearance Obviously when it got when it was first built it would have looked more raw But now it is Much more part of that environment and I think that's really nice considering that it is surrounded by nature It's on a steep cliff. It's on a steep hill. It doesn't protrude out a lot. It's not sort of invasive in the environment It's kind of at one with the environment in a nice way Perfect picture for that is the next one is number 19 Oh, yeah, there they are Shows how it works and as you perfectly said this is actually vertical or raw cut siding so the water always drains off And um, yeah, it's all natural. I always tell my clients, you know If they say, oh, why don't we paint the wood? I said once painted always painted You always got to go back to your maintenance intervals if you don't that you're in trouble So the best is actually to leave the wood untreated and and wood can last a long time and um, it's you know, um Again the nature of what warehouse is different than this one here as a typology So also by nature this has weathered much better And also the climate and the environment is much better. It's very way more windy here So when you got rain, you have the breeze basically dried out Pretty soon after that helping to evaporate as long as you Dry the rain the water the humidity off immediately. It's not a threat to to wood at all So that's um, that's obviously a great um, a great quality the house has and if we go back to, uh, number 19 one more time here is that um The the sort of um Strategy of the house reminds me a lot of master lukan for example amongst others where The house when you look at it, it looks strange because it doesn't follow any conventions, right? Of openings or proportions Correct, and I will never forget ashore cows blew me away, which you can't figure out what proportion what scale What these openings are Once just like this house here once you are and have the chance to be in it once you Understand the logic from the inside You will understand it from the outside and you will appreciate it. So if we go back to, uh, 19 one more time again is like that And we took this when we were we were so, you know It was about the house So we spent a lot of time and they hosted it graciously and then we were going down it was starting to get dark So that's when you see how the light, uh, you know goes on in the building So that top big thing there that opening is exactly that spectacular, right sort of hovering, uh, you know in the clouds Right space with a corner with a corner window, right and you see the you know, your iconic, uh, trust Wood trust looking right through the window. There it is And and uh equality. So it's it's also taking a very different approach to the views right as well That we have in architecture so much. We got a Phase out a number 20 is, uh, thanking, uh, Steve and Irene who had us over But also for being such a great inspiration and we started with you in the 70s So we're gonna close with a little laugh about me in the 70s now It's time to look at you looked at de soto in the 70s now. Let's see martin in the 1970s 21 And I was I was building a tree house with my buddy here and this would be Unimpossible these days with a paranoia of liability We were given a bunch of boards and nails and hammers and went to a public city construction site Later later on I was in my I was like in my tens like I don't know 12 or 10 12 in that range And later on 22 together with my family business my father and my sister We were building we called this tree top apartment so you can certainly see some inspiration there But most importantly is the last picture is number 23 where we're currently with an emerging generation 13 students and myself having proposed this here, which is called stratosphere Which tries to provide dwelling and dignity For the most underserved who who don't have a home who don't have a roof of their heads So we want to thanks Steve for being a lasting inspiration and the very best news is that actually they have found Buyers for potential buyers for the house who will keep the house and Appreciate the house With so a new family will end so the legacy will live on and continue And that is that is something to consider when you build a real unique property Absolutely. So with that all good things are three We're going to have one last of steve's sort of late hippie era of the 70s And you already released what it will be it will be juicy and meaty It will be that's right who likes steaks. It will be buzzer steakhouse So see you for that next week. Thanks for tuning in


What's up everybody, Jason here for jasperyscasebrakes.com. Last four boxes here, guys. This is 2022 Peany Knee Score Football. Four box hobby break, random divisions number six. Again, eight total spots. Everybody goes around a division at NFL All-Cards Ship. Look for four autographs, 90 rookies, 10 parallels, 36 inserts per box on average. Here we go, guys. Here's the dice, really. Here's the customer names and the divisions. Let's roll. Four to one, five times. Good luck. One, two, three, four, five. Five times. Gregory at the top, Donna Kev at the bottom. And five times. One, two, three, four, five. NFC West, down to the NFC North. And then Gregory, you have the NFC West, Carlos with the AFC East, Chris with the NFC South, AFC North and AFC South. Angel with the AFC West, Travis with the NFC East and then Kevin with the NFC North. Now, I don't think there'll be any trades, but I'll leave it open for about like 30 seconds. If you want to propose one, do it, if not. Let's just close the thing, guys. All right, so we'll go one box at a time. Probably just gonna skim through the base cards. Obviously, there's like a pattern in every box, so. Just stop for like the rookies, inserts, autos and then we'll continue to skim through the base cards since I'm gonna do special fancy about those. But again, guys, we have a very busy schedule today. Started off the day with two certified breaks. Now we're on to score. So in about like 25 minutes or so, I should be done with this. We'll go to a quick impeccable one box R&B and we'll go to some quick autographed Facebooks or Fanatics. And then Sterling filler with Bowman Sterling. And then after that, we'll be open to potentially doing something. Okay, so again, I'm gonna skim through the base cards here. Again, we start right here with the rookies. No autographs there. Oh, Dante Cole Pepper. Nice Trayvon Walker, that's the number one overall pick. Very nice. Nice, Steve, NT Baseball? Cool. There is a filler though right next to it, so we would have to sell out the filler and then the two spots that are remaining. Just let out five. Yeah, we can definitely do that today. Nice Gary Wilson to 50. So that Dante Cole Pepper is gonna go to the NFC North. Let's go into the AFC East. Wow, Bailey Zappi, how about that? Wow, three out of 10. His stuff has been going for some good money. That is a nice hit right there for the Patriots. Who has the AFC East? Carlos, how about that, buddy? I mean, obviously if Mac Jones is gonna take over, his stuff should probably drop, but not a bad time to get rid of it though. Very nice Zappi, three out of 10. Solid hit. Awesome man, congrats. Always good when you win a giveaway with us, right? Whether it's some break credits and boxes. Luke Eakley to 199. Three out of six, can he pick it? Draft rookie. End zone and AFC North. That's Chris Maxwell, how about that? I had a couple of great hits here so far. Steve, I don't know if you heard me a few minutes ago. Thank you, I appreciate that. We also have a filler for that NT baseball, so if you are the one taking those spots and don't mind helping out more in the filler, have at it, buddy. That'll sell out NT baseball. So we only sold four R&B spots straight up, six of them are hiding in a filler. J. Kwan Briskar, points is coming up instead. 600 points. So everybody will get a shot at this at the end. All right, solid box, guys. Really, really solid box. This is a personal, should have been an awesome box. All right, let's continue on. So again, we'll skimp through all this. We got a Hot Rookies Kenneth Walker to 100. Kobe Bryant to 50, not the Black Mamba. Sam Halbrough, little gray border. Tyler Heinecke, Michael Thomas to 50. TJ Hawkinson for the Detroit Lions. Then we got Trayvon Diggs to 100. And Desmond Ritter, nice for the Falcons. That's gonna go to the NFC South. Aiden Hutchinson was, or sorry, TJ Hawkinson was NFC North. There you go, all right. Halfway through, guys. Next box, some points. Don't wanna show that. Drake Jackson to 100. So we'll give out these points at the end. So far we have two points, I think, two redemption points, 600 and 400. So number one gets 600, number two gets 400. TJ Watt, that's number to 10, nice low number. And first auto is Terris Marshall Jr. And Romeo Dobbs, Kobe Bryant died cut to 10. Tonight's winner for the Seahawks, AFC West, or NFC West, I should say. Ronnie Rivers, nice Drake London little gray border. Our last two stacks, potentially, here. Kyron Williams to 35. Whoa, that is not good. Just saved it, Jesus. Last box. Man down, man down. Good to go. Our last box here is four, and I don't think we have any more after this, guys. I don't know if Nick has taken it off the website already, but I believe this was the last four boxes. Because we were looking for some for personals yesterday. We didn't have any. So I appreciate you guys buying out this score. Guys, last box. TJ Watt, eyes gold, 46 out of 50, little color match there. AFC North with that one. And that is Chris Maxwell. Another one.  Kenny Pickett and Zap, you're always together. Jameson Williams, he should be back very soon as well, to 100 for the Lions. That's NFC North. Fletcher Cox to 20.  Dontario Drummond, just to 50. To 50, Derek Stingley Jr., nice little color match there, too. That's for Houston. And Mark Gassano, that's the last auto there for the Jets, AFC East. All right, there you go, folks. That was the break, so I'll top a little of these autographs here. We've got another nice auto here. There's 400 points, Ritter, sorry, 600 points. And the first box was actually pretty nice. That's Zappy to 10. Got the sixth Kenny Pickett there, very, very nice hit. So again, we're randomized to names, number one gets 600 points, number two gets 400. Those would have been extra autographs there. So let's get a little dice roll going again on new lists. All eight names, roll one and a five, six times. Good luck, one, two, three, four, five, six. And six times, one and a five, six. Travis, you're gonna get 600 points and Carlos, 600 points. So I appreciate it, guys. JaspysCaseBrace.com.


Today is my day. My name is Arthur and I live in Pasco, Washington. Before I gave my life to Christ, I believe after my father's passing, it was a real hard struggle for me. I started going heavy into drinking and severe depression. I used drinking as a coping mechanism and it didn't really, it felt good for a couple hours but it really never really helped in the long run. One night when I was drinking a beer, it didn't feel right so I went into my mom's room. I told her I wasn't feeling right and she prayed for me and rebuked all the demons that were inside me. Since I've rededicated my life, my life has changed a lot. I started reading the Bible more, started going back to church, started going back to home group, going to morning prayer more often and now that I've been delivered and rededicated my life to Christ, I want to show today through baptism the growing of my relationship with Jesus Christ. So Arthur, do you believe in Jesus Christ as God's Son and your personal Lord and Savior? Yes. And do you promise to follow Him with good and clear conscience for the rest of your life? Yes.


Hey traders, this is Tosh I go by T Bradley 90 in the my investing club chat a general reminder for those who do not know MIC is having a one-year anniversary event where bow is going to be trading live in front of our members It's coming up August 17th mark your calendars as an added benefit for our members The event is 100% and exclusively free for annual and lifetime members While lifetime on top of that get extra coaching before the event and guaranteed front-row seating While most charged for these events we show our support by making it again free for annual and lifetime members If you are interested in signing up for this event DM T Bradley 90 in MIC slack chat and or email myself at Tosh at my invest in club calm Now we have a very special video for you guys this week as Matt who goes by Chicago trader and one of our head Moderators in MIC chat brings back his weekly Sunday video series and today He's going to do a review on the fundamental side of a couple tickers and one in particular is nerve NERV and While this is just a preview of the full-length video if you want to watch the full-length or any of our exclusive content Then become an MIC member What's going on everyone? It's Chicago trader checking in for the weekly fundamental video Doing this one here in the middle of a week as we've had a few names Kind of move and I've had quite a few questions on a certain ticker And I'm gonna be out the rest of the week, but regardless just a few names I wanted to go over and a couple questions that I figured what I had Just addressed to everyone I'll do the quick one first. So Monday nav B moved So in the past if you guys recall like a lot of these companies Have had offerings and then you see an insider buy. I'm near a 52 week low I've definitely given us fits if you are a short seller on day one This one, you know moved up a little bit on pre-market on some news right after the PR But When you come look at the most recent offering it was eight million shares at 75 cents raised six million dollars for The company the things are 52 week low someone just bought, you know over two million dollars similar situations that are OTLK Where the guy bought, you know a bunch right here near gave three or four days RWLK was a very similar one to where like 25 cents or Maybe two dollars. I can't recall I got it one of the largest shareholders bought a bunch of it in the offering, you know near a 52 week low You know again gave fits, but that'd be not so much Another one with a Bitcoin running riot. It's been moving Head of conversation with another member You know Around the baby shelf. So there's obviously a video of it in the video library guys. So check that out Always review, you know a couple of times You know throughout the year or whenever so you know keep up with it So this one I thought was interesting too because you can see the market cap Is under the 75 million for the baby shelf But I mean obviously you got to look at what the float is right and this one happens to be the float and outstanding shares are pretty much the same There's no insider ownership in it But regardless of that The point I want to make with this is you can't just kind of look You know and say hey turns out 75 million the restrictor to the baby shelf Hey traders, this is Tosh I go by T Bradley 90 in the my investing club chat Just wanted to reach out and say if you have any questions about M. I see joining M. I see maybe you're a member already You have three ways to contact myself personally and through M. I see you can hit our social media You can hit me through pms and chat or you can contact us through my email at Tosh at my investing club calm That's TOS H at my investing club calm I will get back to you in a timely manner And I'm saying this because I'm here to help and I don't want anybody to be afraid to reach out and ask any Question that they have we are here for you guys. All right. See you guys


What genetic legacy did the Indo-European migrations leave? Well, two genetic markers that these ancient ancestors left were haplogroups R1A and R1B. These are common genetic markers found across Eurasia today, with R1B particularly common in Western Europe and highest in Britain and Ireland. Subscribe for more.


The drama in Plateau Assembly took a frightening dimension on Monday. The impeached speaker Abok Ayuba and 10 lawmakers loyal to him were whisked away by security agents. Around 3.15pm, Plateau State Commissioner Police Edward Ibuqa led the 11 members to four awaiting Hilux vehicles before they were taken away. The members appeared unlawfuled. Are you under arrest? I don't want to speak now. We want to reach you. Are you under arrest? Now I cannot tell you whether I'm under arrest or not. Where are you going now? We have told them where they will take us. If they refuse to take us there, we will not inform them. Where are you passing to? Down the road. We have people outside already that we are safe. It's okay. It's okay. It's okay. It's okay. Let's go. Let's go. People are going here. You are representing people. People are outside. Most of them want to know what is happening. That's what I'm saying. Are you under arrest? You are not even under arrest. It's okay. It's okay. No, it's okay. Are you under arrest? That's it. Thank you.


Hi everyone, Joe for jazzy's casewrakes.com. Guess what? We did it. Here's the last filler to give away the last seven spots in transcendent WWE Top seven get spots in the break in the transcendent break Everyone else will get a sealed pack of 2021 tops chrome WWE hobby edition So a little consolation prize there. So that's how it shakes out. So we'll just be randomizing Just your names not those spots All right, big. Thanks to this group here for getting in on the action. I appreciate it and let's Let's roll it. Let's randomize that list four and a six ten times One two three Four five Six seven eight nine and 10th and final time after 10 So it's top seven will get those spots. So John all the way down to Ross and everyone in between. Thank you for giving this a shot I appreciate it Thanks for getting in. Thanks for taking the shot. You'll get a pack. Hey, you may end up with something nice out of there, too Let me know if you do but thanks for trying top seven. You're in that transcendent break Joshua Dennis Joshua Dale Kevin Joshua and Stephen Kay There you go. The seven of you are in Thanks, everybody coming up in the next video will be the transcendent break itself I'm Joe. I'll see you for that one next. Bye. Bye


Hi everyone, Shawn with jaspyscasebreaks.com and jaspys.com where we have all of our personal breaks. Doing a personal break for Greg of 2019-20 PD&E Chronicles basketball fat pack, one pack for him. He's already picked it out, we've got it right here. Now it's just time to open it up. Good luck Greg. So first up, Jarrett Culver, RJ Barrett, Cam Johnson, Nikhil Alexander Walker, Brandon Clark, Darius Garland, Kevin Durant, Carson Edwards, Kairi, Romeo Langford, Yannis, Kauai. So this one here, you can see it's like bronze, not much coloring, but bronze down there on the logo. That's exclusive to these cello packs. Kobe White, Luka Donchich, getting a lot of good names in here, not specifically rookies, and James Hardin. That was the most vets I've seen in one of these packs in a long time, but I mean Luka, Yannis, and Kauai Parallel, not bad. That was 2019-20 PD&E Chronicles basketball fat pack, personal for Greg. I'm Sean, jaspys.com for personal breaks, jaspyscasebreaks.com for case breaks and group breaks. We'll see you next time.


Okay, how's everyone going? We're on the home stretch. So, yeah, I'm gonna make a start. We might get a few stragglers coming in, but I do have a reasonable amount to get through. So I'll make a start. So my name's Angus and I work for an agency called Weave. For those of you who don't know me and don't know Weave, we're an agency based in Melbourne and really our specialty is content strategy. So we're content strategy people and we work on a lot of projects with other agencies, especially development firms, but we also do a bit of Drupal work ourselves. So I sort of come, I have a bit of a foot in both camps, but I'm much more of a content strategist than I am a sort of a hardcore Drupalist. So, yeah, talk today is about content modeling. And I really got four main things that I wanna cover. The first is just to talk about what a content model is and why we need one. I'm gonna talk about some basic principles of effective content modeling. I'd originally planned to talk a bit more about actual sort of processes and techniques and that kind of thing, but I realized I was just gonna go way over time if I tried to do that in too much detail. But I actually think with content modeling, the most important thing is to have a sense of what the principles are and what you're trying to achieve. And the actual process isn't that difficult, it pretty much works itself out once you've got the principles in mind. So that'll be the second part of the talk. I'm then gonna be talking about what content modelers need to know about Drupal. So if you're a person who is working on content for a Drupal site and you're not actually familiar with Drupal, what are the really big picture things that you need to know about Drupal as a platform in order to really take advantage of what it can do? And then finally I'm gonna talk about some of the common issues with content modeling in Drupal. So what are some of the sort of tricky little things that come up when you try to actually implement a content model on a Drupal site? Can everyone hear me okay? Is the mic working all right? Yep, cool. Okay, so I wanna start with a question. I deliberately, I listed this talk as a beginner talk and I have tried to make it accessible to people who don't really know anything much about Drupal. So can I just get a bit of a show of hands? Can you put your hand up if at some point you have created a content type in a Drupal site? Okay, so it is the majority.  I will be going through some fairly basic Drupal stuff. So the rest of you will have to bear with me while I might go through a few concepts that you'll already be familiar with. Hopefully you'll get maybe a sense of how to talk about this stuff with people who are less familiar with Drupal. Just one, just a couple of caveats before I start. I'm a relative newbie in the Drupal site building world myself, so I've worked on Drupal sites for several years as a sort of content author and somebody who trains content authors, but it wasn't until relatively recently that I actually built my first Drupal site. So hopefully that's an interesting kind of perspective for you to get. I'm not so over familiar with Drupal that none of its quirks seem quirky to me anymore, but at the same time, I might make some mistakes that some sort of newbie mistakes. So if anybody, if I make any egregious errors about Drupal, feel free to point them out in the Q&A, I won't be offended. And yeah, the other caveat I wanna say is that when I get onto the Drupal specific part of the talk, I'm really mainly talking about Drupal 7. So as people who work with Drupal would know, there's a lot you can do with content in Drupal 7 that you couldn't do with Drupal 6. There'll be even more you can do with content in Drupal 8, but I'm not terribly qualified to talk about Drupal 8 yet. So a lot of the specific stuff is Drupal 7, but in a sense, everything I say will only get better in Drupal 8. But if you're on, if you're still on Drupal 6, you can't do quite as much, sorry. Okay, so let's get started just by talking about what a content model is. So content model is essentially, I like to think of it as just a specification of the structure of content in your CMS. So in Drupal terms, we can think about a content model as essentially documenting the content types that are gonna be available within our Drupal implementation and the fields or chunks that these content types are gonna consist of. And as you know, if you've built a Drupal site, what defines a content type is that it's something that has its own set of fields. So that's what a content model is. It's what are your content types, what are the fields within those content types and also what are the relationships between different content types. But why do we need a content model? And this bit's gonna be very, very familiar to Drupal people and in fact, this might seem really obvious. It's not so obvious to people who might be coming from other platforms. So let's think about an author on a website entering some information about a very common type of content, which is an event. Okay, and let's imagine first of all that we have a completely generic kind of out of the box implementation of our CMS. So our author enters an event by essentially copying and pasting a whole lot of information into one big body field. And this is something that you still see in websites all the time, including Drupal sites, incidentally. So there'll be a big body field. It'll do the job of actually, the content will be published and it will be available, but there's not a lot you can really do with that content. Then compare that approach to a more structured approach where instead of the author saying, I'm just gonna create a page, they actually say, I wanna create an event. And the CMS then presents them with a range of different components for that event, which they sort of fill in individually. So for a typical event that might be something like a title, a teaser, a longer description of the event, a photo, a location, which might be some sort of geographical coordinates, a date and time and some information about how to make a booking for the event. So once we've actually got our information in our CMS in this kind of structured way, the reason why we do that is that it allows us to do a lot more with that content. So as soon as we have events sitting in our system as structured data in this kind of way, we can start doing things like automatically adding our events to a calendar. We can then decide that we don't actually like the calendar and we just wanna replace it with a simple listing of events. This is something that happens all the time in websites where people think a calendar sounds great, but then they only have one event per month. So they decide, now let's just have a list of events. That's no problem if you've got properly structured data because it's just replacing one view of that data with another. We can do things like automatically archive events when they're finished. So all we need to say is that in our display of events, we only wanna show events that have a date of today or in the future. So therefore events just sort of disappear from view when they're in the past. They're still obviously living in the CMS, but they're not visible to end users. If we've got our location in our event as a field and if it's in a machine readable format like a set of coordinates, a latitude and longitude, we can think about doing things like displaying a map of the location of the event or linking to a map of the location. And finally, and this is, sorry, not finally, second to last, we can start thinking about laying out our information differently on a desktop view versus a mobile view. So, and this is really, this move towards responsive websites where we know we are gonna wanna adapt our layout to a range of different devices. This has really been one of the big drivers behind the content strategy community becoming interested in content modeling as a thing. So what this basically means is if you have your events in these kind of granular chunks, you're giving your designers and your front-end developers a lot more individual bits to target so they can make a lot more, there's a lot more variations in the decisions they can make about how those events are gonna be laid out as compared to one big field where we can do is really shrink it. So none of this is news to any of you, but this is what we're really trying to do when we're modeling content. And finally, we can think about offering a feed of our events to another website. So if we're wanting to export our data in that kind of structured form, like a JSON export or something like that, then we need to have our events, we need to have that content properly sort of structured in the first place. Okay, so that's what content modeling is. Again, it's not really gonna be news to any Drupal people because Drupal is a platform that's set up to be good at doing this kind of thing at sort of storing structured content. But that's not to say that every Drupal site does this well. So what I wanna talk about next is really three basic principles of effective content modeling. And these are the three things that I think are really most important to bear in mind when you're developing a content model. So when you're deciding what your content types are gonna be and how you're gonna break them up. And the first one I think is probably the most important and that is to separate your content model from your presentation model. And then you've probably come across the idea of separating content from presentation. That was a big part of the, I guess, the emphasis behind the development of CSS and the idea that we have HTML elements and CSS can, it's the CSS that tells the website how to display those elements. So this is really an extension of the same idea. It's the idea that we really have two different ways of thinking about content when we're developing a website. So the content model is all about how content is stored in the database. So it's about our fundamental kind of content structures. It's about the content types we have and the fields that we have. And so it's sort of about how our content ends up getting stored in the database. The presentation model is about how that content gets presented to users of our website. So it's about what those end users actually see and how they, the different ways in which they can view that content. So the presentation model is about pages. It's about our information architecture. It's about landing pages that collect content from various different places on the website. The content model is about the basic content that gets served up to those pages. So the two things are obviously very closely related because we can't have a presentation model without also having a content model. But they are different things. And there are several, there are lots of reasons why it's good to think about them as different things. By the way, the term presentation model on sort of borrowing from Jeff Eaton, who's a famous Drupal person that a lot of you have probably come across, also really interested in content strategy. So he's the one who has sort of borrowed this distinction from the content model versus the presentation model. So why do we want to separate our content model from our presentation model? The first reason is that a single content model might end up serving several different presentation models. And in fact, in the case of a modern website, that will almost always be the case. So we can really, we can think, for instance, of the desktop view and the mobile view of a website as being different presentation models. You know, the layouts are different. The order of things might be different. So, and the user experience is different, but it's the same content that's being served. So we've got a single content model, multiple presentation models. We can then think about, you know, other kinds of presentation models, such as screen readers, for example. So a screen reader that is an audio way for, or an audible way for a visually impaired person to access content, that's another kind of presentation model. That's one that's radically different from the visual kind of presentation model that we have on a web browser. We can then think about, you know, other ways in which our content gets sort of served to different services. So there's things like Instapaper, there's social media, you know, in the modern web, our content is going to get chopped and changed and sliced and diced by all these different services. And we can think of them all as different presentation models. They all need to be served by a single content model because all our content is going to live in one place. So another reason for keeping these things different is that ideally your content model is something that isn't going to change very often. Your content itself obviously changes, but the content model, the basic way that you structure content, ideally should be something that you're in for the long haul. And if you've ever actually tried to sort of retrofit a content model onto an existing body of content, you'll sort of know why. So it takes a lot of work. So you really want to be building a robust content model that's going to be around for a long time. The presentation model, on the other hand, might change quite frequently. So you might redesign your website depending on how trendy you want it to be every couple of years. Or you might at least add new design elements. You might want to rebuild your website in the latest kind of front-end whiz-bang technology. So if you've got a really robust content model, you can actually change the way that content's presented without having to go in and make a whole lot of changes to the content itself. Potentially, the content model and the presentation model can even be implemented in different systems. So an example of this is the so-called Headless Drupal project, which according to Jam, we're now supposed to call de-coupled Drupal. De-coupled is a much better word. So this is the idea that Drupal is really good at storing and structuring content. A custom JavaScript thingamie... Sorry, I'm not a front-end developer. A custom JavaScript, whatever. It might be better at actually displaying that content, so we should have the ability to store our content in one place and display it in another place. And obviously, to do that, it's really, really important that we're not including presentational logic in our content model, that our content model is kind of purely about the structure of our content. And finally, the content model is what authors interface with. So when an author creates a node, for instance, in Drupal, they are presented with the fields that are part of our content model. And it's really important for authors to understand that that's what's happening. And when we tie our content too closely to one particular form of presentation, so when we act as if what authors are doing when they create a node is creating a web page that is always to be viewed on desktop. When we sort of encourage them to think that way, they tend to forget about all the other potential presentation models. So they're not going to think about how their page is going to be read by a screen reader. They're not going to think about how this blog post might appear on Facebook and so on. Karen McGrane, who's a really well-known content strategy person, has a saying that the internet is not a laser printer. But what we often do with authors is that we use metaphors that come from print, such as telling them that there we see that their CMS is just like Microsoft Word. So that's the kind of thing we're really trying to get away from as much as possible when we create a content model. Okay, so that's our first principle. We've got a content model, a presentation model, or multiple presentation models, they're different things. The second principle for me is to treat your content model as a pragmatic system, not a complete model of the world, unless you happen to be building a site that is meant to represent the whole world, like the idea, for instance. So what I mean by this is that you really need to make pragmatic decisions about how granular you get with your content, whether something needs to be a separate content type or not, whether something needs to be, whether you need to break a certain section into five different fields or two different fields. And the way that you make those decisions is not by thinking, well, what's the maximum possible level of granularity I could possibly have? Or what would be really cool to do? What's the most complex, kind of complete system I could possibly build? It's very easy to get into that way of thinking when you're actually going through the abstract process of building a content model. So what you really need to do in those situations is to go back to your user stories, your scenarios, your fundamental goals for the site. And if you're getting to a level of granularity that's not actually going to help you achieve any of those goals, then you probably don't need it. So if you can't imagine a situation where you might use a thing, it probably doesn't need to be in your content model. Example of that is I was working with a client who publishes a lot of scholarly papers with lots of bibliographical references. So when I first started working on the site, I sort of thought, wouldn't it be cool if every entry in the bibliography was an entity and we could then structure those entities so that we have all the elements sort of nicely stored and then we could create these wonderful views where you could click on a reference and see every other paper that's referred to the same thing. And I sort of had a conversation with the client. Does this sound like something you might want? And they just sort of said, no. We just need a list. So that's what they got. So it's really important to come back to Earth with these things sometimes. But there's a major caveat to that and that is that within reason, you should be thinking about future needs as well as present needs. So this goes back to the idea that you're not going to be changing your content model very often, so you do want to make it robust enough to deal with at least foreseeable future needs as long as that's not going to create too much extra effort. So here's a really good example of this. The LA Times, the Los Angeles Times, recently had a redesign where they introduced this new section to their website called Neighbourhoods. And these Neighbourhoods pages are essentially landing pages that collect a whole lot of different information about an individual neighbourhood in LA. So they've got a whole range of topics. They've got sort of statistical data. They've got news stories. They've got basically everything to do with a particular neighbourhood. Now, when this section was launched, the journalists at the LA Times had actually been adding geographical locations to their news stories for several years before the website had any use for this at all. So journalists were just told, well, when you write a story about a particular location, look up for the latitude and longitude and stick it in here. They obediently, I guess it was part of their jobs, they just obediently did it. I don't know how they were talked into it, but they did. And so the result was when the section of the website launched, it was already pre-populated with all this content because, you know, hey, Presto, we've already got all this stuff that's existed behind the scenes. And I think geographical, like, location data is a really good example of an element of content that you might want to think about adding two certain content types in anticipation of possibly needing it in the future. So I've actually done this on a couple of sites where we've had article content that's about specific locations, and I've known that this client at some point in the future has plans to have some kind of mapping functionality on their site and part of what they're probably going to want to do is show stories that belong to a particular location or a particular area. So by getting them to start putting that data in their stories right from the beginning, once they're ready to actually launch that functionality, they'll have that all ready to go. Okay, so, yeah, so don't be more granular than you can imagine ever needing to be, but do have a bit of imagination and think about, okay, what might we want to do in two years' time? So, you know, if you're building a site now and you can think of something cool, you can add to the content model that might make it better for the Apple Watch. You know, go ahead and do it. And let me know if you work out what it is.  And, you know, you can't even actually flick through to see the full story. It's just going to be a nightmare, anyway. Not our problem. And the third principle really is to start testing your content model with real content as soon as you possibly can. So I'm probably teaching this as a converted here, but why would you want to test a content model with real content as opposed to just making a nice wireframe or testing it with low-remix or, you know, develop generated content or something like that? There's a few different reasons why we want to do this. The first is that it allows us to see our real content in different contexts. So one of the really important things about content modelling is that it involves treating content as data. So, you know, in that sense, it's a very similar process to traditional data modelling, but we always need to keep in mind that content isn't just data. It's also narrative. And actually taking a chunk of content out of context can sort of radically change its meaning. So... That's right. A bit of Google Maps going there. No worries. Yeah, so taking a bit of... So testing with real content lets us spot the places where our content is out of context, so it might not be making sense and we might need to make some adjustments to allow for that. It allows us to identify false assumptions. When we're building a content model, we'll always make certain assumptions about things like character count. So we'll sort of say nobody could ever possibly write a title that's longer than 80 characters or something like that. You know, the sooner we can start testing that with real titles and real articles, the sooner we'll find out that those assumptions aren't true. This is a really big one, identifying edge cases and deciding what to do about them. So content models are neat and real content is messy. There'll always be... There'll always be pieces of content that don't quite fit into your beautifully designed model. And the sooner you start testing again with real content and testing with worst case scenarios as well as best case scenarios, the sooner you're going to figure out what those edge cases are. The sooner you know what to do in response. You can adapt your content model to adapt to the edge cases. You can shoehorn your edge cases into your content model or you can decide to treat your edge cases as something else altogether and just create some kind of custom solution for them. But the sooner you know what they are, the sooner you'll be able to make those decisions. And finally, finding the gaps... Find the gaps... Sorry, testing helps us to find the gaps in our content model. We need to identify those bits where we need some kind of reference field to create a relationship between two bits of content, but we haven't actually put it in anywhere. So how do we go about testing with real content? Well, for me, there's no substitute for doing it on a real Drupal site. So what I've started doing whenever I want to test a content model is to essentially build a prototype Drupal site. At this point, you might be thinking, if you're not a Drupal person, you might be thinking, I can never build a Drupal site and I'm here to tell you that you're wrong and I'll be going on to that in a minute. Okay, so there are my three basic principles. So I now want to talk about what content modelers need to know about Drupal. What I mean by content modelers is just anybody who needs to work out the content structure for a website. So that might be somebody with the official title of content strategist. That might be someone within an organisation who has the responsibility for looking after content. So if you're working with... If you're working at how to structure content for a Drupal site and you don't know very much about Drupal, here are some things that you really need to know. This is one of the bits that we'll be very familiar to all the Drupal people. So I apologize. Drupal is totally agnostic about structure. You decide almost everything for yourself. Honestly, when you first do a Drupal installation, at least if you're using the out-of-the-box version of Drupal, you basically get almost nothing. You get a couple of really basic content types. You get a front page that looks really weird that almost everyone ends up throwing out. And that's very different from the experience of installing something like WordPress for the first time because you basically you install WordPress, you have a website that you can start using. It's a pretty simple website but you've got something that you can start using. So on the one hand that makes Drupal a bad solution for your uncle who runs a phishing tackle business who wants to launch a five-page brochure website, but it makes Drupal a great solution for organizations with complex content that really gives you a blank slate that you can do do whatever you want with. Drupal's site built as a content model is by default. And this is what I meant by the title of the talk today, the Accidental Content Strategist that one of the interesting things about Drupal is that the first thing that you're when you do any kind of training in how to build a Drupal site, one of the first things you're told is well, you need to create some content types. So in order to do that you need to decide what your content types are going to be and then within those content types you need to decide what fields you need. So just the very experience of building a Drupal site forces you into a kind of content modeling mindset. So Drupal people really have a head start in this stuff that I think people using other platforms don't necessarily have. If you're building your first Drupal site, one of the surprises might be that you'll almost certainly need contributed modules to get your content model working. So everyone's had, you know, everyone who's built their first Drupal site has had the experience of I want to put a date field in here and oh, there's no date field and in fact you need to install a module to get a date field. You need to install a module to get an address field. You need to install a module to get an entity reference field, which is one of the most basic things that you could ever want to do in a content model. So that's just part of the story with Drupal is that a lot of the really common functionality at least in Drupal 7 is provided by contributed modules. Drupal 8 things are going to get slightly different. There's a lot more in core in Drupal 8. It is one of the quirks of Drupal that we rely a lot on contributed modules for what might seem like really basic things. And then finally I had this whole spiel about entities that I ended up abandoning because it was just going to take a while. It is important for people working on a Drupal website to know the basics about the entity system. So I'm just going to go through the really top points here. So in Drupal most content lives in entities and an entity is basically a piece of information or a collection of information about a thing or an object. So a blog post would be an entity in Drupal, an event would be an entity but also a user would be an entity. So in Drupal the entity system that includes a whole lot of different kinds of information. So from a content point of view the most important kind of entity is a node. And a node is the type of entity that's sort of designed around storing content. So typically in a Drupal site 90% or more of content will live in nodes. But what's interesting about Drupal from version 7 onwards is that this entity system has been extended to all kinds of other things. So things like taxonomy terms, users, comments and much more. And that has all kinds of implications but what it means for us as content modelers is that if it's an entity you can add fields to it. So one of the crazy things about Drupal is that you can add fields not just to nodes, not just to content types but also to taxonomy terms to users and to all these different things. So that's my spill about entities. If you want to learn more about entities you can read this page on drupal.org which you'll see is a node. So it's an entity. And yeah, obviously my slides will be uploaded to the website so I don't feel like you have to write that down but I definitely encourage you to learn a bit about entities if you're going to be involved in content modeling for Drupal sites. And then the final thing that I really want people to know about Drupal is that you can build a Drupal site yourself. And this is one of the really powerful things about Drupal is that anybody can download Drupal. Anybody, and I'm speaking from experience here, anybody can learn to build a basic Drupal site. Drupal does have a learning curve that's probably steeper than other systems. But once you get over the initial hump with Drupal, it's really amazing how much power you have in your own hands. So I basically sat down last year and did a whole bunch of video training at a site called Drupalize which is run by a really well known Drupal shop in the States called Lullabot. And within a couple of weeks I was doing things like building sites where I had all these really complex views of I played around with mapping a lot and I had maps where things would appear and disappear depending on the times of events and all that kind of thing. And it was just like I'm not a developer, I don't know any PHP I've done all this just in the basic sort of interface of Drupal. So Drupal is a really powerful tool even if you just use it to prototype and test your content model. So I was talking about testing your content model earlier that the single best way to do that is just to spin up a really simple Drupal site and start building some content types sticking in some real content and playing around with it. So that's my evangelist section of the talk. Yeah, so there's options out there for where you don't even have to worry about creating a database and all that kind of thing. I think it's good to have the experience at least the first time of doing it in a local dev environment and creating a database and running the full kind of installation process as it's documented on Drupal.org but it's definitely Drupal Gardens. There's also Acquia Free Cloud basically allows you to sort of create a single click Drupal website so it really sort of speeds up the process. So yeah, there are definitely quicker options out there than sort of running through the full process. Okay so the last part of my talk I just want to talk about some of the common issues that you come across with content modelling in Drupal. So this is where I get sort of more Drupal specific I guess and the first really major issue that you still see on a lot of Drupal sites is mixing content logic with presentation logic. So when I talked at the beginning of the talk about keeping your content model and your presentation model separate, this is kind of where the rubber hits the road with that stuff. Now Drupal is inherently better at separating content from presentation than some other systems. So we do talk about nodes for instance rather than pages so we do have this concept in Drupal that a node is one thing and a page is a different thing which is kind of a good start but it's still easy for presentation logic to creep into a content model in various ways and here are some of the ways that you will often see. I'm calling these worse practices but I'm not trying to blame anybody who's done any of these things, we've done them ourselves but I really think it's important for us especially as we move towards that more sort of decoupled world to really think about making our content model a pure content model. So there's obviously the traditional one big body field approach where we basically said to authors if you want this page to be formatted differently just do it in a table hardly anybody does that anymore but it is still something you see on some sort of legacy Drupal websites. Naming content types after pages is a really common one so I mean Drupal comes with a content type called I think it's basic page or standard page I can kind of live with that because it's not really part of the content model, it's really a sort of it's what we have to deal with everything that doesn't fit into our content model but if you're creating a content type called event for an event for instance call your content type event not event page because it will train authors to think about an event as a piece of content that might exist in several different places in the website rather than as just a page. Similarly naming fields after presentational elements you still see websites with fields that are called things like right side by content so try to use labels that are that don't presuppose a particular presentation model when you're naming fields like this so you could call it something like supplementary content or even break it down into further fields. And then finally there are particular modules that I think are kind of big culprits in sort of sneaking presentational logic into entities and one example of this is modules that allow you to select a view mode from within an individual entity so a view mode is a way of displaying the information in an entity so for instance a teaser you might have a view mode called teaser and another one called full content and you can create custom view modes for all kinds of different situations and there are certain modules that allow you to actually select a view mode when you're entering the entity itself or when you're creating the entity itself and to me this is just a totally wrong headed way of thinking about things it's like you're buying a pair of pants and a t-shirt and you've got the pair of pants sewn onto your t-shirt and you can only ever wear one t-shirt with your pair of pants it's basically saying I'm going to enter my content and choose a presentation style for it at the same time so bad stuff so bean is an example of this you don't actually have to use this option within bean but it is there and there's also a display suite extra that allows you to do this within you can basically tick a box in display suite that says allow authors to select a view mode from with a node or something like that and I love display suite but I would never actually use this particular extra and the kind of even worse version of that is allowing authors to build a custom layout from within an individual entity so something like panellisa and I know people use this module a lot but panellisa is a part of the whole sort of panel system and it allows authors to essentially sort of create a sort of customised layout within an actual entity and you know once again you're really breaking down the whole idea that your content decisions you make about content are different from decisions about presentation so realistically though I know that there are reasons why people use these things and the really major one is that authors need flexibility okay so you get this pushback from clients about over structuring their content and they say oh but we want to be able to we want to be able to just arbitrarily decide what's in the right sidebar of this page or you know not have a right sidebar at all or have a left sidebar stand blah blah blah blah we need to do all these we need to be able to make our own decisions about this stuff because we're in a world where nobody is ever creating a pay or sorry creating an entity for a single presentation model we really need to get clients away from this way of thinking and what I think we need to do is basically give them some flexibility around the way they structure their content without making that flexibility live in in layout so think about ways we can give them more flexibility and not impose you know loosen up our kind of what we impose in terms of structure without imposing a layout so a good example of a module that allows this is paragraph so I don't know if anyone's ever played with paragraphs before I think there's actually another talk going on about paragraphs as we speak so I'll be listening to the recording of that one I won't say anything more about it at this stage but go and listen to that recording because paragraphs is really exciting stuff I'm sort of running out of time I'm just going to briefly touch on entity types so we have the whole because we can add fields to any kind of entity we often feel like okay anything that's about a topic I'm going to add to a taxonomy term or anything that's about a person I'm going to add to a user there's all these things that you get in nodes that you don't actually get in other entity types so there are things like published or unpublished states authors published and modified dates, revisions revisions is a huge one, you only get revisions in nodes granular permission so saying I only want this author to be able to change this content type that's something you only really get in nodes searchability out of the box so Drupal core search out of the box works with nodes it doesn't work with other stuff and also comments at the moment can only be attached to nodes although you'll be able to attach a comment to anything in Drupal 8 which will be great so just be aware if you're tempted to think that all your topical content for instance should go within a taxonomy term then it's probably not it might not be the best idea so my sort of recommendation is to store only your sort of basic unchanging information in taxonomy terms and to actually create a content type for more substantive topical content so if you have anything that you think you might want to revise and be able to revert back to an older version of all that kind of stuff or sort of have a workflow for within the organisation that really still needs to be in content types and then of course you can use a reference field to link the two so you can say this content type relates to this taxonomy term yeah sure so imagine you have a taxonomy imagine you have a vocabulary of places of place names so I say cities and obviously the main thing we use taxonomy terms for is to classify other content but we might also have some sort of static content about the term itself so say I've got a Melbourne taxonomy term which I'm using to tag articles that are about Melbourne but I also have a lot of information about Melbourne itself like its population and you know I might have a little essay about the history of Melbourne and that kind of thing I might be tempted to store that information inside the taxonomy term but because of these restrictions with taxonomy that might not be the best idea yeah does that make sense to everyone so I kind of rushed through that point because I'm running out of time but yeah we have sort of similar issues with users as well and sort of recently struck a case where we really wanted to use the user entity type of people that weren't necessarily users of the system such as authors of articles and that kind of thing really got a lot of pushback from the organisation about that and one of the issues was that when they see the word user they expect that to be somebody who actually uses the website which is probably fair enough but another issue that we hadn't thought of was that within their organisation user accounts were actually controlled by the IT department so they didn't want to have the publishing team have to ask the IT department to create a new user account every time they wanted to add an author to an article so so you can think about you can try and be as pure as you like with these entity types and use the correct ones for the correct things but there are actually intrinsic sort of limitations in Drupal that mean you can't always do that okay so I'm almost completely out of time does anyone have any burning questions yeah yeah presentation model yeah that's a good question I guess it really depends on the project but yeah ideally there is one person on the project who has the responsibility for the content model and if you have a content strategist on the project that's that person if you don't then yeah I think you do need to pick somebody whose job it is to have that kind of supervision of the content model and to be able to work out when decisions that are made about development might actually be breaking the content model or when assumptions have been made about content that don't actually work about the model that don't actually work with real content that kind of thing so I definitely think it's a good idea to have one person who sort of owns the content model on a project yeah I just have one more slide I guess about making your content model author friendly I think it's all pretty straightforward so I'm not going to go through it I'll just leave it up there for those of you who are who are interested because this is another obviously another big issue with content modeling you want your content model to be something that authors can actually use once there once you've got it in place I've used up my 45 minutes so I'll let you go if you want to go if anyone does want to stay around and ask more questions then feel free but thanks everyone I've got some recommended reading as well which will be in my slides which will be on the website


Hi. Well, first of all, I'm in a new place. Before I was in my office with the books behind me, which I kind of like, but it wasn't very well lit. Here I get a lot of natural light. So let me know what you think about this new location. Unfortunately behind me, there's absolutely nothing because it's just a wall. But at least it seems better lit. And so I'm trying out as I am trying out this shirt for some reason. Anyway, today I want to talk about something a bit more technical, let's say, and it's something that I've sort of touched on in the past, but not really. And this is what to do when you're not sure about a translation. This is mostly for people who feel a bit insecure, especially when you're beginning. You'll you might see requests for translations or you people might want you to work on a translation or you think there might be a chance for a job or something, but you're not very secure. Like, I don't know if I could translate. I haven't translated things exactly like that before. They might have new terminology. I'm not ready for that, et cetera, et cetera, et cetera. I just wanted to address what to do when this happens. When you're unsure about your translation about certain terminology, about a certain term or anything like that, because this doesn't change. It doesn't go away. Even the most experienced translators have it happen to them. I can have jobs coming from my regular clients, maybe just the regular quarterly financial statement. They send me all the time to translate. It's just an update, but there might be some term there that I've never seen before. Now, I've already gone through more or less what I do specifically, but I, as I mentioned before, am an Italian to English translator specializing mostly in financial translations. So this means I use very specific websites that help me out with what I'm doing, but many of you deal with different types of translations and different types of specialties, and so that might not be very helpful. If you want to check out that video, I'll leave a link down below and say you can. But in this one, I'm hoping that I can give information that's a bit more general, so then it can help all of you. So what do you do? Say you accept the translation and they give you stuff to translate, and there are some terms there that you have no idea what they mean. What does that term sesquipedeliac mean? I have no idea what it means. So what do you do at that point? If you have an online dictionary or a bilingual dictionary especially, but even just a dictionary that's in one language, it can give you synonyms for whatever that term is, and it can help out. If you can find it there, that's great. If you can find other websites that deal with certain types of terms, like maybe it's a specific term for a certain type of industry, or a type of sector, a segment, or whatever, and if you can find dictionaries that deal with that specific industry or sector or segment, then by all means go there. And by the way, bookmark whatever websites you find that are useful, because you're definitely going to need them in the future. But maybe none of that helps. So where else can you go? This is usually the point, at least for me, when I started where I started panicking because I'm like, I can't find it on any dictionaries and so I don't know what to do. One thing you can do is, if it is a term, say it's a couple of words together, or even if it isn't, try taking the couple words in this context, put it in quotes, and then just googling it. See if it turns up anywhere else, because you never know. Often what happens is that you're translating something for a company, and they've already translated the same term before, and you'll find that term on their website, and that can be translated again. Usually, if this is the case, the company should have sent you a glossary of their past translations, but if not, you can always, if you find something like that online from their website, absolutely, you can feel free to ask them if they have past translations, a glossary, or anything along those lines. So the first thing to do is, yeah, put it in quotes, whatever the term is, or the word, or a set of words, and search for it, and see if it pops up anywhere. And, you know, see if through that you can get a translation and see what you can do with that. The next step, if you say you still can't find anything for your translation, you still have no idea how to translate this specific term, then you go to forums, there's translatorscafe.com and pros.com. I've mentioned these websites a million and a half times purely because they're the most helpful websites for translators. And go to these forums and, or a lot of them have just a glossary, have an online dictionary, et cetera. Search for it there. First of all, search to make sure it doesn't exist there somewhere already. And if it still doesn't, ask. You can always ask a term there and people are so helpful, you can just ask, hey, I came across this term, I have no idea what it means, or I have no idea how to translate it, does anyone know? And you'll pretty much always get quite a few answers, a good number of answers within 24 hours. And then you can go through those, sometimes it's back and forth, you can speak with them and try to figure out which one you like best and which answer works best in your specific situation. Don't be scared to do that. Every time that I've done it, it's been super helpful. Of course, it can take a bit of time because you usually need at least those 24 hours to look it over. So bear that in mind and don't wait until the last minute to do it, but know that that avenue is always open. Now, maybe once you do this, and once you get your responses, you're still not 100% sure. So what you can do at that point, and you can do this with any terminology, any term you translate, you can always send it to the client and tell them, look, if you have any questions, or if you're not sure about any terms, please feel free to get back to me. Always mention that you're available for any questions or any issues because if they find an issue, they should be able to reach you and then you work with them and then they'll be happy. So don't panic also if they say, hey, I don't get why you use this term to translate it. Do you think that's right? Don't be scared about stuff like that because you can always explain your logic. Well, I thought because this and this and that, they say, oh, no, no, no, usually we deal with that and that and this, and then you say, okay, then in that case, you should use this term. Something along those lines. Don't be scared to do that. Don't think, oh, no, I made a mistake. They're going to hate me. They're going to hate me. No, you know, you're working with them and frankly, they might be blaming themselves as much as you because it may be something they feel like they should have explained to you. Obviously, don't start blaming them or don't start saying it's not my fault, not my fault, but work with them to try to come up with something. So you do have all these avenues and so, you know, you can look it up and if you can't find it anywhere on any dictionary, you can feel free to ask and people always help on all these forums because there are quite a few people and so, you know, you can usually find some help and then you can always ask the client. And many times what I've done is explained. I'll be like, look, I use this terminology here because of this and this and, you know, and how it's been used in the past and so I think it works well or, you know, what also happens is sometimes one word gets translated in two different ways depending on the context. Anyway, things can get very complicated once you get into it. And if it's something that I think will confuse the client or that they might not like, I try to preemptively explain what I did. Otherwise, I just send it and then, but I'm ready in case they ask me any questions or have any issues, I know what to reply. So hopefully all of this can help you and so you can feel less insecure and more secure when you're dealing with potential translations. So you can actually accept your first translation or, you know, a new client and work on their translation knowing you can get through it. But you'll notice something here. You definitely need to make sure that you leave enough time. You need enough time to work on this. Like I said, it can take 24 hours for someone to reply and then you need to look all this stuff up and you can use this to your advantage. Say you're talking to a client and the client, you know, they need something translated. You're like, okay, I can do it for 50 bucks and they're like, no, 50 bucks is too high. Then you can try to negotiate with time. You can say, okay, look, I can do it for 30 bucks. But how about I do it for 30 bucks, but you give me an extra day or two extra days.   What this does is it gives you more time to then go on these forums and ask people if need be or do your search and try to find stuff. Try to try to find the right solution. So try to negotiate with time whenever you can. Now, obviously the bad part there is that you get paid 30 bucks rather than 50 bucks. But especially when you're starting out, and I've mentioned this so many times before, when you're starting out, ratings and referrals should always be very important to you probably more important than the money you make because you can use those ratings and referrals to make more money in the future. So it's an investment. So I wouldn't worry so much about not making those extra amount of money at the beginning, but instead concentrate on doing a good job and getting those good ratings and referrals because you can use that later to make a lot more money. So just learn how to use this to your advantage and know that you can translate any term out there as long as you have the time to do it. And I'm not saying to go accept some ultra, ultra technical translation, even though you've never touched those things before, because that will take you forever to translate, trust me, and or medical stuff or stuff like that. Those are very specialized. I mean, if you can try to look up every single thing, but it will take you forever and chances are even then you might make some mistakes. But if it is something that you're more or less used to, and you're just afraid of certain terminology here and there, then go for it because there's always a way to find the right terminology. And by the way, in case I didn't mention this before, if you do find a term that you're happy with or you find a way to translate some term you didn't know before, always write it down. Keep a glossary. I've done videos before. If you search for under my videos under glossary, you'll see the glossary that I keep. It's very rudimentary. You can do something on Excel. It's very easy, but you need to keep the term you translate somewhere. If it's something you had to look up, then absolutely jot it down and keep it for the future because it's going to come up in the future and six months from now, you're not going to remember what it was. You're not going to remember where you found it and you don't want to have to go through that same huge search once again to search for it. So anytime you find a term, keep it in your glossary so you have it for the future. Really, you really need to. So I hope you found this helpful and again, I hope it helps you in accepting those translations early on where you might feel a bit insecure just to know that there is going to be a way to deal with it. If you know of other ways of dealing with it, then please feel free to let me know. I'm always happy to know of other ways to find good translations. That's pretty much the process I go through. And now, like I've mentioned in other videos, I have my go-to websites that I check and usually I'm able to handle 90, 95% of all my issues with those. And over time, you'll find your go-to websites as well, which will help a lot. But in the meantime, just know that help is out there and you always have those forms you can go to and people are very super, super helpful there. And so don't be afraid to do that. That's about it for now. I hope you found this useful. If you did, please click like because that always helps. And don't forget to subscribe so you can get more videos like this that help you with your freelancing, with your freelance translation. And I'll see you in the next video. Okay, thanks. Bye.