Consume Media - Current

Dawn Audano: Oh, he left. He's coming back.

Lydia Rosenberg: Yay.

Dawn Audano: There he is. He's muted, but he's back.

Chris LaFay: There we go. Okay. My computer has frozen on me. No. Chrome has decided to not work and just shut down. It happened three times yesterday while on calls, mind you. It was great. It was fantastic. Okay, we're gonna try this again and pray that Chrome doesn't die.

Lydia Rosenberg: Sending good vibes. Yay. Yay.

Chris LaFay: We got it. Awesome. Okay, so all the links up here at the top work, but you can't hear. But the play button does play the audio. We have all of your content in here. We imported every single one of your projects. They all.

Lydia Rosenberg: 92 Of them.

Chris LaFay: All 92 of them. And from. We did not click through literally every single one, but there was a good 15 of them that we clicked through and they all seem to be. Everything seemed to be wired up very well.

Lydia Rosenberg: Yay. That's great.

Chris LaFay: So I have no reason to think that they would be messed up. We have the different pods here for the different story pieces. We didn't have the videos for each of those, so we just left the same, same starter video on there. We'll take. We also imported your testimonials. One of the things that you will see is across the site, the pages and their structures were built prior to mass importing all the testimonials, the projects, things like that. So on sample pages you will see the dummy content that we added in the very beginning. We did not go through all the pages and just add in new dummy content with real stuff because we figured that's going to happen anyway, no reason to waste that time. So we have all these various different building blocks. The one thing to think, look at here, what we didn't want to do when we built out all these pages for products specifically is give you guys a dropdown menu during QA that was longer than the screen. So we went ahead for right now and just shove them all underneath the products link down here in the footer so that you guys have easy access to all of the pages without having to think about it. Once you decide which products you want in the nav bar, we will then add those into the drop down menu up here and then we can then call this list. We just want to make sure that you had a starting point be able to get that. Your blog is also all imported as well. So. Wow.

Lydia Rosenberg: There, there.

Chris LaFay: The one thing to note about it is it came over at about 90% accuracy, meaning there's just a couple of things like this that happen every so Often. So if you want to click through them all and do that, feel free. But most of these came over perfectly. Other than some random text pieces, the video imports all came over well. The feature images, the tags, the whole nine yards. All that came over from what I can tell, very much flawlessly.

Landon Schellman: And Chris, when we do see things like that, is it helpful to point it out or is that something that will be fixed or we can fix.

Chris LaFay: On our end or y' all will be able to fix that on your end. So what I would recommend. So y' all will have access to marker and Don will go over this. I would. If there are these like small like on things that are mass import. So mainly projects and blog posts. If you see any posts that you want to go back and edit later, just make a note of the URL somewhere. Don't. If you submit it as a marker ticket, that's going to get in our project management system and I would rather you guys have a list of those things to go back and edit yourselves afterwards.

Dawn Audano: Got it.

Chris LaFay: On the about page. One thing I wanted to call out here specifically is we did go ahead and build a custom block for your. Your toggle your kind of like your hover over states, except we didn't have hover states. I know you're going to have different photos because these photos of different people all were in circles. We're not doing the circles here. So rather than go through and just duplicate Leo's face 15 times over, we just did the one. And so you'll notice here on this page that the goal here is not to go through and edit every single one of these, but to just take Leo's block, duplicate it over and then apply the appropriate settings. I'm not going to walk you through how to do these changes right now. That's not important. But. But I just want to kind of call out that one tidbit for you on the work section. This is the biggest piece that we went ahead and just decided to do, AKA Chris got board. All of your projects are categorized in multiple ways and this we have talked about by product, by strategic goal, and by service line. So one of the things that we talked about adding in later would be the ability to view all of them by category and stuff like that and having them all linked here went ahead and did all of that. So your work page is dynamically filterable by product type, by service line and by strategic goal. Now obviously these random three things that I clicked, obviously they don't have all the things there, but these dynamic Filters, from what I can tell, all work very well, and they. I don't see any issues with them so far.

Lydia Rosenberg: That's so great. Thank you, Chris.

Chris LaFay: You're welcome.

Lydia Rosenberg: It's really cool.

Chris LaFay: So we have that there. We also have. When you're on a project, we went ahead and built out the individual pages that just showcase all of the Brand Anthem ones. And they're all paginated here. So all of this stuff pulls from the exact same styles and structures. So you can link specifically to a categorization of product if you would like.

Lydia Rosenberg: Got it. So if we wanted to send a link to a client of. Yeah, like all Brand Anthems or all of our customer testimonials, like, very easily, we could just send them this sort of specific link and they could see all of our examples that we have on our website for that particular product category. I'm just making sure that I'm understanding. Is that correct?

Chris LaFay: You're 100% correct.

Lydia Rosenberg: Amazing. That's really cool.

Chris LaFay: And so all of these are typical.

Landon Schellman: We wanted to do something like change that gray background color at the top or something. That's not a common to leave. That's something we do on our end later.

Chris LaFay: We can do that. Just note that these. So these are what are called technically taxonomy templates. WordPress as a. Rather than calling things like categories or tags, the global word for that in WordPress is called taxonomy. And so you have three custom taxonomies attached to a project. You have product, strategic goal and service line. The reason I say all of that and dive into that odd detail is each of these. These listing pages of a taxonomy. So in this case, this is a product taxonomy called Brand Anthem. Each of those taxonomies, this is a part of the template. So if you decide you wanted to make the dark gray on the product taxonomy listing. Excuse me, your dark green color. All of your product taxonomies would have that dark green.

Lydia Rosenberg: Got it.

Landon Schellman: Testimonial would have the same dark green or whatever we changed it to.

Chris LaFay: Yes.

Lydia Rosenberg: We could customize all of the product pages to have the same header color. All of the goal pages have a specific color, and all the service line pages to have a specific color or whatever background we want.

Chris LaFay: 100% Correct.

Lydia Rosenberg: Okay, yes. That's good.

Chris LaFay: And later down the road, if. If we want to expand the data that's stored within a single, like, taxonomy grouping, like a. Maybe there's, you know, maybe we wanted to have a description underneath Brand Anthem. So that's why we're gonna add that. That could all be added in later fairly easily. So that wouldn't be in scope for today or for this project, but adding stuff like that in later, not a problem. These are, those are small things that we can do.

Lydia Rosenberg: Okay, cool.

Chris LaFay: Yep. So that's how that works. So that's obviously in terms of quantity of things on your site. That's that right. There is a large bucket both between the blogs and the projects. The next thing is going to be approach now. Now we're getting into pages that we went ahead and built but didn't really have a lot of content for. So we went ahead and built the layouts of these. So we have our, the, our approach section and by the way, we only load in about like 10 or 15 images from the website. So you're probably going to see some of the same images over and over again. And so we have our approach section, different process testimonials, etc, we have our call to action. We have our main products page and these all link to the various different individual products as well. The images were dynamically pulled so these images might not line up one to one with what you want. That's okay. We have some CTAs thrown in here as well. The goal here was to do individual product types and then kind of the groupings of the packages basically trusted by bar. So there's that. We have our home, we have our learn. I build out the contact page. I did because dawn reminded me to build out the contact page. We have the contact page. One thing to note is we do need to have an email address on file to put put to shove this form into.

Lydia Rosenberg: Yeah, we can give you one. I think we just have like a basic consume email or probably that one at the bottom.

Landon Schellman: The contactonsume-media.com yeah, contactsume.

Chris LaFay: Perfect.

Dawn Audano: Hey Chris, do you want to take this opportunity to show them how to use marker for content by adding a note to that page with that email address.

Chris LaFay: That's a great idea. So this is marker. It's our favorite tool in the world. We've used it for like five years. So the way you'll do this is you'll click on report issue and it's going to take a screenshot of whatever the heck you're seeing and you will have a form over here on the right hand side that pops up. Actually, let me actually back up. So what you can do, you can now annotate this mock up. So let's say that you wanted to change that particular field or let's say that you notice that you know this isn't Right. But like let's say that, that there was something there wrong. You could mark this up as much as you want and then we pre populate to basically two questions. What is wrong? Email doesn't send when submitted what it should be send to contact@consume media.com and if you have an attachment, so let's say that you wanted to swap an image out or things like that, you could go here and add an attachment. You can then put in whatever you want there. And then when you click on Create Task it's going to do some intense mathematics and calculus. And since you all are in asana, let me go ahead and share this tab. You will now see that a task has been added. Fix email send failure on submission and it said it submits all of this. It also sends us the screenshot and also tells us all the different like different like the URL that you were on and all the different like kind of interesting pieces there as well. So this is why when you guys are submitting tasks, it's great to do it together so that we don't have the same tasks being put in by different people that also say conflicting things.

Landon Schellman: Yeah, we can definitely get together as a team and do it together because we understand that struggle. We don't want to. Do you like that.

Lydia Rosenberg: Yeah, we have a. We actually have a two hour block tomorrow to do just that. It's on our calendars.

Chris LaFay: Fantastic. So that right there is the bulk of everything that we build out. Because most of the product pages are basically exactly the same. They were just copied and pasted. We also went ahead and built out a B2B like some industry landing pages here as well too to get you guys started with as well. If you guys decide you don't want to do these, that's perfectly fine. I know they don't exist on the site right now. That's okay.

Lydia Rosenberg: That's great. I think we've always had that intention and we just hadn't built it out yet. So it's nice to have something to use as a foundation. So thank you.

Chris LaFay: The other piece, the other piece that I'll also tag in here as you all are going through and doing QA is if there is a building block that or a set of blocks, you're like, I need this set of blocks identical on every single page. For example, the trusted by bar. The trusted by bar is actually a shared component that if you edit it in one place, it edit it across the board. So as you're going through things and you're thinking you know what? This little section, maybe this ends up being like a process section over here. You're like, we need that section across other pages. Make a note of that. Because when we then go through and edit this, we can then make it shared and then apply it, the exact same one across multiple pages, so that it saves everybody a lot of time in the future.

Lydia Rosenberg: Cool. Chris, question for you, actually. Sorry, you just brought it up. The trusted by bar. Is it possible because, like, for example, if we do like B2B SaaS, companies like our, like our industries, we would probably want that trusted buy to be different across those three pages. Right? Like, so. So you mentioned, right now it's currently built as you change it one place, it changes across the board. Is that something that's easily. That we're able to make a, you know, duplicate and make a special one?

Chris LaFay: Yes. So my recommendation is. So there's one other page that's not linked anywhere. It's called block library. And Don can send over the URL to this. This is basically our listing of all the different building blocks that we have at our disposal with how to use them and all that jazz. So knowing how to use them right now is not the most important thing. My recommendation would be if you have a friendly, the most organized way to do this, if there are things like that to where you want the same things on multiple pages, I would like that to be in a single ticket. So I think what my recommendation would be, since y' all got, since y' all are very used to asana, is if you have something like that, drop one ticket on a particular page and then go into that asana task and then add to that description and basically say, on these pages we want these. On these pages we want these other ones.

Landon Schellman: Chris, would it be easier if we left that feedback on this block library?

Chris LaFay: You could do that. So you could also find it here. Like, so there are some things that you want in mass that you're noticing kind of globally. Feel free to go to the block library page and find that block and then leave the comment there. That way we. That's also just an easy way to know that you found this in multiple places. That also works. You could also, if finding it on here, because all. All of these have names that are associated with their blocks. Like, as you're building it, you would type in CTA Dash thin, and this little buddy right here would pop up. But I also know that looking at it solely on the front end of the site, you're not going to know what those that nomenclature is. And so in a perfect world, yes, anything that's global that you notice in multiple different areas, toss the feedback on the block library page so that we kind of know that it's global. Anything that's one off directly on the page. But don't waste minutes and minutes and minutes of time trying to find stuff on the block library. Rather you just go back into asana, find the task that you dropped and then like, hey, by the way, this was actually on multiple pages. Here's a couple of other URLs, just FYI. Does that make sense? That was a little bit confusing. I realize I can re. Explain that if it would be helpful.

Landon Schellman: Yeah, I think I got you. And Chris, if we have. If there's a page. So just going back to like a general web page, if there's a page that we had a couple of comments about, is it better to do one comment with marker IO or is it better to do multiple?

Chris LaFay: Multiple, because it's only going to take one screenshot and so it's not going to take a screenshot longer than your, your viewport. So my recommendation would be like, let's say that you had. I would honestly, I would probably do one core, one core request per ticket. So rather than try to like get both of these in the. Like, like, let's get both of these in the screen, like zoom out a little bit and then do this and then mark up multiple things. My recommendation would be kind of one global requests per ticket and then just kind of add in, add in items that way.

Landon Schellman: Okay.

Lydia Rosenberg: Okay.

Chris LaFay: Because we know the page that it's on. You don't have to tell us what page is on. Marker will then send us the URL, the browser type, the screen size, the whole nine yards. So we know all of that. So we can organize that way, son.

Landon Schellman: Got it.

Dawn Audano: Okay.

Landon Schellman: Thank you.

Lydia Rosenberg: Are there other things, Is it quite obvious, Chris, like what blocks are the ones that are this. Like, like the trusted by one where you said, hey, if you change this one place, it changes everywhere. Like, is it. Is that clear in the block library? Like which blocks those. Like which things?

Chris LaFay: I wouldn't, I wouldn't worry too much about it right now. Know that I think the only legitimately shared block that has. If you edit it in one place, that edit. It's everywhere. I think the only one that we have right now is the trusted by one.

Lydia Rosenberg: Okay.

Chris LaFay: All the other ones are template templated blocks to where.

Lydia Rosenberg: Okay, so like FAQ is. Yeah, FAQ is like a template and we could change The FAQ on no matter what page. And that's not a problem.

Chris LaFay: Bingo. Exactly. I think that's pretty much the only one. All of the. All of the hero blocks Ex. So all of the hero blocks, except for the. The one that's on the blog posts and the. The projects where the. The image kind of hangs off a little bit, all of the hero blocks are actually the exact same code base. They are just different heights and paddings and then center and left alignments. So if you ever. If you leave a comment on a hero block, all the heroes follow the exact same code base. So a change in one of them that looks like this will change all. All of them from a style and structure standpoint. Obviously they can have different background images, different background videos, different background textures, colors, the whole nine yards. So I wouldn't worry too much about whether blocks are shared. Most of them are templated.

Landon Schellman: And Chris is something like, oh, we'd like to use a green CTA button here instead of this light gray one. Is that a useless comment? Because we can just change that on our end.

Chris LaFay: You can go like, if you want to go ahead. And if they're actually dawn, do you want to. Do you want to hop in here and talk a little bit about content edits and things like that.

Landon Schellman: There?

Dawn Audano: You can keep sharing your screen though, and I think that would be helpful. Okay, cool. So for this section, for example, what these clients need, you can use the marker tool as well to add our content in here. So you would do the exact same mechanism. You would hit your report, a what does it say? Report issue. I would usually highlight the section or you could. So I would say, like, change this text too. But for the whole section, if you wanted to change it, you would say like eyebrow text. And then you would tell us what the eyebrow text would say. You would give us the heading, what that should say, paragraph text, what that should say, and then the CTA and what that should say, as well as where it should go. So for blocks like this, we actually need five different items. Plus, if there is a video that needs to go somewhere else or an image that needs to be changed, you would change those. You can add those and upload them here. There's an add attachment feature that you would just click that adds it to marker, and then I have to manually add it to asana. But we. We get all the content in one place, and that allows us to. That allows us to be able to swap everything out pretty efficiently. If on your end, it would be very helpful for you to have a list of pages you've already added content to because all of these pages are, are right now looking identical. So you're going to want to know which pages you've already commented on so you don't end up kind of in a loop updating content again and again.

Lydia Rosenberg: Yeah, yeah, no, and that's helpful. Thank you, Dawn. I guess like our maybe and maybe this, maybe this is what Landon's asking more is like, is that, I mean, is that something that is easy enough for our team to handle? And like, is that really the best use of you and your team's time at this stage? Given the fact that like, for example, I know that like Michael has experience in WordPress and I think that we could like go back and update the eyebrow text, the header, that, that stuff. And to be totally fair and totally honest, we're not going to have all that information done in a two hour meeting tomorrow. It's just like, I want to be totally honest with you also. Like, I. So I guess the thought is like,.

Landon Schellman: Is that easy for us to change ourselves?

Lydia Rosenberg: Is that easy for us to change later? If so, we're happy to do that. We have no problems. We want to focus on this like QA with y' all of like, what are the things that we really need y' all to like help us with versus like what we can just like update later?

Dawn Audano: Yes. So, and it's a fair question. I think my personal goal is to always get the website to a place where before it goes live, before we pass it off to you, everything is there. So I think if you we this round of QA for sure should just be on making sure that everything works. And then for those blank pages, we can always come back in. If you want to have the access to the site to do it, Chris will have to just talk through, I guess, the logistics for giving them access and then what the go live would look like after that. Do you want to talk about that now?

Chris LaFay: Yeah. So what we'll do is if so going back to some of the like marker comments and things like that, making notes on things like this button should be green versus gray. Don't worry about that type of stuff, only work about. Only worry about the larger pieces that are a little bit more global. Font sizing, spacings, general coloration, things just don't look right at all. What I would like to do is. Let me see here. I'm not going to solve this problem right now. Problem, sorry, that's not working. I would. What I would like to do is I'm going to. There's going to be videos recorded once all this stuff is done about like how to edit the site, different building blocks etc. There's actually already built, actually recorded some very long form videos about how I built out pages. And so what I would like to do when you're done with this round of qa I want to send over some of those page building videos just so that you have a little bit of a primer on how these blocks work. And then let's schedule probably an hour to an hour and a half call where we go over it all together of how to do various different things. What are limitations and whatnot.

Lydia Rosenberg: Yeah, I would probably. I would definitely have Michael join in on that one.

Chris LaFay: Oh yeah, totally. Yes. And make sure so the. The required piece of that will be at least watching one of the videos that I send. They'll probably about 30 or 45 minutes. Because I'm very much my mindset on building content pages in the back end of any website. It's not. Nothing is simple like it's. Some things are easier, some things are harder. Don't get me wrong. But there's nothing that just is like magic. It's. Everybody has different preferences on how to build out pages pages and so I record them long form with the intention of showcasing thought process of like oh, I dropped that in there. That did. That didn't work the way I expected. How did I fix that? So it's very intentional. Let's schedule a meeting for maybe that week of the 13th where we do a deep dive on page building. We'll make a backup of the site beforehand and will give you guys access to the site for a couple of weeks. And so we just want to make sure that the site in terms of its building blocks and its structure is all in alignment so that when you guys get it, the only questions you should have is how does this block work?

Lydia Rosenberg: Cool. That's great. I think that's a great idea just looking at some calendars and such also just if we wanted to go ahead.

Chris LaFay: It's not. I'm sorry, it's 9:30. I have a meeting. I have to hop off. Dawn has access to my calendar. We can, we can skip that a little later. I do apologize. I lost track of time. Time. So I'm sorry.

Dawn Audano: You're good.

Lydia Rosenberg: Thank you.

Dawn Audano: You're fine.

Landon Schellman: Thank you so much, Chris.

Chris LaFay: Take care.

Lydia Rosenberg: Bye bye.