Online AB First Test

[00:00] Hey folks, happy Tuesday. So I wanted to do a quick little test and share with you what I've found. So I wanted to kind of pressure test how long and how difficult it would be to

[00:10] move the barometer to the online version. As an aside, I think we should retire the use of dynamic

[00:20] for now, because I think the reality is that what we're really doing is more of an online and responsive version. Meaning it's online being that it's going to be hosted on Webflow,

[00:30] so we get all the analytics and the gating and the stuff we need out of it. And responsive, meaning it responds to whatever device it's on. So mobile, tablet, etc., and we can start to do

[00:40] special things for different devices basically. So that will unlock quite a bit for us. But

[00:50] barring an entire lecture on that, I wanted to just kind of see how long would this take to just move an issue from print to online and try to match as much of the styling that

[01:00] was already decided for the print version. So I took issue 5 and said I'm just going to try to start building this thing out in a way that I think we could easily reuse the pieces. That

[01:10] obviously has a big asterisk around the conversation we've been having for the past two weeks about

[01:20] how consistent is one issue to the next. The consistency needs to be thought about from a structure perspective, not necessarily a what-it-says perspective. So we can have any number

[01:30] of paragraphs right here, for example, as long as those paragraphs are always in between this heading and this scale, right? It's that kind of way of structuring the document that makes it

[01:40] cut down at the hours it takes. So the barometer, the most recent one was like 10 pages or so of

[01:50] actual content. I built out about four or five of them, and it took me about five hours or so

[02:00] is I think where I'm at. Now that was me building it from scratch with logics and stuff in a way that I knew that one of our agents would be able to build it faster in the future if we just said

[02:10] here's the updated content. But there's always going to be a need for us to get in there and to make sure the stuff's working correctly and work back and forth with our human brains and

[02:20] eyes to understand is this the right thing to show here in this way? Does it read correctly? All that sort of stuff. So the more special cases we have throughout the document, the more hours

[02:30] it will add every single time I need to do one of these. So, okay, with all that, let me just

[02:40] kind of show you where I'm at. So I've got this piece in here that's responsive. We have a sub menu. I'm swapping out the main nav up here. So you can see it's kind of switched to the agentic

[02:50] barometer version. We might actually want to put this logo up there instead to really make it feel like that, but it would basically take you to the other issues. So we'd be launching this with

[03:00] historic issues, which I think is a, you know, it's worth some time, but it's table stakes. I

[03:10] think it would be nice to be able to see the previous ones. And then a methodology and about page that could be a methodology and about page, or it could be two pages. Not really sure. It just

[03:20] sort of threw something up there. We have the hero, which opens up very much like the document does. And then a sub menu here, which you can see is sticky. So it's always going to kind of keep a

[03:30] distance off of there. And as you can see, it's highlighting the section that we're looking at. So this would be the overview and you kind of get the, how to read the barometer. I moved the order

[03:40] of this because as I was reading it, I was confused. So I put it up here and I added this heading to make it a little bit clearer. But you can see that this is, you know, built out

[03:50] all this HTML. So this is all like, you know, highlighted stuff. It's structured correctly, effectively. And then we have the index tables. And again, all of this stuff is kind of a built.

[04:00] So there's no images here. This is all like actual code. Then the so what piece, then moving into the position and momentum, you can see that the top switches. So if I click on it, it'll scroll me to

[04:10] that section. And again, these would all be, you know, populated there. This all right now is very static. You know, it's just already on the page, but in theory, not in theory, once we get there,

[04:20] it will sort of more responsively and animated, like load in. So not that things will be like

[04:30] flying in, but just as you get closer to the bottom, things will start to fade in the next way to make it. And that'll give it a little bit more of like a dynamic feel.

[04:40] And then going down. So these two pieces are almost always the same, right? Like ideally, right? We have overview and the moment or position and momentum. And then here is sort of where the editorial kind of starts. And this can kind of be whatever,

[04:50] right? I started taking the pieces on the pages. Once you take all the headings off, there's actually kind of like

[05:00] This is an example where the design here of these could work for print and you could keep it that way for the PDF version, but for the online version we'll need to simplify and

[05:10] pick and choose how we're going to go about some of this stuff. And then what a controlled agent looks like, so I'm just going on and on, and then the

[05:20] money map is where I sort of stop just to kind of get a sense. So what does this mean, how does this kind of work? If we look at it on mobile, you could see that it's a bit of a mess when it comes to

[05:30] going, if I bring it all the way down to like mobile, but you get the idea that it's a responsive

[05:40] system. So it doesn't matter what screen you load it on, it will always look good and we'll start to make it adapt for that. So as you can see, I have a lot of work to do to make it not terrible looking when it's

[05:50] on mobile. But point being is that things will rearrange, text sizes will change, and that'll give us a better sense. And then from a tracking perspective, of course, we'll be able to see what devices or people

[06:00] are using it on, how many times they're accessing it, and a whole bunch of other sort of pieces there. So anyway, that's kind of the preview I meant.

[06:10] I think for now, I'm not really sure if it changes the direction for our next issue yet. I kind of, it's only, obviously it's three days away from the end of the month.

[06:20] So I think my original estimate of December being the first possible use of this is probably still accurate, but I think it's a good step forward.

[06:30] So I'm curious to hear your thoughts. I'll share the actual link too so you can kind of poke around with it.