Local Jungle - Current

Speaker 1: Good morning.

Speaker 2: You've seen me without coffee. You don't want me without coffee.

Speaker 1: I guess last, I think last week might have been actually a coffeeless day, if I remember correctly.

Speaker 2: Yeah, it's not productive at all.

Speaker 1: Did you survive yesterday?

Speaker 2: I did, I did. It's been hectic all week. I don't even know why. Yeah, I do. I don't know why I'm saying that. So Tuesday, the reason I was out of office is because we bought a house. We had a home inspector inspection. Can't talk yet. Anyway, that two hour window threw off my entire week. It's been insane.

Speaker 1: Yeah, that's what happens. It sucks. I actually had on Tuesday, given that we didn't meet, I actually, you let me know early enough to where I actually didn't have any meetings that day. And I blocked off the whole day and it was,.

Speaker 2: You gotta get, you got caught up.

Speaker 1: I did. I legitimately, I did because my wife and I are gonna go out of town this afternoon actually and we're just gonna go to the mountains and hang out and whatnot. And so I had like three major projects that needed to get to a milestone and I just sat down on Tuesday and just. And it was good. It was really, really good. And so I feel fantastic leaving at 2pm today. So I have a couple of fun projects that I'm gonna work on for myself while we're at the cabin because I don't have time to work on my fun things and my fun things are relaxing. They feel like work, but they're not. They're fun. I actually want to show you something at some point today. I don't want to spend more than like three and a half minutes on it, but I'm so excited about it. I have to shy. I think you'll like it and I, I, I just want to show it. So that will happen at some point Today I do have a hard stop at the top of the hour because I do have a meeting at 11am Eastern time.

Speaker 2: So same, I have my meeting, my weekly meeting with the web developers and I'm at a point where I want to fire them like so, so, so, so bad.

Speaker 1: You said that two months ago too though.

Speaker 2: I know, but it's gotten worse. Actually, let me say this. You're the one that pushed Marco, right?

Speaker 1: I think I'm the one that introduced Marker. Yes.

Speaker 2: Okay.

Speaker 1: Yeah.

Speaker 2: So let me share my screen with you. This website I just looked, they have clocked a hundred hours until. Which is inexcusable because it was a template almost Already done. Anyway, so I don't even understand how it was 100 hours. But here is the description. Please picture Bob with pictures Sammy, shop dog. And then, yeah, so just, hey, replace this picture with the shop dog. And I thought I had. I gave them the description somewhere. Oh, right here. I don't know. I gave them a description, and that's just on the home page, right? So I come down here and look and I'm like, okay, bomb stuff is on here. That's whatever. On a whole different page, on, like, the whole team page. With as long as how this guy is such a skilled technician. They replace the picture on this page too. I'm like, okay, we're not in elementary school. I don't care if you're overseas or not. This is just logic. What the hell are we doing here? Here? And I understand it, it could be communication or whatever. But it's not like we just started working with them. They know what I mean. And it's just like stupid mistakes like this that drive me up a wall. So I started this point, I looked at this because this site is supposed to go live tomorrow, and yeah, it's absolute garbage. And then the page speed, I'm not gonna go too far into this, but they know our page speed requirements are so important to us. This is gonna take a second, but the page feed, I'll look again here in a minute. Is not great. It's like in the 70s.

Speaker 1: But why would that be? If they're using a template, why would it be.

Speaker 2: Because they try to take the easy way out. And Craig has been, I want to say, at least 100 hours trying to figure out what is happening with our page speed. He's working with another senior developer right now that he's worked with for a long time. They're going through all the plugins. They're trying to make a perfect tech stack with the perfect settings with the perfect everything to make sure that it's actually hard to screw up. But right now they will do, like, the stupid stuff where they'll try to get fake page feeds. What I mean by that is like Callvail, they will try to hide it for a certain period of time. So our page speed insights, it won't show it loading, and it will load the page. And then when you start interacting with page or whatever, that's what it shows.

Speaker 1: Okay.

Speaker 2: Oh, look, it went up. It's 80. I mean, this is passable. This is passable, but not great. That's. I don't know. It's just some of the things.

Speaker 1: Because all they're doing is uploading content. Like all the dev teams uploading content is putting images in at the end of the day.

Speaker 2: Yep. So there might be like a couple sections I have them build. Like, I had them rebuild their section. This was like the original coupon section that actually had them pull off the home page for this client because he didn't really like the coupons being right there. So now the coupons are on the actual SEO pages.

Speaker 1: Gotcha.

Speaker 2: But like, it's not like he. I don't understand. And that's why Craig's getting so pissed off. And he's really irritated with the whole page speed thing in general. And the developer he's working with, he's very much into WordPress. He understands page speed really, really well. They're trying to figure it out, but every day it's just like, we need to get to Astro. We need to get Astro. So there's no chance to be like fixing anything until page speed issues fixed. So that's a little frustration. I won't communicate with you.

Speaker 1: Go to the PSI thing. I'm just scared. Go to the Google psi. Scroll down to the like. Okay, those aren't. Those aren't bad.

Speaker 2: This is the big issue. So this site, they actually fixed this a little bit. Like the first contour. Full paint is great. Total blocking time. Whatever. But then the LCP is always so big and I don't know why. Force reflow.

Speaker 1: Go down to the next, like whole section. No, I actually could go. Go back up a little. Okay. Identifier css. So those are all yellow. Okay. Go to the next.

Speaker 2: These I feel like are really easy fix is like you can go upload the CSS and do like a minifier thing.

Speaker 1: Yeah. But you don't want. You don't want to do that manually. You want that to be automated. Because if you do that, if you're basically saying as a part of the dev process, go and grab your style css, shove it into a minifier, then copy and paste it back in. Like, nobody is going to do that.

Speaker 2: Is it that plugin that does that?

Speaker 1: The log into the back end of. Can you log into the back end of the site that we're. That we're fussing about?

Speaker 2: I know a better way. I know logging into WP admin is probably easier, but this is just. Everything's all in one place.

Speaker 1: Found me.

Speaker 2: You. Do you. I don't think the website should take haunted hours. That insane. That's like custom website time.

Speaker 1: More than that.

Speaker 2: Yeah.

Speaker 1: But it, it very, very much it depends.

Speaker 2: Well, this is. Okay, the 100 hours. To be very, very, very specific about that. 100 Hours. That's actually working on tasks. That's not design, that's not anything like that. That's. Hey, here's all your stuff. Go do it. That's the hours I'm talking about. About. So all together we probably 150 hours on this.

Speaker 1: I mean I think that's probably too much based on everything I know about you guys. But I also know how many. There's a lot of moving pieces with content and images and all that kind of fun stuff. Go to plugins. I just want to see the list of plugins.

Speaker 2: Okay.

Speaker 1: Can you zoom in a couple of clicks for me?

Speaker 2: Yeah, there we go.

Speaker 1: Let me actually zoom in this. Okay, here we go. So we have art direction response.

Speaker 2: I have no idea what this is.

Speaker 1: That's why that's a common. The anti. It's a. It's anything that's deactivated. It's fine.

Speaker 2: Oh wait. Okay. So yeah, yeah, our direction.

Speaker 1: I have no idea what that is.

Speaker 2: That's not a poop plugin.

Speaker 1: Better search and replace. That's fine. Gravity Forms is fine. Imagify is. I've also heard of imgify. That's fine.

Speaker 2: That automatically optimizes the images on that. It doesn't look great, I don't think.

Speaker 1: Oh, it doesn't. Okay. I have.

Speaker 2: I don't.

Speaker 1: All the custom local jungle plugins. Those are all fine. In general, I. Based on what I know about those. Those aren't really adding any actual bloat. Like it's. It's all back end stuff. Make it easy. Pop up probably adds front end code because it's a pop up manager.

Speaker 2: If I had this. Again, we're running into the same issue where they're just adding a whole bunch of shit to the plugin. I need to look at this more often because we have a list of approved plugins and none of these are on there.

Speaker 1: So I don't know what widgets for Google. I mean, I know, I understand what widgets for Google Reviews does, but I know that, I mean if you're dynamically pulling in Google Reviews, that's definitely gonna be a front end. That's gonna be a front end thing.

Speaker 2: Yeah, we have Trust Index. That shouldn't even be on here.

Speaker 1: Oh yeah. Yes. Also wait a second. Yeah, you definitely need workfence. So you have something called Security Optimizer. Oh, that's the site.

Speaker 2: Oh, this is by Choice index. This is just the new. They shouldn't even be doing this though, because they're supposed to be adding the. Whatever. I don't care, honestly. It's just Index.

Speaker 1: WP Rocket's fine. Honestly. A lot of these plugins are. Okay. The Yoast duplicate post. I. I'm not a fan of duplicate post plugins just because I feel like they're dumb and you can just copy and paste stuff. But I also know that you're dealing with content at scale, so I'm assuming that's all back in. So it probably doesn't matter.

Speaker 2: Why does he have that? Is that because the. Oh, that's why they're lazy and they don't want to copy the blogs.

Speaker 1: But also like the. The duplicate plot. Like the duplicate posting. But like, that's not. That shouldn't add anything to the front end that should not impact page speed. So it also looks like you this. Like if you go back to plugins, I think that SiteGround plugin. Security Optimizer. I think it does. Oh, yes. Scroll up to. There you go. So, yeah, Security Optimizer. Then you also have Speed Optimizer. Yep, Speed Optimizer. I don't. I mean, I. I understand.

Speaker 2: Which I don't understand why we have that. Because we have WP Rocket.

Speaker 1: It probably is automatically installed because it's a. It's probably automatically installed because of the siteground thing, if I had to guess.

Speaker 2: No,.

Speaker 1: I mean, it's not under the must use plugins, which is where.

Speaker 2: No, you're probably right.

Speaker 1: But you could. I mean, it's d. It. You're able to deactivate it. But I also don't know. I don't know enough about siteground to know how important it actually is.

Speaker 2: So. And that's another thing that we're trying to get off of. We're trying to go over to rocket.net yes. We just gotta figure out page speed first. So yeah, that's the frustrations. Right now go to.

Speaker 1: Go to the Tools tab really quick for me. I think it's on the Tools. Yeah, go to Tool. Oh, nope, it's actually not. Go to Hover over Settings. WP Rocket at the bottom. Go to File on the left hand sidebar that Go to File optimization. So okay, we're just do like a slow scroll. I'm looking at the check boxes. So Minify CSS checked. Optimize CSS delivery. Check should not be removed.

Speaker 2: Okay.

Speaker 1: Yeah, Minify. Okay, that's fine.

Speaker 2: Oh, this.

Speaker 1: Oh, remove. Removes unused CSS per page. Safe list of Sci Fi should not be removed. Yeah. So basically it wants it. Yeah. That's all. That's all fine. JavaScript file, minify them, load JavaScript. That's all fine.

Speaker 2: Isn't this what I'm talking about with the.

Speaker 1: Not specifically, no. Like what. I think what is probably happening, there might be some custom code written that literally says wait five seconds before long. Deferred loading is a little bit different. It's not. It's not the same basic. This is the simple version of deferred loading. Don't take this to the bank. But basically what deferred loading means is once the entire like document is loaded, then immediately load the JavaScript. Whereas what you said is it was on a delay.

Speaker 2: Yeah.

Speaker 1: Like a timer. Now you. And my assumption is you'd have to write custom code to put it on a timer.

Speaker 2: Yeah. That's how old developer he got fed up with Craig and his page speed stuff. This is like a really important thing to Craig. And I thought it was. Honestly, at first I was just like playing along, like, okay, yeah, I work for you, I'll do whatever you want. And he showed me the actual difference that 8090 makes on our ads. And it's insane. It's literally almost a 5, 10 difference on our ad conversions just by that 10, 10 points in page speed.

Speaker 1: That's nuts.

Speaker 2: And I've never seen that in any other industry before ever. So the fact that you showed me that data, I'm like all on board about it now, so. And specifically how we. It translates to dollars we earn due to how we bill. So our old developer, he would just get fed up because he's very much developer. He has his blinders on. He doesn't care about anything else except building this. Right. And then with Craig's page feed stuff, he would go and custom code all that and he would just try to make page speed insights look good.

Speaker 1: So interesting. I. Nothing in here says nothing in this list here screams bad to me.

Speaker 2: Yeah.

Speaker 1: Now in the plugins, there's a couple in there that actually go hover over speed. Opt on the left hand, black sidebar. Hover over speed optimizer.

Speaker 2: I don't think we actually use this. I think this is the one that's going to be removed. It's.

Speaker 1: So yeah, this is the one.

Speaker 2: Yeah. Part of our issue is this overlaps with WP Rocket, which overlaps with one more tool. And that's what Craig was like working on is like the settings between each so they don't conflict. I am likely going to Remove this.

Speaker 1: And I don't know if that's going to help at all. But when you have two plugins doing the same thing, it's not necessarily a great idea.

Speaker 2: So it conflicts. We already know that. But Craig's the one that goes on that page speed things, so I'll let him do that.

Speaker 1: Have you all tried just taking one of these basically full blown like this is a full blown website at this point?

Speaker 2: Yes.

Speaker 1: And migrating this full blown website to just a different server and running a page speed test on a staging server on another host.

Speaker 2: On another host, yes. So that's where Rocket.net came into play. We never finished that out to be honest. But we were going to do. I forgot what site it was. Oh, I know.

Speaker 1: Because I'm kind of curious if you took this site as is this one.

Speaker 2: We took this site. We had to finish some things that. I never finished this out. But while we were building this out, what I did is I took this over to Rocket.net and there was an immediate difference. However, rocket. Net is really weird. We didn't make the decision on moving over quite yet because what happened is we move this over on siteground. We were sitting at about a. I want to say a 70. Yeah, it was about 70. I moved it over to Rocket.net on cash. So it was 70 and then 64. So 70 was cash. 64 Was non cache for Rocket.net cast was 90, like 4 or 95. That was on mobile and desktop. However non cast was 52.

Speaker 1: I mean now the likelihood of showing a non cache page is very, very, very slim.

Speaker 2: And that's. You're using a lot of UTMs and things like that. So we have to take that.

Speaker 1: I didn't think about that actually because every UTM is going to be slightly different based on.

Speaker 2: Ah, then we. That took us back to the page speed thing and we are excluding or we're including caching basically. They're doing something. I don't know. This is where it gets over my head. They're doing something where the UTMs, even if it is customized, it's going to be cached. Hitting a cache version somehow some way it like 90 of the time. But that other 10% needs to. We gotta do something with the page speed.

Speaker 1: Interesting. Okay.

Speaker 2: And that's where ASO comes into play. Astro only delivers the cached version regardless. That's. I don't know the technical workings but that's why Craig's so focused on switching over to Astro because it will 100 delivered cash. Huh. Okay, so yeah, that, that's just to catch you up with what we've done.

Speaker 1: Be something interesting.

Speaker 2: So where we're at now is I don't like E2. We're going to keep them on. In the meantime because I don't want to switch a bunch of things. We're attaching our process. So as of yesterday, we began onboarding two new clients. We're kind of sprinkling them in before we open up the firehouse. We have one that is an existing client, but we'll be doing the whole website. So we'll be onboarding them to test our process. And then we accepted one new client to test our process as well. All the changes that we made were now tested.

Speaker 1: Can I go ahead and send you over the course the core plugin so that you can use it on this new one?

Speaker 2: Yes. I still gotta play with it and then I still have to get approval with Craig to do that.

Speaker 1: So it's basic. It's, it's as done as it's going to be for now. There's other things we can add into it later. But the only thing I don't have in here is just the, your actual like, honest to God iframes for the like location modal boxes. So on that note, let's look at this, shall we?

Speaker 2: Yep.

Speaker 1: So I'm sharing my screen. I think I just kicked you off of sharing screen.

Speaker 2: Oh, I, I. Okay, cool.

Speaker 1: Awesome. So we've gone over all the coupons, so none of that's changed.

Speaker 2: So.

Speaker 1: In the let me move, you know, your face over here under a single location, you can now drag and drop blocks as well. So your location pages can actually be built out with content. We have our address, phone numbers, Google maps, scheduling, iFrame, etc. We got the email routings for the, the coupons here as well too. That's all, most of that is all the same as it was before at the block level. I'm going to quickly go over the things we've already went over just for kicks and giggles. We have the custom block called Nav Locations which is dynamic. So if it's not on a single location page, it'll show all the location names. It's only on one location. It'll only show, It'll only show that address nav times. It'll show one of the locations times. In this install, I have separate times for both locations just because I just wanted to see if everything toggled correctly. In the actual navigation bar, we have a, we have a call to action section. So it's the NAV CTA and that combines all of this stuff here together. So if you're on a multi location spot, not a specific location, it's going to show Schedule Online and you can then select which of these you want. But then we'll also show the city name and the phone number that is clickable over here. That is all this is all one magic block. And then if you're on a single location, it only shows Schedule appointment with the phone number as the cta. So all that's handled dynamically in that one single block. Then we have a custom block called the Schedule Online block. All this outputs is the Schedule Online button. If you are on a single location page, it'll just say Schedule Online and it'll pop open the the modal box. If you're on a non location page it will show a drop down very similar to the Schedule Online thing over here to where you'll then pick your location first and then the pop up will show up. And I have just YouTube videos on here for right now as the embed codes. Then over here we have the all location info block which will always show all location information broken up by address, phone and hours. And then in this, this actually does have a custom field where you can toggle it between showing it in a column layout versus rows. And so here it's not going to show that in the editor very well, but you can then switch that. So if you wanted to try use this block on an actual content page and drop it in the middle of the content, you could do a column layout there. Then lastly went ahead and added the where's the footer? We didn't talk about this, but this felt smart. So I did a smart thing.

Speaker 2: So that's what I want my developers to do.

Speaker 1: I made a locations grid block that has no custom fields to it. But this is meant for the footer. You could hypothetically use it wherever the heck you want. And what it will do is it outputs a two column grid of location information in small text. And so if it's only one location, it just shows the location name. With all of this spanning up question,.

Speaker 2: Let's say just hypothetically we go on and take a client with like 20 different shots, right?

Speaker 1: We need to reconsider some of these things.

Speaker 2: Okay. We built it for the normal case and then when those things come up we'll, we'll do something effect because we.

Speaker 1: Can, because we would, all we would do is we would just edit the existing blocks. We basically go into all the Blocks and say when we would. We would probably set what we would probably do at the, like at the plugin settings level, we would probably have a. A field here that says like max locations.

Speaker 2: Yep.

Speaker 1: And. And if the number is above that, that filter, then all of these custom blocks do something different. Now some of them won't do anything different. Like for example, like the, like the schedule online button. This would just show a list of them. That's not problematic, but obviously this is highly problematic. This and like the. Actually these two. So this one right there, the. The location section. And then this would be problematic if there's more than like three or four. Yeah, but that's not normal. And so let's. We can then edit the block and then we just then would deploy the block, the custom blocks and the different. Like, because all of this is housed in a single plugin, so if you wanted to update it, you just have to upload the plugin file and then all the sites get the updates.

Speaker 2: Okay.

Speaker 1: All of this is at your disposal. It's not yet. Technically it's not at your disposal yet, but it is about to be at your disposal.

Speaker 2: Two things I will need from you. Well, three. Well, obviously, one is the plugin. Two, can I add you to the website so that way you can go ahead and implement it to the template correctly.

Speaker 1: Can you add me to the website? Yes, you can add me to a website.

Speaker 2: Okay, I'm going to add you to the template because I know I had them add it. But what I want to be able to do is have both for right now. That way if Craig's like, oh, hey, I don't want to do that. I want to go back to what we were doing before. We can switch it. And then I also want it to be done right. And I think my developers are idiots, so I don't think they're gonna do it right. And then number three, I'm sure that's gonna take you like no time at all to get it like added correctly or whatnot and make sure that it's functioning. Number three, can you create like documentation for this?

Speaker 1: Like already have.

Speaker 2: You already have. Perfect.

Speaker 1: Yeah, I need to. I need to check, but I. Let me.

Speaker 2: Local.

Speaker 1: Actually no code. Un momento.

Speaker 2: Open folder.

Speaker 1: Wrong one. That folder.

Speaker 2: Yeah.

Speaker 1: And local jungle. Yes. So here, let me. I'm just going to share. Present something else. Yes. Window. So I have a markdown file here that I can convert to like HTML. But we have. Here's the blocks. Let me collapse that LJ coupons. What it does how to use it, any page you want them to go. And then what are the different settings that you have within that block? And then what does it showcase? And then, then the nav locations inside the top bar, the header, the strip with the address and hours shows, the address links to Google Maps shows a little bit of everything.

Speaker 2: Basically what I'm going to do, just for my ability to read this without being dumb, I'm going to put it in cloud. Like, hey, make this into our SOP on how to change this.

Speaker 1: Yeah, Claude wrote all this up.

Speaker 2: I was like, I will understand it perfectly. Cool. Yeah. So here's the vision in the next, in the upcoming months. So these two clients are going to be super important. Number one, we need to prove our processes. Number two, it's also going to prove that the team can function without Craig. In the dayto day, all he's going to be doing is the strategy and then the final qa. So these clients are kind of putting all of our systems to the test. Number two, he is finishing up this site speed stuff, which should help al clients. But once he's done with that, we are probably going to start testing with Astro and seeing what we can actually take over to Astro. So what I actually foresee happening is everything we build in WordPress, we are going to somehow translate one to one to Astro where it's possible. So. We're going to pull the file, the, the website files 100% and have quad rewrite them for Astro and upload it to Astro. So everything that we've done on WordPress should not be any sort of waste because for the research that we've done, it should translate to Astro in some way shape or for.

Speaker 1: What does that mean, translate to Astro?

Speaker 2: So Astro, I guess to my understanding they have a different, like it's almost a different coding language, I think if I remember right, so it would be a little bit different. And what everybody's doing is actually using cloud code specifically for this. Astro wants it to be written one way. So we'll take all the file code, upload it to Claude, say, Claude, I want this translated to Astro. I want this rewritten for Astro, basically. And now Astro wants it written and then we'll upload it to Astro and then boom, there's our website. That's how it should work now because we know things don't work out perfectly. Like that. Is the next hire, it was gonna be a technical, like project manager. I forgot how we loaded that. Basically we're gonna hire equivalent of what Tesla used to do. As far as like project manage, all the website stuff, that was gonna be our next one, but our next one's gonna be like a intermediate developer. So that way they can handle all the internal stuff. If they can't handle something, we still have access to a couple senior level developers and then that's kind of how we're going to run the ship. And then I'm also hiring that technical project manager. So that way they, they know enough about it. They know more than me about websites and they can direct that team a little bit better than I can.

Speaker 1: Yeah. I am the, the Claude. The, the Claude. The, the shoot freak. What's it called that Astro migration seems very odd to me. There's something, there's something about it that just doesn't, doesn't click in my developer brain.

Speaker 2: It might be how I'm explaining it.

Speaker 1: That's. Yeah, I'm, that's what I'm mostly concerned about.

Speaker 2: Yeah, let me do this.

Speaker 1: Because I think what the, the problem that I have is the. And I know you're going to be hiring somebody at some point soon, which is good. But nobody on the active team actually understands the Astro code base. They understand the benefits that Astro will bring. But you have all of these websites built on a code base that nobody understands how it's done.

Speaker 2: Here's the better way of explaining it. I got a better way. WordPress uses PHP, right?

Speaker 1: Yes.

Speaker 2: ASO use JavaScript. JavaScript based web playbook.

Speaker 1: Exactly. Yes.

Speaker 2: 100 That's the, that's the difference.

Speaker 1: Correct. All of you are 100 correct. And it is what it is like that's fine. Every. Everybody. I know that everybody has their preferences. What I don't like seeing is people getting out over their skis using a new technology that nobody fully understands and are relying a lot on AI to just do it. Right. That's the, that's the.

Speaker 2: So correct. And that's the thing. Right now internally we don't have a developer and that's a problem. And it's a problem I thought that was going to get solved with E2M but at the end of the day it was not Box. And it's something that we're kind of coming to figure out. And our, the senior developer that we've been working with, he is, he hates ET he have built so much crap into this is he built the original template. So he's like, I don't know how they made it so bad. I don't know. I wasn't part of those conversations. But anyway, yeah, right now we're on WordPress and we're going to stay on WordPress unless we can prove that migration to Azure works. So in Craig's head, it's through rose colored lenses where the idea of using Astro, where it delivers cache websites every time he loves because the page speed. However, he understands that we do need to test it fit quite heavily. So we're still talking six months from now.

Speaker 1: Yeah, which makes sense.

Speaker 2: He's like, oh, maybe it's only gonna take two months. When it's two months for him, it's gonna take a lot longer than that. So yeah. Okay, I'm gonna.

Speaker 1: Do you have a GitHub account? Do you have a GitHub account?

Speaker 2: No.

Speaker 1: No. Okay.

Speaker 2: It's one of the things I need to get. Okay.

Speaker 1: I was going to share access to the entire repository with you so that you could pull. You would just have access to it.

Speaker 2: Can I do that on the free.

Speaker 1: Yeah, no, it's GitHub's free.

Speaker 2: Okay, I'm getting it now.

Speaker 1: Do you know how to use GitHub?

Speaker 2: No, I'll figure it out.

Speaker 1: It's. Do you want me to give you a 30 second tutorial? Okay, let me pull up, hold on, let me. GitHub desktop.

Speaker 2: And I know you also wanted to show something else with me too, so.

Speaker 1: I do want to show you something else because I am partially a child and when I have new toys, I like showing them off. Okay, sure.

Speaker 2: I have an account now. Okay.

Speaker 1: Entire screen. So do you understand what a repository is?

Speaker 2: Yes. It's where you put all your stuff,.

Speaker 1: All your stuff and it keeps track of changes and blah, blah, blah. So here's my local Jungle template and here's all the various commits that I've made over the last couple of months. So what you will do, you'll download the GitHub client, the. I'm sorry, the, the GitHub app for your, for your laptop. You'll sign in to GitHub and I'm going to share the repository with you so that you have access to it. So what you'll do is you'll. There will be none listed here. I have a million and a half. You'll click add and you're going to clone copy down a repository from the server and then you're going to go over here and filter it and you're. You will only have one, but you'll type in Local Jungle template and it's freaking out on me because it's like, oh, you already have it downloaded. What are you doing? You'll Basically you'll then go over here and once you've selected your repository, you'll then go and choose Is this a.

Speaker 2: Plugin or is this like the fourth.

Speaker 1: This is the whole. This is, this is the repository actually has a lot more stuff in it because that's how I set up repositories.

Speaker 2: So this is like what you should use for like claude and stuff. We're like, hey, this is all about info. Okay, I knew all this was okay.

Speaker 1: Get has become a lot more popular with non technical people in the last like 12 months. Like get is going zoom right now. So you'll then go over here and create a folder somewhere on your system and call it like, you know, Local Jungle plugin, whatever you want to call it. And then you'll click on clone. I'm not going to do this because I already have it on my computer. And then what you'll see in that folder is so you'll go and navigate and you'll see Local Jungle template or folder you have. And you will see not actually all these folders, not all these folders, but you will see the contents of WP content. This is what I have inside the repository. And you'll go over here to plugins and you'll see the Local Jungle core plugin. And that's the, this is the folder of all the stuff that you'll upload. And then inside of it you'll see the blocks guide. And I actually went ahead and had it converted to HTML so that it's just a little bit more legible for what it is. So that way if I make an update to it, all you need to do is go over to you open up GitHub. If I send you and be like, hey, updated the plugin, you'll go to GitHub and you'll click this fetch origin button and it'll go to the server, find the updates and pull it down to your computer for you.

Speaker 2: Great. Okay, so yeah, yeah, the first time you make an update, you're gonna have to show me that again.

Speaker 1: No, that's fine. But I, I at least wanted to give you the basics of it because I feel like if you see the basics, that's gonna trigger thoughts.

Speaker 2: Yeah, you won't know. What do I do? Yeah, I'm downloading.

Speaker 1: Oh, I have actually haven't added you yet. Hold on one second. What is your, what's your email address?

Speaker 2: Gavin T. Local jungle dot com. I should have done the marketing email. It's fine.

Speaker 1: Invite ad. All right, so you should have you Go over to your inbox, View Invite, Accept invitation.

Speaker 2: Boom. Okay, you got one thing this is not. Is this my account?

Speaker 1: Yeah, it is.

Speaker 2: Okay. Yes.

Speaker 1: So now go back over to the GitHub app.

Speaker 2: Yep.

Speaker 1: Click on the little refresh icon next to the filter your repositories. Click on that and say Clone. So the URL at the top, that's going to say the same. Where do you want this to? Actually, this is going to live in your documents folder inside GitHub. Inside local jungle template. That's a fine location in general.

Speaker 2: No, because I need to separate this out because I'm going to use this for my other agency too. Hold on. Oh, I should only have. Damn it. This is the problem of running multiple businesses off of one computer.

Speaker 1: Yes. I had to like. Actually you can see like on the GitHub screen, down the bottom right hand corner, you'll see Chris Lea and then Classic City. I was running two separate GitHub accounts and I had to log in and log out of my GitHub app every time I wanted to make changes to different repositories. Like if I was doing a personal repository, I had to go and log in, log out of my Classic City one, log in my personal one. Then I just combined them all. Recently I said, screw it, I'm tired of this.

Speaker 2: This is going to be. New folder. This is going to be very well good. Local drum Go. And then.

Speaker 1: Excuse me, sorry.

Speaker 2: This is the folder, right? Yeah, the new folder.

Speaker 1: I would keep the folder name that the repository lives in still Local Jungle template, so that the folder name matches up with the repository name. That's a nomenclature thing that I would definitely keep.

Speaker 2: Yeah. So I just added a folder inside of that.

Speaker 1: Awesome. There you go. So go ahead and click Clone. And now it's going to download all the stuff. Now if I tell you, hey, I updated the code.

Speaker 2: Oh, it's in a subfold.

Speaker 1: So that's what you have to be careful. It's going to. Basically what it's going to try to do. It doesn't have to, but it wants that final folder to be the repository name. But anyway, if you open. Go ahead and just open up that folder.

Speaker 2: Hold on. Sorry, I get so.

Speaker 1: So now go back. So now it's in a different location. Now go back to get. Go back to the GitHub app because now that that path is wrong. Oh, say no, it's fine. Click on Locate. Click the blue Locate button and then just navigate over to. And then Local Jungle Template. Double click that. Now click Select Folder. There you go. Now we're good. Now you're good.

Speaker 2: Okay, cool. I. Yeah.

Speaker 1: Okay, so we got plugins and then Local Jungle Core. Oh, go. Go up a folder. That's the. That's a zip file. That zip file is probably outdated, mind you, but there's a folder called Local Jungle Core. There you go. That is the plugin. And then the blocks guide is the dot HTML file, the MD file. And then the HTML file should hypothetically be exactly the same. Just the HTML file is easier for to view.

Speaker 2: Yeah.

Speaker 1: And then the claw dot MD has all the instructions on how to. How this all. How this all works, which you don't need the Claude md. You don't have to read that. That's for. That's for Claude.

Speaker 2: That's for Claude. Okay. Okay, cool. Okay. What do you want to show me?

Speaker 1: I want to show you something. Okay, here we go, Here we go, Here we go. You ready for this? I'm actually going to. It's on a different computer right now, so I'm actually going to hop. I'm going to switch.