Add to Preferred Sources
The wordpress block theme vs classic theme choice shapes every future edit, plugin decision and performance result your site will ever produce — and it gets answered incorrectly by most SA businesses because they copy global advice that ignores local constraints. If you are reading our guide on what a website costs in South Africa, the theme type sitting underneath your build can shift that budget up or down and change who you can hire to maintain it. Get the decision right at the start and you will not face a costly rebuild two years in.
WordPress is the dominant CMS for SA business websites according to local market data, yet the technology underneath those sites is splitting in two directions. One direction — block themes built on HTML templates and theme.json — gives clients visual control of the entire site without developer involvement. The other — classic PHP-template themes — gives developers precise control and nearly universal plugin support. Each direction suits a different operator profile, and SA constraints (WooCommerce with PayFast, a PHP-developer-heavy freelance market, and mobile-first visitors) change the calculation in ways that global comparisons miss.
Quick Answer
A wordpress block theme vs classic theme decision comes down to who edits your site and what plugins it depends on. Block themes power Full Site Editing — clients change headers, footers and page layouts without a developer — and load only the CSS each page actually needs, which benefits mobile performance. Classic themes rely on PHP templates and the Customizer; they are the right choice when your site runs Elementor or Divi, or when your developer team is PHP-first. Most new SA builds in 2026 suit a block theme or a hybrid theme; existing Elementor-built sites should stay classic until a planned rebuild.
Jump to a section
Not sure which theme path fits your site?
Send us your current setup — plugins, page builder if any, who edits the content — and we will tell you whether to switch, stay or rebuild.
Get a free theme assessmentHow do WordPress block themes work?
A WordPress Full Site Editing theme — the formal category name in the WordPress.org directory — stores every template as an HTML file containing block markup, manages all design settings through a single theme.json configuration file, and delivers the complete site through the block-based Site Editor rather than through multiple legacy panels.
The traditional PHP template hierarchy — header.php, footer.php, index.php — is replaced by an equivalent set of HTML templates in a /templates/ folder. Reusable site elements like headers and footers live in /parts/; design patterns and starting layouts sit in /patterns/. There is no separate Widgets screen and no classic Menus screen; Navigation blocks and template parts handle those roles.
The editing experience inverts the classic WordPress model. In a classic theme, only a developer can modify site structure; a block theme lets the site owner redesign headers, footers, 404 pages and layout templates visually — without touching code. WordPress generates CSS only for blocks that actually appear on each page rather than loading one heavy global stylesheet on every request, which is the architectural reason block themes tend to score better on Core Web Vitals than classic themes of equivalent complexity.
Block theme in brief
HTML templates + theme.json + the Site Editor. Developers supply design tokens and patterns. Clients control layouts, colours and typography without code. Performance default is lighter because CSS is per-block, not global.
How do classic WordPress themes work?
A classic WordPress theme is built on PHP template files and registers its editing surface through three separate interfaces: the block editor for page content, the Customizer for colours, fonts and site identity, and the Widgets and Menus panels for structural elements. Theme logic sits in functions.php; styles live in style.css with any overrides in the Customizer or a child theme. Changing a header layout means editing PHP or installing a page builder — which is why Elementor and Divi grew to dominate the SA freelance market. They gave clients design flexibility that the classic model otherwise reserved for developers.
If you compare classic theme WordPress South Africa freelancer availability against block theme expertise, classic theme knowledge is more widely held in the local market — and that has a real effect on maintenance costs and turnaround time.
Classic themes also have a 15-year head start on plugin compatibility. Almost every WordPress plugin — form builders, SEO tools, booking systems, membership platforms, WooCommerce extensions — was built and tested against the classic theme paradigm. That compatibility gap between classic and block themes has narrowed but has not closed entirely, which matters for SA businesses whose sites depend on established plugin stacks. WordPress core continues to support classic themes, though practitioners increasingly report that new feature development at WordPress core is block-first, with classic themes in maintenance mode.
Classic theme in brief
PHP templates + Customizer + Widgets and Menus panels. Developers control structure; clients edit content. Nearly universal plugin compatibility. Requires PHP knowledge or a page builder for layout changes. Fully supported by WordPress core, no new core features targeted at this model.
WordPress block theme vs classic theme: 5 key differences
The difference between these two theme types runs deeper than the editing interface — it changes who can do what, what plugins you can rely on, and how your site performs by default.
| Dimension | Block Theme | Classic Theme | Best For |
|---|---|---|---|
| Template format | HTML files + block markup | PHP template files | Block: new builds; Classic: PHP-heavy custom logic |
| Site-wide editing | Full Site Editor — one interface | Three interfaces: Customizer, Widgets, Menus | Block: client-editable sites; Classic: developer-controlled builds |
| Design settings | Centralised in theme.json | Scattered across CSS, Customizer, functions.php | Block: cleaner handoff; Classic: granular PHP control |
| Plugin compatibility | Growing; most major plugins now compatible | Mature; near-universal across 15+ years | Classic: complex legacy plugin stacks; Block: new plugin selection |
| Performance default | Per-page CSS; lighter asset load | Global CSS on every page; heavier with page builders | Block: mobile-first, Core Web Vitals targets; Classic: optimise manually |
The hybrid option: A hybrid theme is a classic PHP theme that adds theme.json and block pattern support while keeping PHP templates where they provide control. Many SA development teams shipping WooCommerce stores in 2026 land here — getting block patterns and design tokens without the FSE rebuild cost.
Which WordPress theme type suits your SA business?
The right theme type for a South African business depends on four variables that global comparisons routinely ignore: who will edit the site, what plugins the site depends on, whether your developer is PHP-first or JavaScript-capable, and how critical page speed is to your visitor profile.
In South Africa, where the majority of web traffic arrives on mobile devices over variable connections, performance defaults carry greater practical consequence than in markets with reliable high-speed infrastructure. A site carrying more than 200KB of JavaScript from a heavy page-builder theme is slower on the connection that most of your visitors are actually using — and that overhead is the norm for full-featured classic theme plus page builder combinations.
Finding a developer who can properly build and maintain a WordPress block theme South Africa-wide is possible but takes more searching than finding a PHP/Elementor developer — the local freelance market skews classic — so factor development support into your decision alongside performance.
| Your scenario | SA-specific modifier | Recommended theme type |
|---|---|---|
| New brochure/services site, client will update content | Mobile-first visitors; want low ongoing dev cost | Block theme — client edits without agency calls; lighter default performance |
| New WooCommerce store with PayFast/Peach Payments | PayFast plugin has declared WooCommerce Blocks compatibility; complex checkout customisation still PHP-heavy | Hybrid theme — block patterns for marketing pages, PHP control for WooCommerce templates |
| Existing Elementor or Divi build, no planned rebuild | SA freelance market is PHP/Elementor-first; switching risks breaking existing layouts | Classic theme — stay the course; optimise for speed via caching and image compression |
| Marketing site with multiple authors or frequent layout changes | Reducing developer dependency lowers ongoing maintenance cost (R500–R3,000/month in SA) | Block theme — Site Editor gives non-technical authors layout control; reduces billable change requests |
Good fit for block theme: A Johannesburg accounting practice building a new services site wants the marketing manager to update team bios, service pages and seasonal promotions without calling a developer each time. A block theme gives the marketing manager layout control in the Site Editor while a developer sets up the initial design tokens and patterns once.
Poor fit for block theme: An existing SA retailer whose WooCommerce store was built on Divi two years ago, with 15 custom templates, a Divi layout library and a marketing team trained on Divi's interface. A block-theme rebuild is hard to justify on cost and risk unless a redesign is already planned.
WooCommerce and SA payment gateways: which theme works better?
For South African ecommerce built on WooCommerce, theme compatibility with payment gateways is not theoretical — it is a build requirement. PayFast, the country's most widely used payment gateway with more than 100,000 South African businesses on its platform, maintains an official WooCommerce plugin that has explicitly declared compatibility with WooCommerce Blocks, the block-based checkout experience available in block themes. The August 2026 release (v1.7.8) requires WordPress 6.9 or higher — a sign that the plugin is tracking the modern WordPress stack.
If you are weighing a new SA Gutenberg vs page builder decision for your store, know that the gateway compatibility barrier that once kept SA stores on classic themes has largely been addressed for PayFast. The practical implication: payment processing is less likely to be the blocker for a block theme in South Africa than it was two years ago — WooCommerce template complexity is the more common constraint in 2026.
That said, WooCommerce stores with complex PHP template customisations — custom product layouts, bespoke checkout logic or deep WooCommerce hooks in functions.php — are better served by a hybrid or classic theme in 2026. A full switch to block theme FSE removes direct PHP template overrides; rebuilding that logic in blocks requires developer time and testing. Gatilab's 2026 developer guide specifically cautions against block themes for stores where WooCommerce template overrides are central to the user experience. The honest answer for most SA WooCommerce sites right now: a hybrid theme with block patterns for marketing content and PHP templates retained for the storefront.
If your SA store is also thinking about the broader annual running cost of your website, theme type affects maintenance spend. Block themes reduce the number of plugins you need for basic tasks (navigation, image galleries, layout), which can lower the plugin licence overhead that accumulates in a classic theme setup.
Building or rebuilding a WooCommerce store in South Africa?
Tell us your current plugin stack and payment gateway — we will map the right theme path for your store and give you a timeline.
Get a WooCommerce theme assessmentWhy South African businesses work with Growth Pulse Media
Growth Pulse Media selects the WordPress theme architecture that fits your actual editing workflow and plugin requirements — block, classic, or hybrid — drawing on direct experience operating and scaling South African ecommerce businesses. Founder Dirk van Greuning built and scaled a large South African ecommerce business before founding the agency; the decisions described in this post — theme type, page builder choice, plugin stack, WooCommerce template architecture — are ones worked through on live SA operations, not hypothetically.
Our web design service is built around those decisions: we choose the theme architecture that fits your editing workflow and plugin requirements, not the one that is fashionable globally. We keep a deliberately limited client load so every build gets senior-level architecture decisions, not a junior following a template. All work is executed in-house.
We also maintain sites after launch. If your theme type choice creates an ongoing maintenance cost, we will tell you that before the contract starts, not after the first invoice.
Who this is NOT for
You want a theme switch, not a rebuild. Switching from a classic theme to a block theme is effectively a frontend rebuild — design, templates and page builder content do not transfer. If your budget is for a "quick update," keep your current theme and invest in caching and image optimisation instead.
You are on a complex custom WordPress membership or LMS build. Membership plugins and LMS platforms built on PHP shortcodes and classic template overrides have uneven block theme compatibility. A theme switch without testing every membership flow first carries real risk of broken enrolment or payment processing.
You want a low-cost template-flipped block theme with no architecture work. A block theme's Site Editor gives non-technical users layout power — which means a poorly structured block theme also lets them break the layout. Block themes without a sensible design-token system and pattern library hand clients a tool without a manual. The upfront architecture work is not optional.
You need a developer to stay in full control of every pixel. Block themes are specifically designed to give clients layout autonomy. If your business model requires that every visual change goes through a developer for brand compliance reasons, a classic theme with strict role permissions and a page builder locked to a template library is the better fit.
Trying to scope your WordPress build budget?
Send us your requirements — we will assess theme type, plugin dependencies and timeline and give you an honest project scope, no obligation.
Get a free project scopeFrequently asked questions
Can I switch from a classic theme to a block theme without losing my content?
Your posts and pages content survive a theme switch intact, but your visual presentation will change significantly. Headers, footers, sidebars and custom page builder layouts do not transfer between theme types — they need to be rebuilt in the Site Editor. Treat a classic-to-block theme migration as a frontend redesign, not a settings change, and budget development time accordingly.
Do block themes work with PayFast and WooCommerce in South Africa?
Yes. The official PayFast WooCommerce plugin (v1.7.8, August 2026) has declared compatibility with WooCommerce Blocks, which is the block-based checkout used in block themes. For standard checkout flows, a block theme is viable. Sites with deep PHP WooCommerce template overrides should use a hybrid theme that retains PHP control over the storefront while delivering block patterns for marketing pages.
Does the wordpress block theme vs classic theme choice affect my Google rankings?
Theme type alone does not determine rankings, but performance does. Block themes by default load per-page CSS rather than a global stylesheet, and avoid the heavy JavaScript payloads that page-builder-dependent classic themes often carry. Those factors affect Core Web Vitals — Google's experience signals — which are used by ranking systems. A well-optimised classic theme and a well-structured block theme can both pass Core Web Vitals; the block theme starts closer to the pass line out of the box.
Are Elementor and Divi compatible with WordPress block themes?
Elementor and Divi install on sites running block themes, but they were designed for the classic theme paradigm and largely bypass Full Site Editing when used with a block theme. You end up paying for a block theme's architecture without using its editing advantages. If your workflow depends on Elementor or Divi, stay on a classic theme until a planned rebuild makes a full switch worthwhile.
What is a hybrid WordPress theme and should SA businesses use one?
A hybrid theme is a classic PHP theme that adds theme.json and block pattern support, keeping PHP templates where structural control matters. Many South African professional builds in 2026 use this approach for WooCommerce stores: block patterns handle marketing and landing page layouts; PHP templates retain control of the product, cart and checkout pages. It is a practical middle ground for teams that are PHP-first but want access to modern block capabilities without a full FSE rebuild.
Need the right WordPress architecture for your SA business?
Growth Pulse Media builds and maintains WordPress sites for South African businesses — matching theme type, plugin stack and WooCommerce setup to your actual editing workflow and budget. All work is in-house; limited client load means senior attention on your build, not a handoff to a junior. No obligation — we will get back to you within 24 hours.
Start the conversation