Hi everyone, Joe for Jaspy's casewrakes.com with 2022 Topps Chrome F1 Sapphire Formula 1 really nice stuff here three box random team number six. It's only a 10 spot break all card ship of course and There's the all other cards that features the F2 and some other teams that aren't on the list etc etc Big thanks to this group for making it happen. So we only it's a 10 spot break But we only sold nine outright one of you is gonna get a free spot a little buy one get one scenario for somebody Let's roll it randomize it five and a four nine times for the nine spots spot on top It's the extra spot one two three four five six Seven eight and good luck ninth and final time. It's Matt There you go Matt Johnson after nine You get an extra spot There are the teams right there now. Let's Randomize you a team. Let's roll it and randomize it three and a six nine times different nine one two three four five six seven eight and Ninth and final time three and a six nine times for the teams one two three And good luck ninth and final time after nine we got Red Bull down to Aston Martin Red Bull finishing one two couple days ago For stopping finishing second this time Aston Martin right behind them too Matt. You got Red Bull Jason with McLaren Michael with Mercedes Harry with Alpine Michael with Alpha Romeo Matt with Haas Brian with the all other cards F2 track cards Alphatari so on and so forth Rob with Williams and Ferrari and Matt with Aston Martin Let's sort this by team here alphabetically And we're in a positive video for just a little bit when we come back We're gonna see if there's any trades then we'll have the break stick around BRB Alright, welcome back everybody. No deals were done So that list right there remains the same Thanks everyone for getting in we've got another three boxes in the store right now Just piece case breaks calm same deal if you buy a spot chance to win a spot some color in there already There's George Russell. We've got a max for stopping behind him driver of the day. It's pretty good 23 out of 100 nice That's for Red Bull. That's gonna be for Matt There's another verse stopping here in a charlotte Claire, and we got Carlos signs for Ferrari 005 out of 199 That's gonna be for Rob got some verse stop in some Lewis Hamilton's Lewis Hamilton's will go to Michael and Mercedes All the first stop is going to Matt and Red Bull and This purple Esteban O'Conn is for Alpine. That's gonna be That's gonna be for Harry and Alpine out of ten origins not full Little baby in the twitch stream We still have a we sell a filler to go. It's right next to the sold-out origin. So always look out for that There's Yuki Sonoda 13 out of 50. That's for Alphatari It's gonna go to Brian It's George Russell and a carl of science nice first box In fact the filler for that origin still should be in the in the twitch stream chat Just click that help us fill that we'll get it or it's officially full give away the ten remaining spots there Formula one fans. We've got another three box break of this in the store as well. Just be case race calm check that out Run this back tonight pretty easily Shall go on you. There's Lance Stroll 43 out of 50 For Aston Martin, it's gonna go to Matt with the spot that he won Aston Martin looking pretty good So far this season another verse stopping and Dennis Hager 88 out of 99 And that f2 spot Brian without and we got a you move Iwasa future stars 25 out of 100 going to that f2 spot Brian Aiman and there's a Charlotte Claire for Ferrari 94 out of 199 Rob with Ferrari Yeah, it's always good to double check we we often do here on this channel. We often do those filler breaks to help People get into a break in a different way So always double check for those whenever you see something sold out There's a ward winners Lewis Hamilton for Mercedes. That's for Michael. There's Enzo Fittipaldi 16 out of 75 Future stars for that f2 spot Brian Haman and Max Verstappen Grand Prix winner the third and final box Yeah, sometimes we offer those fillers because it's a way to get into the main break for a fraction of the price Sometimes people like to take that risk instead of getting a full spot All right third and final and we also have a Google doc with the break schedule on there So you don't have to be in the chat You can just monitor that page as well and you can See when that break is coming out because when it's officially sold out it'll be on the schedule. All right Other Max Verstappen and I like these sepia toned cards are pretty cool There's Roy Nassani 25 out of 100 F2 Brian and if those F2 drivers end up becoming F1 drivers, that's a good one to have There's Lewis Hamilton and Nicholas Latifi 83 out of 199 For Williams, that's gonna be for Rob and Williams racing Lewis Hamilton for stopping And a black-and-white Max Verstappen that's 14 out of 15 nice low number there from Matt and Red Bull Well worth the wait Matt Matt with Max All those other cards those base cards will all add up as well and there's a pure ghastly orange 13 out of 25 that's for Brian and Alphatari And we got Jack Duhan future stars to 199 for Brian and the F2 spot And we got Charlotte Claire and Jalgan you back there as well nice sapphire edition real sharp stuff Another three box break on Jasper's case breaks.com right now. I'm Joe for Jasper's case race calm And I'll see you next time for the next F1 break


8 ways to develop the speaking abilities of kindergarten students. A teaching job abroad is another level of everyday challenge but is a fulfilling one. With my teaching experiences, I started crafting my own ways on how to develop the English speaking skills kindergarten level students, especially the non-native speakers. 1. Have a routine. Routine is one of the most vital things a kindergarten, teacher should keep in mind while teaching kindergarten learners. A well-established routine helps the learners follow instructions effortlessly, and remember the things you taught easily, such as instructions and songs. 2. Be as animated as you can. Being lively in class adds up to the interest of the children in going to school every day. Going to class every day is also a very big factor in learning something in English, because if a student comes to school every day, they can practice English speaking skills as well. Learning a dynamic teacher in class is also inviting students to be an active speaker as well. 3. Provide various related and meaningful materials. Offering different resources that kindles the interests and curiosity of the children will definitely contribute to their language building. Example of these materials is common pictures of things around them, realitya, toys, and even the posters we stick on the walls inside the classrooms. 4. Books and stories. Learning big books in the class will also be helpful for them in learning the English language. From time to time, the teacher must engage the learners into a big circle and conduct a story reading or a storytelling activity. The teacher can ask them open-ended questions or verbal gap fills about the story or pictures and encourage them to ask a question. If students ask questions, the teacher should always attend and respond to them to encourage more questions on the next activities. 5. Play with them. Learning is one of the best ways to communicate with students. As an EFL teacher to kindergarten students, play is the common language to everyone in the classroom at first. Starting from there, a teacher can build a connection with them, and can start teaching them simple English words that will be of great use in the activities. Singing English children's songs will be very fun and evocative to students since, the rhythms and lyrics of the songs are catchy and easy to remember. In this also, a teacher can insert teaching the correct sounds of letters and words so that pronunciation will be better, the songs taught to them will mark in their minds, and will even sing those wherever or whenever they want. 6. Do not exhaust them. Teaching in a kindergarten classroom requires energy and hype. Having breaks in between will be great for them. If kids are too tired of the activities, the tendency is that they might start being rowdy. If this happens, classroom management is affected. To counter this event, give or insert a nap time for the kids in the daily class routine. 5-15 minutes break between heavy activities will be more accommodating. 7. Expose them more. Having field trips are also arousing activities. Exposing the children to the surroundings will make them more curious making them ask a question. In this way, a teacher can have the opportunity to communicate with the students. A field trip can happen even around the school campus, such as a garden, the canteen, the waiting area, or even in the playground. A field trip can also be outside the school campus, like parks, market, city library, or a museum, but going out is not necessary. As long as they are exposed, and they are encouraged to ask and talk to each other and to the teacher, it is good. 8. Assess them. Assessing kindergarten is not like assessing high school students. There are different ways of assessing these learners. Instead of graded report cards, a teacher can have performance tasks for students. These performance tasks will surely help the teacher identify the strengths and weaknesses of the students. One of the well-known activities to assess the speaking skills of the kindergarten students is the show and tell, where they bring something of their own interest in the class, and share something about it in front of the teacher, and their classmates, or sometimes even their parents. The results will then be written, or so-called anecdotal records. The results will then be analyzed by the teacher, and if there is something that is needed to be improved in the speaking skills of the students, an intervention might be done then. Do you want to teach English abroad? Take a TEFL course today. Kindergarten is the most crucial part of learning since it is the foundation years. This stage will be of great impact to learners' success later in life. If we teach them properly and invite them to be active learners, results will be great in the future. In a similar manner, teaching the non-native speakers in the kindergarten level is not an easy task but it will be surely fulfilling. As teachers, the passion for molding children to be better should always be the reason for teaching them.


Excellencies, distinguished participants, dear friends, ladies and gentlemen, I am very pleased to be in your midst today as you launched the important work of the Preparatory Secretariat for the next ITU Plenary Potentialary Conference, which is scheduled to be held in Busan from the 20th of October to the 7th of November, 2014. The ITU Secretary General, Dr. Amanon Tui, had wanted to deliver this video message himself, but has unfortunately been unable to do so due to his current travel commitments. Dr. Tui has especially requested that I express again his appreciation and that of ITU for the excellent organization and hospitality shown to him during his recent visit to Korea in September of this year. He was impressed by the well-established preparation plan the Korea Administration has made, and the goodwill the city of Busan has shown to him. At ITU, we are particularly looking forward to returning to Busan after ITU telecom Azure in 2004 held in Busan. We are very confident that Busan will provide an excellent platform to host the PP-14 with its efficiency, hospitality, and beauty. Returning recently from the ITU telecom world here in Dubai, we had the opportunity to visit the Korea Parvelling, where everyone was so impressed not only by the dancing robot, but by the excellent PP-14 welcome stand that was already providing invaluable information about the PP-14 and our host city of Busan. I would like to take this opportunity to share with you a good news that in the recent published report, the Measuring the Information Society report 2012, which is an ITU annual statistical report, Korea remains number one among 160 countries registered in this report. We sincerely congratulate Korea for its marvelous achievements in ICT development. Ladies and gentlemen, the Plenary Potential Conference is the top policy-making body of the ITU. Held every four years, the conference, among other tasks, we assess the unit's general policies, adopt a four-year strategic and financial plan, and elect the senior management team of the organization, the member of council, the members of the Radio Regulations Board. The PP-14 in Busan will be a pivotal moment for the unit. With the launching of the preparatory secretariat today by the Korea Administration, we can be confident that we have started our journey to PP-14 in a timely and efficient manner. On behalf of the secret general, the other elected officials of the ITU, and all ITU staff and members, we congratulate you on the launching of the preparatory committee today, and look forward to working closely with you to ensure an effective and successful Plenary Potential Conference in the beautiful city of Busan in two years' time. Thank you very much for your attention.


Hi, I'm here to answer more of your burning solar eclipse questions. I'm Danny Mili Salvovich, Associate Professor of Physics and Astronomy at Purdue University. Next up, what does totality mean, and why should I care? Finding a viewing place in the path of totality just may give you a once in a lifetime experience. Just south of here, Indianapolis is one of a few major U.S. cities that will be in the path of totality, for the 2024 total solar eclipse. This means that for just 3 minutes and 44 seconds, on April 8th, the moon will completely block the sun from our view. We call this period of time totality. During totality, the only part of the sun that will be visible is the corona, which is the sun's outer atmosphere. Aside from its faint glow, most of the light from the sun will be blocked, and it will become dark, almost like sunrise or sunset. From our vantage point in Indianapolis, we will get to see all phases of the total solar eclipse, which includes a partial eclipse. This takes place both before and after totality, as the moon moves across the sun, covering more and more, and then less and less of the sun from our view. Anyone who is close to the eclipse, but isn't in the path of totality, will only be able to see a partial eclipse. From their perspective, the moon will cover part of the sun, but will never completely cover it. That makes us extremely lucky to see the eclipse. The next time a total eclipse will be visible, in this part of the world, will be in 2044. So make sure you get out there to see it. Get tickets for our total solar eclipse event in Indianapolis at purdue.university forward slash solar dash eclipse. Boiler up.


The best spray detailer depends on personal preference. Maguire's classic quick detailer in the Burgundy bottle has been trusted by car enthusiasts for decades and works great to help remove light dust and fingerprints and is a great choice to use as a traditional clay lubricant. If you have a darker colored vehicle and are looking to maintain a wet look only a dark color can provide, our gold class premium quick detailer is a great choice. Maguire's ultimate quick detailer offers our most premium option utilizing hydrophobic polymer technology, delivering an amazing ultra slick application and glossy finish while our hybrid ceramic detailer is a definite go-to to maintain the amazing characteristics of our hybrid ceramic waxes. Whichever you choose, remember to work on a cool surface and use our premium clean microfibers like our Supreme Shine microfiber towel.


Cardi B has been telling us since her 2018 hit song I Like It that nobody stunts half as hard as she does. And this little tidbit of information has never been truer than it is today after this freshly turned 29-year-old received a truly epic birthday gift from her husband, rapper Offset. And no, I'm not talking about their newly delivered beautiful baby boy. Instead, I'm referring to the $1.49 million investment property they just scooped up in the heart of the Dominican Republic. And today, we're going to check it out. In these videos, we don't reveal any addresses and even though I've done a house tour of my own place, please do not show up at any private residences because it's not safe for anyone. Cardi B is a rapper who first kicked off her career as an internet celebrity. These days, she's worth an estimated $24 million and she lives with her husband Offset and their children in a gorgeous Atlanta mansion. Now the happy family also has the vacation home of their dreams. Cardi has long been imagining herself owning a rental property and now that day has finally arrived. She wrote on Instagram. For a hot minute now, I've been telling Offset that I really want to invest in a short-term home rental property in the DR and other Caribbean countries, but I felt like he didn't agree with me and would rather put money into other investments. While as Cardi herself soon found out, she was completely wrong. Hey guys, it's Cara the Vampire Slayer back with another exclusive house tour here on Famous Entertainment. We're going to get an in-slide look at Cardi B's tropical paradise getaway that you too could potentially stay at. Be sure to subscribe and ring that bell for notifications because we post brand new videos daily. As always, you can follow me over on Instagram to chat and now let's get into this video. Let's get one thing clear off the top. As unbelievably gorgeous as this new home is, you need to keep in mind that it isn't even Cardi B or Offset's primary place of residence. After all, how many Hollywood celebrities do you know like to shun their entire industry by living their days off-continent on a Caribbean island somewhere? Yes, I'm aware that's basically how Sean Connery spent a lot of his final decades on this earth, but let's be honest, that's one ornery and unique Scotsman right there. And while Cardi B and Offset are most certainly unique, they aren't quite as anti-socialist Connery could sometimes be, which is why they'll still be spending most of their days living in their mansion out in Atlanta, Georgia. A while ago, we took a look at that place with its very own house tour, so if you're interested in staying inside their everyday family home, be sure to check that video out when you're through with this one. But for now, let's kick things off by walking you through how Cardi received one of the biggest surprises of her life. It all started with a birthday celebration that was thrown for Cardi a short time ago in L.A., a dance hall-themed event that was full of Hollywood superstars. At one point during the night, Offset took to the stage to shock everyone in the room, announcing that since he had already bought Cardi some of the biggest diamonds in the world, next, he was gonna get her something that meant even more. That's when he dropped the bombshell by revealing that he had bought Cardi her dream vacation home in the Dominican Republic. After hearing this news, Cardi B was left speechless, which I'm assuming was probably one of the first times that's ever happened to her in her life. And really, who could blame her? Just wait till you get a peek inside this place. While it's unknown exactly how much Offset wound up spending on this property should be noted that prior to the sale, this seven-bedroom, seven-bathroom mansion, situated on 8,000 square feet of hillside, had previously been on the market for a listed price of $1.49 million. This four-story residence is located in a private and gated community in the resort town of Elastarenas that boasts three outdoor tennis courts, private beach access, and even its own helipad. Moving on to the property itself, this home features not one but two primary entrances. Once you've stepped foot inside, you'll quickly come to realize that one of the coolest things about this home is how much it embraces its surrounding landscape by using mostly natural materials throughout the home's interior construction. The gorgeous texture of exposed wood is what especially stands out as a pop of color against the otherwise white walls of the inside of the home. And nowhere is this any clearer than when you're looking at the central staircase that simply put could take your breath away with its expert craftsmanship. Further into the home, the kitchen offers up a double fridge alongside the standard appliances like a microwave, burner, gas stove, and island bar with classic seating arrangement. The nearby dining room is connected to the kitchen and offers breathtaking views of the surrounding area thanks to its floor-to-ceiling windows. Moving on to the living room, things may look a little cramped in here, but there's no shortage of seating options and that flat screen television is almost always going to have some steep competition with the dramatic views going on just outside of the nearby sliding door. Of the seven bedrooms that are available, I don't think anyone is going to feel put out if one room gets claimed before another because they're almost all the same size. But I will say that whoever lines up with the bedroom that walks directly out to the lap pool is definitely the winner in my book. Not to mention up on the roof of the building, there's even more going on. I'm talking a rooftop infinity pool with built-in lounge chairs, fountains, and picturesque views of the surrounding lush greenery. There's also that smaller-sized lap pool that's available for those looking to be a little more active-minded with their downtime. I don't know about you guys, but I'm going for the infinity pool and a floaty type of vibe. Finally, there's a rooftop dining area that comes complete with a grill, sink and overhead awning for those rare nights when that island weather just isn't cooperating with whatever you have planned. Oh, and did I mention the gym? Because yep, that's up there too. Last but not least, the property also features an individual one-bedroom studio that has its own living room, bedroom, and bathroom. As I mentioned earlier in the video, despite how amazing this home obviously is, the primary reason that Offset bought it in the first place was so that Cardi could finally live out her dream of having an investment property. After Offset announced his surprise gift to his wife, took to Instagram to let the world know how happy she was that her hubby had been listening to her the entire time, even when she thought he hadn't been. She wrote, I'm so happy that you are actually listening to me and not just smiling and nodding your head, so I could stop talking to you about it. You don't think my investment ideas are whack. And while it's unclear how much exactly Cardi stands to make from this new property, you can already rent the place out yourself over on Airbnb, where it's available at around $836 a night. I'll do some quick math just to give you an idea for how much Cardi might be raking in. So at $836 a night, let's assume that a place this nice gets rented out at least five nights a week. That gives us a weekly haul of around $4,200 give or take. That $4,200 would turn into about $17,000 a month, which means that annually, Cardi and Offset would be clearing around $200,000, not so shabby. In about a decade or even less, this place will have paid for itself. So now we've seen Cardi B's beautiful new Dominican oasis and that brings us to the end of our house tour. What do you guys think about Cardi's newest business idea? Would you rather just live in the stream home yourself rather than rent it out? Which was your favorite room or spot in the vacation mansion? Let me know your thoughts in the comments down below and be sure to like and subscribe to our content. As always, thanks for watching. Don't forget to follow me on Instagram and I will see you all in the next video. Bye.


This video will cover the following objective from the reproductive system. Describe the location and structure of the ductus deferens, seminal vesicles, prostate gland, bubble urethral glands, penis, and scrotum. The external genitalia in men is the penis and scrotum. The male gonads, the testes, are protected within the scrotum. The penis contains the urethra that functions for both the urinary and the reproductive system.  The sperm travels out through the urethra. The tip of the penis, the distal end, is known as the glands of the penis. And there is a fold of skin covering over and protecting the glands, known as the prepuse or the foreskin. Although the prepuse or foreskin is commonly removed in the process of circumcision. Sperm are produced inside of the testes in the seminiferous tubules and then are transported into a long-coiled tube that hugs the posterior and lateral and superior surfaces of the testes, known as the epididymis. The epididymis functions to store the sperm as the sperm mature before they are released in the process of ejaculation. Sperm will then be transported through a system of ducts from the epididymis into the ductus deference. The ductus deference is also known as the vas deferens. The ductus deference travels through the spermatic cord up into the pelvic cavity. As it's traveling superiorly towards the pelvic cavity, the ductus deference is located inside of a bundle of connective tissue called the spermatic cord. The spermatic cord will connect to the inguinal canal where the ductus deference will enter into the pelvic cavity and continue traveling until it reaches the ejaculatory duct of the prostate gland. Sperm is released from the ductus deference into the ejaculatory duct during the process of ejaculation. The ejaculatory duct is found inside of the prostate gland. There are a pair of ductus deference that connect into the ejaculatory duct. There are also a pair of seminal vesicles that are located just on the posterior surface of the urinary bladder that have ducts connecting into the ejaculatory duct. The ejaculatory duct forms from the union of the ductus deference and the seminal vesicle. Then the ejaculatory duct will connect into the prostatic urethra. The seminal vesicles produce the majority of the volume of semen that functions to nourish and help transport sperm during ejaculation. The semen will be transported from the ejaculatory duct down through the prostatic urethra and into the membranous urethra. The prostate gland also produces some exocrine secretions that contribute to the volume of the semen helping to nourish and protect the sperm. The bubble urethral glands are located just adjacent to the membranous urethra surrounded by the external urethral sphincter. The bubble urethral glands produce just a small volume of semen that functions to help neutralize acidity of urine inside of the urethra to help prepare the urethra for the majority of the semen to be transported through without being exposed to any acidic residual urine inside of the urethra. Then from the membranous urethra the semen will travel down through the spongy urethra inside of the penis. There are three major regions of the penis. The root of the penis is the deep region anchored to the ischioramus.  The corpora cavernosa are a pair of erectile bodies located on the anterior and superior regions of the body of the penis anterior and superior to the spongy urethra. The corpus spongiosum is an erectile body that surrounds the spongy urethra in the body of the penis.    The engorged erectile bodies push against the penile veins and venules which slows the rate at which blood can drain out of the penis, helping to maintain a stiff erection which enables sexual intercourse.


Awesome, well, thank you everybody for coming this morning. We're really excited to be here and thanks for taking your time to listen to our session. So we're going to be talking today a little bit about finding the right Drupal partner through your RFP process. And just to introduce ourselves, my name is John Stewart. I head up ZenSource, our product development, business development, and really working with our agent scene development partners to develop web apps. I'm joined by Jake Bell, who's our chief architect, who's going to talk a little bit more about some of the technical details about what goes into things. But Jake leads up our cloud architecture and oversees the engineering for our experience platforms and code base. So a little bit about us. We are an open source platform combining Drupal hosting, Drupal support, and an experience design system. And really what we are geared to do is partner with our agencies and help clients provide a foundation, Drupal foundation infrastructure, and accelerate their web development. We're based on the East Coast, three offices up and down the East Coast of the U.S. and to work across a lot of different verticals, healthcare, education, financial manufacturing, so those are our big ones. So what we're going to talk about today is really a few different things. So this is really geared toward both the client side as well as the partner platform side. So from the client side kind of understanding if you're developing an RFP for a new Drupal partner, whether it be development, whether it be a Drupal platform, hosting support, et cetera, or if you're the site builder and fielding those RFP responses, what are the types of things you want to look out for, what are the types of things we're seeing and seeing success with when going through that pitch process and getting selected to work with a different client partner. So just kind of starting with the summary of truths about Drupal and what are the clients asking us? What are they asking us to solve? Why are they coming to Drupal? So starting with community or culture and industry, why do we love Drupal? It's flexible, it's grown to an enterprise level in terms of its security, we're able to get the market faster and we're minimizing financial risk with the tools that are available in terms of our time, in terms of our budget, in terms of the things the community provides. From a community perspective, leveraging the community to develop features, but also having it be easier to upgrade and support and cost, seamless third party integrations, making sure it's future proof. From an experience perspective, having the admin experience be marketing and content author persona first, sourcing what we can from the community, things like layout builder, various authoring tools, but also building our own features to streamline things for our client authors. And Drupal's constantly evolving from a marketing perspective, the API capabilities, cross channel marketing and being able to push content out. These are the things that our clients are asking for, whether they're already on Drupal or they're already committed to Drupal, or if they're considering it, this is what we're really hearing, what we're seeing going to the RFPs. And just kind of looking at who our personas are, who our clients are, what are we hearing, what are they telling us? They're saying that their current CMS is limiting, it's not flexible, it's more expensive to make updates, there's too much code that goes into making updates. The CMO side is probably saying, I'm looking at not just a website, not just a web app, but an experience platform, how are we driving conversions, how are we in the education space getting more admission fulfillment forms in the healthcare space, how are we getting more requests and appointments, things like that. And from our CTO side, we're hearing the needs of their current CMS is probably end of life. We're hearing more and more that why are we going to Drupal because it can live anywhere. We can develop it anywhere, we can support it anywhere, we can host it anywhere. And we're hearing from our IT partners that they like that freedom and flexibility to not be tied to one vendor, but in many cases have a smaller team and want to know that you've got a partner that can support it. One thing that's really interesting that we're seeing more and more, over the past couple of years in particular, I feel like every single client comes to us, every single prospect comes to us and says, I don't want to re-platform ever again. I don't want to redesign ever again. I want to do this one time and I want to continuously evolve. I want to continue to build on top of our tech strategy, build on top of the foundation. I don't want to come back in five or seven years and have to re-platform again or do a really costly upgrade. Going from seven to nine or seven to eight or nine is a pretty big leap and beyond that. I want to know that those upgrades are going to be pretty painless. You know, at Zen Source, one of our big features is that we maintain all of our clients for their security updates, but also we do all of their upgrades, incremental and the major releases so that they're always on the latest version. But that's, you know, I think in terms of the RFP process and understanding how you can deliver a web app and experience platform for your clients where they don't have to worry about a re-platform or a major expensive upgrade in the near term and can really focus on growing their tech roadmap, doing the things beyond phase one to really evolve that ecosystem. That's what really after and that's what we're hearing the most from our clients. And, you know, from the authoring perspective, often we're hearing that that old system is just not flexible. It takes too long to do things. Our brand's getting lost because maybe we have too much flexibility. So in terms of when we get these RFPs and we get these proposals to go and pitch our clients whether you're coming from a development shop or a platform for hosting and support and more like ourselves, what is success going to look like? You know, from the client perspective, we want to make sure that we're delivering on time and on budget but avoiding those hidden platform costs and those ongoing development costs being able to maintain that. You know, delivering a platform that is true to that strategy. One thing we often talk about is that Drupal should be a platform that really enables your digital strategy. It shouldn't be limiting that digital strategy. It should be helping guide and enable. So creating a platform that allows them to stay true to that strategy but also really evolve it over time. That's what success will look like. And all while making sure that that code base is flexible, the authoring experience is low code. It's easier to maintain with less developer support. And that ease of authoring, making sure that the onboarding and the retention with the internal audiences, that's probably paramount to anything, making sure that the authors can maintain this thing and retain the knowledge within the tools that we build. And we're going to talk a little bit more about this in a moment, but making sure that that content migration is smooth in the ease of that scale for additional content. The content migration part of the process is always the most time consuming. It's always the most expensive and it's always the most stressful because there's just so much that goes into it. And really factoring in the time, the budget, and making sure the partner has a really good idea of how to migrate that content and migrate it effectively is going to pay for itself tenfold down the road. So where do we start? Finding the right platform and partner that shares revision of that brand enablement and that strategy. So through that RFP process, finding the right development partner, but also finding the right platform for hosting, for support, for additional features, design system, whatever it might be, that's what we want to figure out in the RFP process is to guide and vet those different vendors to make sure you're finding the right partner that's going to meet all of your needs. So different things, different approaches to look out for, things that we're always working with our clients as we develop RFPs to make sure we're vetting but also things that, you know, from the platform side, we really want to make sure that we convey and build trust in our clients and in our prospects is around how we approach the admin experience. So, you know, in that process really inquiring into the vendor's process for developing the admin requirements but also deep diving into that admin design process. So we all know we're all here because we love Drupal, it's highly customizable, there's a ton available in the community, but it's also something that we can really partner with our clients, our authors, our Drupal development partners and really be collaborative in terms of the workflow and the different authoring tools that we build. So one thing we always encourage our clients to do and from our side always offer to our clients to show our demos of our work. So, you know, we've, whether we're building a site from scratch or we're taking over a site or maintaining it, not all Drupal sites, Drupal 8, Drupal 9 sites are created equal even though they're using a lot of the same modules, maybe the same distribution, whatever it might be, the results can be very, very different in terms of the implementation, in terms of the approach. So I think it's really important to work with any potential partners to figure out, you know, how do they approach the admin experience design and what does it look like and is it going to work for us? Because, again, what we've seen is some are incredibly easy and intuitive and, you know, all the fields are in the right place and labeled great and in, you know, really great use of Layout Manager and a variety of other tools to help remove friction from the admin, but other sites on the exact same platform, exact same set of modules, we've seen just things that are completely different than that. So it's really important to really pressure test that. And, you know, one way we've been successful doing that, we call it a product playbook, maybe you call it requirements, we also call it a build a reference guide from time to time, but really defining the business and function requirements but also putting a lot of time into the platform and custom experience needs. This is a process that we always encourage our clients to do and we account for quite a bit of scope up front in the discovery phase to make sure that we're doing this together. So what does that mean exactly? We do stakeholder interviews at the outset of a project. So, you know, from the Zen source side we'll partner with our agency on the development side and figure out with our clients, you know, what are the needs of the business. We're going to create prioritized business requirements and function requirements. We're going to do a tech roadmap of what it looks like now versus three or five years down the road. We're going to collaborate with marketing and IT, identify all the integrations, make sure we're thinking about what we're going to do now, how it needs to scale in the future, but I think even more importantly, what we really want to do are identify opportunities. How do we uncover pain points, you know, features that are error prone, things in the current system, whether it's an older iteration in Drupal or another platform, what's not flexible, what's not working, and we want to identify the quick wins but also the longer term enhancements that are going to save us time and make the author experience that much better. And then what we really do is we understand the needs of the authors. So diving into their workflows, I don't just mean Drupal permission in a workflow and roles and things like that, but I mean like their day-to-day workflow. You know, what else do they have on their plate? What does their day look like? How much time do they spend in the CMS? Are they a small centralized team that develops all their content? Are they a bigger decentralized team that has more authors in there doing just very specific things, whether it's just updating like news or events or something like that, or really trying to figure out what their different touch points are? How many cycles or reviews do they have? Who needs to approve certain things? Working with an education client right now where they have a core team that does the content writing, but then they have five or six different layers of review and approval before it gets published out. So identifying what that end-to-end journey looks like and building the tools that are going to streamline that, make it easy, incredibly important. And then looking at those friction points and figuring out how we can remove them as we do a new implementation. So how we tend to approach that and how we encourage our clients to collaborate with us and with our agency partners is to onboard and bring authors up to speed early. So we encourage one-on-one training at the latest Drupal admin in the code base that's going to be used. So something we'll often do with clients too and maybe we are a year away from a site redesign but there's an opportunity to get some new marketing landing pages and market now. Try some new creative, getting used to the Drupal 9 interface, getting used to our code base. It gives us a lot of opportunity early on to figure out what works, what doesn't work, what can we optimize for the bigger redesign. And it gets authors familiar with the tools before we get into our detailed training. And then we build up these requirements together. So it's the functional requirements but those CMS experience requirements, we sit down with our clients and we go through layout by layout, module by module, how is this going to work? What's there by default? What are the field labels? What's on the page when we create a new one? How easily can we clone things? All those different types of pieces and then diving into their permissions model. How are they going to maintain site governance? All those things we do with our clients. So kind of getting back to how that ties back in terms of the proposal piece. I think making sure that as the partner where guiding our clients and recommending this approach to really make them feel comfortable with the tools we're building. But then from the client side, making sure that we're asking our potential partners about this and we're factoring the time and the budget and the resources to really deep dive into this throughout that design process is really key. Content migration process. So as I mentioned a few moments ago, and I'm sure a lot of us have been through this more than a few times, but the content migration process is super time intensive and super resource intensive. But when done right, it's the difference between launching on time and on budget and not. We believe that it should be a mix of automated effort and manual effort. So I think if a vendor says, we can do 100% manual migration, they're probably not investing the time in the tools for things like using the Drupal Migrate API. There are plenty of things that we should be able to script and migrate over and not rely on authors to do. But at the same time, any vendor that says it's got to be 100% automated, probably will have reasons down the road why it can't or why there's issues. So from our perspective, finding the right mix of what needs to be manually migrated and what we can automate to have the integrity of that content be the best that it can be is the right way to go. That's usually what we recommend to clients in the RFP process when we talk through that in the pitches. But we also, coming from the client side, really recommend that. Really pressure testing that with your potential partner and really deep diving into how they're going to handle migration is probably one of the most important things for success. So how do we do that? I think ensuring that your development partner is thinking about efficiency of automation but being realistic about the road ahead. We really encourage clients to dig into the approach of content strategy. How do they go about it? Analyze how they execute the automated migration but also their process to clean it up. Training and implementation is huge. We have, whether it be a web app, an enterprise level, health system, whatever it is if you were to ask us for what does a training program look like give us the hour by hour over a week or two week training, how do you approach it? That should be something that the vendor can provide and walk through pretty easily. That should all be really canned and really determined up front. But how we approach it is we do a mix of working with our agencies on the content strategy side as well as the trainer side. So this picture here on the right is actually a picture of one of our clients, Cornell University College of Agriculture and Life Science a few years back we did a redesign for them and with our agency partner, Primacy and this process you're seeing on the screen is before we even got to training it was printing out these huge comps and cutting out modules and the Primacy content strategy team went through and worked with them to figure out how to develop content how to map content, how to put together the modules before we even got into training. And then once we got into training the ZenSource team came in and we helped them go through the curriculum but using that real content not just standing in front of a room of people going through a deck of how to edit in Drupal but really rolling up our sleeves working sessions side by side building out real pages together we find that that is the recipe for success and ensuring that that's part of the process that's part of the flow of the time and the people to do that is really going to help so you know kind of in short whether the vendor has a dedicated team helping you populate all your pages or strategists they're going to help organize or both having some level of that in there is just going to make that migration go that much smoother and just the integrity of the build. Jake I will hand it over to you to talk a little bit about the next piece so these next sections are covering just some of the issues we run into with the large sites or basically non-standard sites where there's a lot more going into them than just the average sites so a lot of times yeah you run into this with you know hospitals continuing care education, social where they've got a lot of either data coming in from multiple different systems they have multiple departments that might want their own permissions their own ecosystem within the content management system or just even like multi-lingual things where the normal approaches don't always translate very well so there's definitely I mean again a lot of modules out there but it's a good to know whether the vendors already vetted these are going to work with that particular approach also in the case where say custom development is needed if they're familiar enough with whatever the API available for the set of modules they're using to actually you know bring that to fruition so yeah as it says here you want to make sure that the whatever solution they're offering is tested to scale up to the enterprise level but also without necessarily locking you into any proprietary functionality so down here we can discuss some of the things that we just run into John touched on some of these briefly but just making sure that they are up on their compliance especially if any there's going to be any personal information or PII stored on the website you want to make sure that they're developing these solutions to scale and what that I mean there is both in the form of upgrade paths but also making sure that the solutions that are working for once you've populated 10 pages are also working if you're publishing say 500 pages you want to make sure that whatever solution they're doing is flexible enough and that it's designed to integrate well with a lot of the other community modules available sometimes we run into where a solution might work fine in certain cases but then when you start adding workflow or visions on top of it things start to get a little tricky and then what we'll touch on more in a second is importing and managing any say external data and that kind of goes back to content migration piece with the external data so while the content migration of the actual site content the page content is so time intensive and consuming also really vetting that where the client's data is coming from is it coming from proprietary database are there things that we're designing that don't live in that data and needs to be co-mingled in Drupal how do we marry that data together and have it all display and work perfectly on the site both the third party and the Drupal specific we just had a case with the client where they have data coming from a third party feed but also want to be able to create the exact same looking content in Drupal but it's just more you know more personalized kind of more on the flow of their tone and voice but being able to really vetting a vendor to make sure that they have the approaches to bring in data and display it and have it work from a lot of different places we find next to the overall content migration is probably one of the more time consuming parts and one of the gotchas you really want to make sure your chosen partner really has a really good way to vet that and execute. And just to get into some specific questions that we like to ask or that we see asked common again in the process of data are they familiar with things like Migrate API or feeds this goes beyond even just migrating data from the existing website but most large sites that we work with such as health care providers they'll have say like provider data coming in from their credentialing system and need to run on a schedule and that needs to continue well past the initial site development usually daily the other big one as far as scalability is what sort of caching system that they've worked with if they've used their solutions tend to offer memcache redis obviously if you're going with like one of the the more like well-known hosting providers like an aqua or pantheon those tend to be documented well but if you're going with you know more of a custom provider just make sure that they've worked these into their solutions and specifically when we're talking about things like varnish if they don't go with varnish or one of the other like well-known ones make sure that their caching solution is supporting what's called tag-based expiration and what that means is a lot of solutions will when a content author is updating a page it'll be smart enough to expire that one URL but without the cach sorry without the tag-based caching they don't have the ability to expire anywhere where that page is used so you start running into issues where if your site is embedding articles used on other parts of the site into it those will be out of date from the main article and that's what tag-based caching gets you around and then another big one with larger sites are just any SEL implications so you know I'm sure everyone's throwing the metatag module on as just a default but there's also a big push to start getting data schema or JSON-LD functionality added on top of that it's great if whatever vendor you're going with has already come up with a lot of default values so that the content author doesn't necessarily have to fill out specific fields but it can say you know populate based on summary of the body text or title or maybe like a hero image depending on if you're using like say twitter tags and then another big one is when it comes to redirects do they have they implemented a large scale way to say import those redirects and then also handle them in a performant manner which usually we try to move it as far up the stack as possible the redirect module is very good for doing like vanity URLs or small amounts of redirects but doing it directly in PHP is going to be more performant than that and then doing it in Apache is more performant still because the redirects are happening now before they even reach your Drupal site and so the other big piece is specifically with the hosting aspects of it so one thing is to find out what they're actually offering as far as going with to white label so a lot of places use AWS these days or Azure preferably they'd be on some sort of cloud based solution but even if they're not just make sure that they have the staff on site and what their turnaround times are for troubleshooting issues same thing with their model security do they have any guaranteed uptime response times do they have their own automated monitoring tools at hand to show site uptime and in some cases can they make these available to you and it explore the other piece too would be more on the security aspect is how are they keeping the data safe do they have encryption at rest encryption in transit do they have good auditing as far as who has access to your data certainly for the ones that are white labeling say AWS AWS has certain guarantees up to a point but it still is onto the vendors implementing these to have their own layers of security on top of that and then as I mentioned above see what kind of encryption they have available if it's just at rest or if it's in transit as well or maybe something on top of that say with web form encryptions so the other big piece is the support aspect of it so the site can be perfectly up to date when it launches but then you know quickly you know within a week or two we'll start falling out of compliance depending on if their security updates available so see if your vendor offers like some sort of support package to keep everything up to date and if they do offer that package you what how far do they go in covering that and so if the do they run updates and then if there's issues that's then put on your team to solve or are they actively monitoring a lot of the core modules that they're using in their sites to see like you know when new updates are coming out or any known issues it really like find out if they're capable of diving into like solve problems or if that's just not necessarily covered and also if upgrades are offered how far those go if they're just minor versions say like nine three to nine four or will they actually cover larger version updates as well you know I don't think you'll find anyone that covers say seven to eight but for sites that are already built on eight the upgrade process tend to be smoother and so that's not as unrealistic so they yes that here because it is so critical make sure to factor that into whatever budget that you have for the project we'll talk more about this in a second but as far as one click updates they're very good for what they are but don't necessarily assume that every aspect of the site is going to be covered by it and if they're they do have a lot of automated testing what's their process for actually releasing these updates is there like human element to reviewing these updates to make sure that the site isn't in an error state after they've done applying them or you know is that on your team to basically review the updates before they're pushed out so some specific questions you can ask as far as hosting if they're not using one of the mainstream environments they should be able to provide audits like SOC2 and get you any sort of information on an architecture diagram to see where the firewalls are in place how access is obtained how you're expected to get say SSH access or FTP access to work at the file system and if they do offer firewall what types of things are they checking for does that cover DDoS protection things of that nature so in the case of like support packages the one click updates again they work very well for small websites but when you start getting to larger scale websites what we tend to find is that a lot of them don't necessarily support Composer very well or if they do cover updates they only cover core and only then if there's no patches being used on the website so just get into the specifics of what is and what isn't covered just so you're not surprised post launch and then if the vendor is offering any sort of proprietary based tools that sit on top of Drupal just find out exactly what Bryce was mentioning in his keynote earlier is who owns the data at that point some of those tools are very smooth for the editing experience but then if you stop paying for your subscription you're essentially locked out of updating the site after that and so it really needs to be like a pro con analysis of whether they're smooth enough to justify potentially losing some level of ownership to the data and take this last part just to close before we take any questions you might have from the client perspective really understanding your partner from the development side from platform, Drupal platform side what's the special sauce they bring to the table and for those of us on the site builder and platform side what is it that we offer what can we bring, what sets us apart in the pitch process, in that whole RFP process and when we're competing against other agencies and platforms and what makes you truly special if you're a development partner on the Drupal side, Drupal platform you're going to take advantage of the community for the client's benefit but devote resources to making that unique experience if you're considering Drupal or have already committed to it it's likely because you expect certain things to come standard but are also excited about the flexibility that we have that we don't always get with Enterprise and make sure your partner is prepared to not only leverage Drupal to accelerate the build but also bring tools and strategies to really build out that technical roadmap for us at ZenSource we saw years ago that more and more clients are moving to Drupal every day again, Dreyas spoke about this at length this morning but across healthcare, across education across these more enterprise huge ecosystems more and more clients we're seeing are asking for it every single day and ZenSource decided at one point let's look at building a front end and back end experience design system something that we can install and it has all the foundational UI modules and page layouts and forms and site search and whether it's a really small build or a really large build using the client's budget and their time and their resources to do what's really custom unique to their brand is what it's about and that for us is kind of having those foundational UX accelerators is what we think we tell our clients as well and for those of you looking for different vendors on the client side are also those of you who are site builders and work for particular platform or software company trying to really unearth the value prop and what's unique to your brand and what's going to set you apart from other potential competitors that's what we really want to convey and try to find harmony with our clients so you can visit us at ZenSource.cloud for more information or to learn more about our products or hosting our core support our experience platforms and you can reach out to Jake and I anytime we love the chat we love to meet talk about your business talk about what challenges you have or what solutions you offer we love to partner, we love to collaborate so please feel free to contact us anytime any questions we can answer anything sure hello I need a mic I'm Laurent from Total Energies so as clients I have an itchy question for you is sometimes we're in a situation where our vendor deliver and we realize the penalties we will not solve the issue and I would like to have your feedback from your perspective did you meet unfair penalties during a project or do you have some suggestions how to for us to write better penalties that is win-win so there's a question more around in the case the site was built implemented by internal IT in maintaining the site or is it more the requirements it's like the way the contract is written and so basically in case of usually the penalties are delays the delivery is late because it's too too many critical bugs so in these cases the next bill will be lowered by this percentage so but when we write an RFP this is the point where we can fix that or improve this part so it's we don't meet this great question a couple different ways we've looked at it what we often encourage clients to do with the RFP process is to write in a warranty period really having a certain set amount of time developer hours a certain criteria whether it's 36 days after go live where they have to fix anything that's deemed critical writing in assumptions like anything that's deemed critical priority one functional display and then also what we often do is work to build an assumptions that you know in order to meet scope all the requirements in the business requirements the bill reference guide whatever you call it the product playbook have to be met so before we can consider it a true handoff having the assumptions in place in the RFP process of final sign off on requirements and the work is not done until these requirements are done tickets, issues, bugs, etc you know must be complete and then from that perspective writing in that warranty period of how long they have to fix those bugs and what success looks like we find that's the best way to do it because if we don't get to the bottom of those assumptions when the site goes live what does success look like like to your point maybe there's you know things that you think are critical that the partner doesn't think are critical or vice versa so making sure that there's ample time beyond go live and a certain expectation of delivery and time of delivery the more assumptions up front the better the more clear we are with the scope and what's in and what's out and not leaving it to be you know vague in terms of what those requirements are that's always what seems to work best for us and it's best for our client and it's best for the vendor to be really clear and transparent that's where we've been I would say too it's good to work in assumptions on adding in like various review checkpoints during the project so versus say having like the finalized solution delivered all at once you're preferably like the vendor can start getting you into the system maybe necessarily before the entire sites finish but just early enough that you can still see the content structure and maybe some key elements of it to catch these sort of issues early in the build process which makes a lot cheaper to you know pivot at that point if there's just more of a not so much that they're not me the requirements but maybe there's just a misunderstanding of exactly you know what the requirement was you can catch that kind of stuff you know much earlier in the process yeah that's that's actually really important one we often will work to put in certain you know deliverable milestones in the RFP and that's a great one like what we like to do is release you know a homepage three layouts and ten modules first and if that's good we move on if it's not what's the feedback then in the next release okay we make those improvements make those revisions release the next batch the product's better it's more tailor requirements and you're not getting this huge delivery that you're stuck with at the end that's too late to fix or out of time to out of money so those iterative releases to you know to staging before we go live we find the clients are always a lot happier with the product when we do it that way we're a little bit more iterative and transparent hmm I see and maybe I have an advice for the for the audience is like it's always easier to make a contract with the when it's fixed price better determine the means like with allocated means rather than always focus on the results like because the result is always as you said assumptions by for what the size of the team the experts at that at that time and that can create a lot of issues after if you say I'm not happy with the results but it was based on assumptions from the from the quotes and if it's fixed bid and there's an assumption that those things need to be met within that fixed bid scope versus it took us a lot longer than we thought and you know it's really another $50,000 change order for this feature because we underestimated it another thing we do that really helps is try to do statements of work for discovery through user experience and then estimate the build after the more opportunity you have to go through that strategy go through the requirements go through user experience concepts and then have a range for the build and have those really focus requirements and wireframes to develop the build budget that always ends up being a lot easier as well because it's so much more accurate at that point versus trying to make assumptions up front that you might not know thank you if we were in the ideal world which documentation would you expect from the customer site to start a website or how customer can better prepare to that process number one will always be thorough documented third party integration documentation apis proprietary databases that data whenever we have more documentation around any data or homegrown proprietary apis you might have that's always going to be the best because when we get into doing an integration and we know there's some database over here and there's some random X and L feed and we'll create a job and import it when it's more ambiguous that's where we budget the fastest and the more documentation and production ready you know apis we have up front is definitely going to be the best way to do it. Yeah I'd say like the second probably after that when the second most important is this will probably be shortly after the RFP process but if it's possible to give your vendor access to say like maybe a staging environment that you have so they can actually log into the system to see how the data is structured see what modules are being used things that you might not necessarily think of in a vacuum but they'll be looking for based on the type of project that they're doing. Hi I've come across this issue a couple of times recently and so a client approaches us and says well they'd like to have a project done, relaunch or whatever and one of my first questions is well can you also send me some of your internal documentation of your workflows how do you author content how do you do things they don't have it how do you deal with this type of situation where there's very little documentation that the client could provide to you so you understand the workflows. Yeah that goes back to what we call the product playbook whereas part of our discovery the stakeholder interviews we meet with the authors because that's one piece that more times than not is not documented there's not time there's not resources to do that but what we do is we'll sit down with the authoring team usually it's the core marketing team and as we develop the functional requirements the CMS experience requirements we'll work through the current workflow what are the authors doing the review the review process how are they publishing all the different pieces so that's where we'll factor in time and budget up front to understand and document what the current process is because you're right it more times than not is not there but we need to understand that so we have a couple more questions what tools to use by agency for workshops and scoping the project with the customer what are the most expected formats of artifacts for selection process as the answer to the RFP can you say the first part of it again what tools to use by agency for workshops and scoping the project with the customer maybe they're thinking more like some of the UX tools like freehand yeah so one of the projects things we use a lot are things like like Miro we'll often do workshops with our clients up front using something like Miro or something like a freehand where we'll do interactive workshops together to sketch out what's in their ecosystem start doing some low fidelity wire framing that kind of a thing that's what we find especially with all of us being remote these days more of like that interactive whiteboard Miro is a product we have a lot of success with and we use that quite often to help scope and kind of help understand requirements before we get into the build that in my opinion is probably the best one the other one is what to look for in vendor or RFP when our policy requires that site to be hosted internally yeah that's a really great question we run inside all the time I think that goes back to and Jake I'll differ you on this one a little bit but I think that's where it's really important for your development partner to have expertise in their own security teams they have their own information security officer that's going to help work with your IT team to make sure things are within compliance that we're doing best practice for data encryption and how we store past data I think having even if you're not hosting, if your development partner isn't hosting but having hosting capabilities and understanding the configuration how to troubleshoot different server configurations that's really important because when it comes to systems if IT's supporting I think the more that we can do to help support them Jake probably having a shared repo that we all have access to that kind of a thing I don't know if you have any other thoughts on that shared repo is definitely a big one a lot of issues we have we've run into in the past is where vendor has their copy of the source code the client might have theirs and the processes may be able to sync those up centralized one if you can but also as far as hosting internally goes too, I'd want to spell out where where the vendors support ends and yours begins so does the vendor just troubleshoot site code, will they troubleshoot actual environmental issues that might come up on your server will you be maintaining the server updates, security updates or will the vendor and frankly are you able to give the level of access if you do want them to support it to have access to those servers to do it themselves or is it assumed that you have staff on hand that can handle deployments and the update process and work with the vendor to get those updates out there I think we have one more question so it's for gen source is it possible to migrate from gen source to own hosting at some point and use it without the subscription yeah 100% that's actually you know that's our business model by design so gen source we have our own distribution design system but it's all entirely built on Drupal built on open source we have subscriptions for hosting and for our support and our upgrades we do have certain standalone host experience things for things like landing pages a lot of our clients host externally in support externally whether it be on prem, aquia, pantheon whatever it is at our core it's a code base the whole idea is that we don't have anything that you can't walk away from but there are certain things that are value add like the support and like the hosting that's more subscription based but everything is you know totally you own it and can move with it so what we do with a lot of our agency partners is they you know download our design system in our code base we have full control to go and use that to build any implementation they want for any client and host it anywhere so that's really where we are at our core but happy to give anybody a demo or talk through it more next week or whatever and we're in the process of getting the distribution actually posted to Drupal.org just haven't gotten there yet but hopefully by the end of the year we plan on getting everything cleaned up enough to get posted to the community see you in time but thank you everybody thank you guys