So I, I was just thinking, I think in, I wasn't thinking out loud. It wasn't making any noise. I was thinking in my head was, uh, one of my clients, um, has their LMS on a different platform to webflow. So we use webflow for, for the marketing and then they have an LMS. Um, and one of the oddities that we have is that you can, you can buy courses on the marketing site, but it pushes all the transactional events you have to do on their LMS site. And it's always not, there's, there's a symbiotic sort of journey going on is that sometimes you, you're on the marketing site and sometimes you're on the LMS site. But when you're logged in on the LMS site, you get this little sort of logged in character. You get your little profile picture and your name and, and then although we make it look and feel as closely as possible to being looking like they're the same site, they look slightly different because as soon as you go back to the marketing site, where there's lots of information and articles and knowledge centers and stuff, it looks like you're logged out. And we, we, we find it hard to, to present that in a way that we can't say log in because they were already logged in. And if they click log in, it will take them to the LMS where they're already logged in. So there could be an instance where we use this type of functionality to bring in that little piece of HTML with their logged in credentials into the web flow nav bar. So it always looks like if they're logged in, they're logged in. And it's just, it's amazing that it's even that simple, a little simple UI UX change that could be done with this type of functionality. And so

with that potentially it could, but you have to remember that you're pulling the HTML over or you're pulling the page over. So if you pull, if you do something like that, you could be pulling more than what you bargained for. Yeah. Okay.

Yeah. Let's call it a little HTML widget or whatever is, has got deep roots into the LMS app, I suppose. But yeah, I'm, I'm, yeah.

In theory, you could target a particular thing and display that on your web flow site. That's in theory, that's possible. But the thing is, is you're pulling HTML over, you're not pulling CSS over. So you could end up with a funky looking, something funky.

Ah, yeah. Okay. Because although with that HTML, you're bringing, because a class name is, is HTML essentially. So you'd have to align. You're not pulling the CSS file over. Yeah. So unless it's inline styles or you, yeah. Okay. Yeah, I get you. So what, what other examples are there where something like, because this, this feels, this feels like a not low hanging fruit, but it feels like a, something that non, you know, because when, when Devlink came out, I won't lie. There's a few of, there's two camps, I think. The ones who got excited because they have exposure to react and they know the power of react and, and then the ones who are sort of like, I don't really know what this means. Does this, like, is it only because I'm, if I work with a SaaS company who use react, maybe they want to bring some of their components in or, but not really that excited about it. The HCMX, the way you present it makes me feel like it's something that I could use on projects that where I'm working with companies that don't necessarily have this big ecosystem of developers and it's built on react and all this kind of stuff. And it's, I can use it in the sort of safety of the webflow environment without thinking too much about other dependencies or having it run locally on my machine or, you know, those kinds of things that the, the, the no code webflow process protects you from in a certain respect. So this, this feels like it's a little bit more obtainable from a functionality point of view and an understandable point of view than, say, using react or, or view. Would that be right or am I maybe simplifying a

too much? And premise of, of HCMX is to provide more functionality to, to buttons, forms and links. So that's what we have on, on the front end. You get, have get requests and posts and pushes. But it's adding additional features. So normally we just use, like everybody has, not everybody, but a lot of people have connected a webflow form to air table, for example. So that's sending data through a form over to air table. So in theory, you can reverse engineer that into webflow. You can get that data from webflow. Not in theory, you can definitely do that. And with HCMX, you can get that data as HTML in, in a, in a way. So we're just, it's adding additional power to concepts that we understand, forms, buttons and links. And the output of that, a lot of that stuff is Java. Like it's, Java script customization. Now, the, I had, I'll give you simple examples. Not instead of going like down this, like it's React, it's view, it's all this. It can, I think it can do, I think it will be able to compete with DevLink, with, in, in simple things, limitations of webflow. Using a CMS tab, you can create a CMS based tab, this tab using HDMX, not a problem. Having CMS categories with CMS content inside those categories on one page, where you've got like heading one, a load of data underneath heading one, heading two and a load of data under that, HDMX can solve that problem. And CMS slider, I haven't, I haven't built one out yet, but potentially it can solve that problem. So, so they're just use cases straight off, like even for your current webflow projects, you can completely make custom, custom tabs, CMS driven, custom, what's the other thing? Oh, yeah, and even nesting. It completely sorts out nesting. You can do that. I was about to say, I think three, four, four times deep with this. It's not.

Because essentially it's the way a lot of Finn's suite solve a lot of these problems is, you know, and HDMX is, is JavaScript underneath the hood, isn't it? It is JavaScript. Well, it's a JavaScript. That's in the, the lifting. Yeah. Yeah, yeah. So, well, instead of the JavaScript

attributes, it's living in your

HTML. But just to kind of, because we, we, you flew quite close to like CMS combined with functional components like tabs or sliders. And you know, you see like web bay at the moment is working on a, I think it's a, it'd be a webflow app, which is going to be a CMS powered slider with the Finn's suite team. And obviously they've got a really good record at bringing lovely solutions to limitations of webflow and using attributes to do that. And I suppose what we're, what we're saying is HDMX is, is almost allow, would allow us in more simple terms to build our own Finn's suite slider CMS execution without relying on the Finn's suite JavaScript. Essentially it's, it's, it's kind of similar, isn't it? Because you know, they, they say, okay, you've got to put, put that CMS at the bottom of the page, then it, ah, so that's going to be on the same page where it's actually with HDMX you can have.

So the Finn's solutions. A lot of times the Finn's suite solutions, not all of them, but a lot of times you have your element that is going to have the content loaded into. And then you have your CMS content underneath that and it, it's a load or a swap. It pulls from here and moves it to, to the element that you want. Perfect solution for a webflow problem. Really good of use of load, use their solutions loads of times. But what this does is that it doesn't live there. So you don't have that flick that sometimes you get. And then you don't have to cache that. So it doesn't happen again. So if you can use a get request that is triggered on page load. So it pulls it straight away. So as the HTML is read, it pull, it, it, it pulls the data that you want or the HTML elements that you want into the right place. Another really cool thing is you can do, like you can have infinite scroll. So if you have a massive website and you're like, this web, like this homepage is huge and you want to con infinitely scroll for whatever reason, but you don't want it to load at one time, you can just have the hero section load. And then on user scroll, the next section loads and on user scroll, the next section loads and all those things are living in different parts of your webflow project. And it means your website is super fast. Now there's complications because when you pull webflow HTML, like if you, if the target a link, so it's the same as changing a page, you click on the link, the Href goes, finds that page and replaces the one you're in. So HTML X does the same thing. But if you target a full link in webflow, you're going to get the header, you're going to get the body, you're going to get the footer, you're going to get like you're going to get everything. So you can, if you do it wrong, you can duplicate even the webflow native JavaScript. And if you do it wrong, again, you can make these duplications like infinitely. So you have to make sure that that you're targeting elements within that HTML. Oh, my God. I was about to

say there's a dog snoring or and or dreaming in the background. My dog is

on that moment. Yeah, my dog just started whining.

No, just in my head, I've like the possibility. So I could have, I could have lots of different pages with content on them. And I could magically on on one button click, bring a variety of those pages or sections from those pages into the page I'm on in a almost in a random manner almost, you know, but I could have they could be all there's like, you know, whether that be useful or not. I don't know. But it's the idea that I'm not constrained to just interacting with the content or utilizing the content on that canvas on that page without the moment without, as you said, if I want to go and access other content that might be relevant to that user journey, I normally have to take them to a new page. Whereas this, for example, say, say, for example, a good example is sign up for a demo, for example, you see this button at the top of a lot of pages. And then that essentially you click on the button, it goes to a page and you've got a form on there which allows you to sign up for a demo for the product. You could have a situation where you want to put that button in lots of different places on the site. And now with HTMLX, you could have that button just straight away, load up that that form or insert a little section that has that form on it. And now you're not even dealing with webflow components. You've essentially made your own little completely flexible access it anywhere component that soon whenever I click on that button, I get this form appear as a nice little component that slops into wherever I am. That's a really good

example. Yeah. You do a modal currently on webflow. You set it to display now and basically, and it sits there. It's there on your page, display now, but it renders. What you can do with HTMLX is you can have a page called forward slash modal. And then you can have a button on your current page like what you were saying there that says, click to get modal. And in that there's a get request that's HX get and that equals forward slash modal. And that modal, well, with a bit more, like I've been quite simple here, but straight away what that will do is that modal will replace that whole page. But if you add a few more attributes, you'll be able to make that modal overlay on your page. And it doesn't live there initially. It lives there right now. And then the X button instead of just hiding and displaying none of the modal, it gets rid of the modal. And where that can come really interesting is if you have huge amounts of CMS items and each of those have a pop up. Like the way we would do it in webflow now is that each button has its own version of that modal because it's true, the CMS, and we've duplicated and triplicated and we've got unlimited amounts of things. And now you'd be able to request that modal from its own part of the website and potentially inject the correct data from the CMS into that based on the button click, which

is okay. Yeah. Okay. Really powerful. Okay. And here's another idea. Maybe this is doable or not. So I click. We've got a home page and I click on a Google ad from a certain keyword and that by clicking on that ad, it categorizes me as a certain customer type, you know, like I'm going to a sports website, then they're marketing sports, athlete tracking software, and I click on the advert that's about soccer. So that attribute comes, well, that value will come through on the URL and could I use HCMX to bring through content related to soccer onto that page because I've got that value come through on the URL. So if they come through on a on a Gaelic football URL, then I could say I could tell the HCMX function go, Hey, look, they've arrived from this place, bring in this Gaelic football content.

Potentially, yeah. Like if you have that, if the get request, you can add URL parameters to your get requests. And if you have that set up correctly with the right pages, builds that are related to those that hate that URL, then yes, I could.