Kadence WP

The theme that does not force you to install a builder

It is the underlying decision behind Kadence, and worth understanding before comparing features, because it conditions the site's next five years.

For a long time the normal way of building a WordPress site was installing a visual builder over the theme. It works, and it carries a cost: your site ends up written in that builder's language. The day you want to change, you do not change the design, you rebuild the pages.

Kadence takes the other road: it builds on the block editor WordPress already includes and extends it. The content stays in the native format, the site weighs less and you do not depend on a third party continuing to maintain their builder.

What the official licence covers

It does not unlock different code: what it brings is updates from the admin, the maker's support and access to the starter template library, which is served from their servers and therefore needs validation. The GPLClub team leaves the activation ready on your domain.

Where it pays: on client sites somebody has to maintain, and on projects where the template library saves you days of layout work. Where it shows less: on a personal project already built that barely gets touched. For that case members have the ecosystem's blocks, such as Kadence Blocks Pro, in the membership catalogue.

What Kadence is

• A light base theme, with speed as the main design criterion.
• Extended blocks for the native editor, with the elements the standard set lacks.
• A starter template library, for launching a site already built rather than from a blank page.
• Header and footer control without touching code.
• Good WooCommerce integration, which is where the lightness shows.

Its direct competitor is Astra Pro, the other big light theme, and on features they are very close: the honest choice is trying which one you find more comfortable to configure.

The cost of changing builder is the part nobody calculates

Worth doing the sum before choosing, because the decision is expensive in both directions.

If your site has sixty pages built with a visual builder, that content is stored with that builder's markup. Migrating means opening all sixty and rebuilding them. Which is why hardly anybody changes: not because the builder is good, but because leaving costs too much.

With native blocks that risk drops considerably, although it is worth not overselling it: a particular vendor's blocks are also theirs, and if you stop using Kadence those specific blocks stop rendering properly. The difference is of degree, not absolute. What is true is that the text, the images and the basic structure stay in a standard format, and that survives.

And there is an immediate practical advantage: the block editor evolves with WordPress. Every new version of the platform improves the tool without anybody having to update anything.

About licensing and the GPL

The code is distributed under the GPL licence and its use is free. Automatic updates, support and the hosted templates are services contracted with the maker. They are not the same, and buying one is not buying the other.