Right at the time, quite a lot of users meant 5,000 because no one was in Gutenberg yet. So I feel like even in the early days, there was quite a lot of users on Kadence Blocks and it's all relative. And so it was really easy for me to push things to users and let them play with it and try it. So I had a decent user base that was using Kadence products at the time, this would've been our Virtue theme and our Ascend theme. How many users did you actually have playing with it then?īen: Pretty quickly I had a lot, part of it was because I had been building themes and plugins already.
Wordpress theme deepfocus repository install#
Kathy: So with Gutenberg not yet being in core and basically to install Kadence Blocks, you had to have Gutenberg plugin as well.
Wordpress theme deepfocus repository full#
And so I started to really try to approach Kadence Blocks as I want to build a design tool for Gutenberg so that people can use this as a full page building experience in terms of being able to create whatever you want. And so that was, to me, a key missing part of every block and everything, if you're going to create settings. And I think one thing that still is there with core is that, and they haven't gone into it all, is the ability to change settings based on screen size. So one of the main focuses I had was on the row layout potential, I was like, how do we make columns and how do we make those columns like movable? The core column option at the time was extremely limited, you basically could choose your columns and that's it, and you couldn't tell that anything. At that point, I had to support the Gutenberg plugin because that's how you could enable Kadence Blocks, which meant that the development pace of Gutenberg plugin and the way that, at the time too, it was just a lot easier to break things then because there's a lot less users on it and so yeah, I think in those early days, I rewrote Kadence Blocks a couple times because things would completely change and I'd be like, "Oh no, this isn't going to work." So yeah, I developed Kadence Blocks and released it pre the 5.0 release, so before Gutenberg was part of core, those were crazy times. You're going to be able to make content, but not like a page builder, but could this be a page builder?"Īnd so that kind of exploration into if it could be a page builder, being able to marry the two and allowing users to escape the heavy load of a page builder, but still being able to create really dynamic layouts was appealing to me as a creator as well as just something I thought, this could really happen. And then just like it just does for a lot of people, like finally the block editor clicked and I was like, "Okay, I can see how this can work." And what the constraints that the Gutenberg team had to deal with in terms of backward compatibility and being able to pull in raw HTML into a block editing experiences, I wouldn't want to have to be the one to have to figure all that out, right? But essentially, I came in and I was like, "Okay, so WordPress is making a content editor. So I think, I can't even remember what year it was, but when Gutenberg was still a plugin, not in core, there was a whole year pre to five release where a lot of negativity about Gutenberg and is this really the future that WordPress should be heading in, and in January, February, that year, I was probably in that camp of I don't know if this is right. Can I ask you to, because I know little bits of the story of how you got involved with WordPress and blocks, but I'd love to share that story with everybody listening to Woo Visions.īen: Yeah, sure. You were the first person to really do some innovative stuff with blocks with WordPress. If for those who do not know Ben, he is the founder of Kadence WP. Exciting, isn't it?īen: Yeah, absolutely. I'm Kathy Zant and I'm here with my friend, my partner in Kadence, The Kadence Beat is taking over Woo Visions this week.
Kathy: Hey everyone, welcome to Woo Visions.
0 kommentar(er)
