George says this is his first pass on the Toro site and that he is using a careful Webflow workflow to protect the live site while making cleanup edits. He explains that he created bz-dev and archive folders, copied current pages into draft backups, and used comments to flag broken links, buttons, and other issues he found while testing the pages. George plans to work through the fixes over the next day or two with the goal of having the site cleaned up by Friday, and he asked for confirmation about whether the case studies and customer stories are the same and whether any live but unfinished case study pages should be taken down.
[00:00] Hey folks, happy Wednesday. So wanted to quickly just go over some of the things I'm going to be working on and a little bit about kind of like how I work in
[00:10] Webflow. Obviously we haven't worked together yet on a website. This will be sort of the first thing I'm tackling. So I want to just give you a sense of sort of what I'll be doing so you have an understanding of where things, what
[00:20] things are moving and you know what to expect. So the goal anytime I work on any website of course is to make sure that the live site doesn't break or that
[00:30] things aren't accidentally published or sort of out of place. So in this case obviously I'm doing some cleanups that's a little bit different, but either way I
[00:40] sort of added the same methodology. So you'll notice that over in the pages I've added two new folders, a bz-dev and an archive folder. The bz-dev folder is
[00:50] the folder that we'll be working in when I develop new pieces that actually have to be put in place and we sort of need a live environment on the internet to
[01:00] actually build them. And then the archive is filled with all of the stuff that we edit. So in this case I put all of the current pages in there, copied them, made
[01:10] them a draft so that we have a backup version of the content for all of this. If anything happens we have a place to go and get them. Okay the actual edits
[01:20] though. So a lot of them are either just kind of noticeable things that are not working or are broken, where others are things that are a little bit less
[01:30] obvious that I kind of found. Webflow has a comment system so I'm taking advantage of that just because I think it would be easiest to just keep
[01:40] track of what piece actually is broken and my sort of status on it. So you see for example I went through every page and I you know tested a lot of the
[01:50] pieces. These links aren't working so I kind of flagged that as a thing. You know there's a button over here that needs some fixing etc. So I went through a lot
[02:00] of these pieces and tagged them all. Over the next day or so I'll start really tackling these so that my goal is that by Friday this site is sort of cleaned up. The pieces that were noticeably broken are not anymore and then we can
[02:10] focus on starting to notice some more of the styling changes and also start focusing on some of those CMS pages. The one call-out I had and question I had
[02:20] was around the case studies template and that were the case studies in general. So
[02:30] I think case studies and customer stories are this one in the same. If that's a wrong assumption let me know. But the current question I have is
[02:40] around the obviously this page is broken from a styling perspective but it's also has a mix of published and draft items but things aren't
[02:50] necessarily linked up. So there's like you know static copy here or say placeholder copy. This title is for a different project but these pages are
[03:00] live meaning they're probably being crawled by Google. So I wanted to flag those that if these are not ready for primetime that we should pull them down.
[03:10] I'm happy to take care of that but wanted to wanted to know just in case you are using them for something. Undoubtful but we'll see. Anyway yeah keep
[03:20] keeping an eye out for me for updates over the next like day or two as we start pulling the site together.