A readability + accessibility benchmark for themes

The tech changes. The benchmark shouldn't.

Brndle is the home of a single readability + accessibility standard that themes should hit no matter what runtime they ship on. WordPress, Astro, Ghost, Shopify, static-only - the file system differs, the language differs, the standard does not. The Brndle theme for WordPress is the first reference implementation. More variants, plus the per-topic benchmark writeups, are on the way. All GPL-2.0+, all on GitHub.

The standard
Cross-stack, single bar
WordPress reference
Shipping now
Astro / Ghost / Shopify
2026 - 2027
License
GPL-2.0+ · forever

Right now

Here are all twelve schemes, one at a time.

Each one of these is a single setting in the admin panel - one click, save, done. The Brndle WordPress release ships every scheme below.

Six situations Brndle is built to handle

If any of these match what you're working on, you're our reader.

Brndle is not for everyone, and the site is not trying to convert every visitor. It is built for agencies and developers who are already past the page-builder era and want their themes to read like real software.

  1. Replace page builders with native blocks

    Situation

    You ship client sites and your page builder is sluggish, lock-in, and breaks at every WP update

    Outcome

    14 server-rendered Gutenberg blocks (apiVersion 3). No Elementor, no Divi, no JS lock-in. Zero KB JS on content pages.

  2. Deliver client sites faster (one theme, unlimited brands)

    Situation

    Agency dev, you fork the same theme 30 times a year and each one accumulates drift

    Outcome

    One Brndle install per client. Pick color scheme + font pair + header + footer in settings. Save & ship.

  3. Ship AI-built landing pages from the editor

    Situation

    You want Claude or GPT to draft landing-page copy but page builders fight the AI output

    Outcome

    Blocks designed for AI-friendly insertion. Drop in hero, stats, features, FAQ, CTA blocks - matches the AI mental model.

  4. Adopt Laravel + Tailwind + Vite on WordPress

    Situation

    You like the Laravel + Tailwind + Vite stack but most WP themes are jQuery + Sass + Gulp

    Outcome

    Sage + Acorn (Blade templating), Tailwind CSS v4, Vite 7. Same DX as Laravel apps, inside WordPress.

  5. Hit Lighthouse 100 on every page

    Situation

    Your client perf scores are mediocre because the theme ships 200KB of JS for a slider you never use

    Outcome

    Brndle ships ~0 KB JS on content pages. Lighthouse 100 is the baseline, not a stretch goal.

  6. Get future Astro + Ghost themes from the same shop

    Situation

    You run multi-stack clients - some on WP, some on Astro, some moving to Ghost

    Outcome

    Brndle for WordPress is shipping now. Astro + Ghost variants in the pipeline. Same design system across all stacks.

Design system

The whole vocabulary, in one page.

Every option below ships in the free release. Pick one of each in the admin panel, save, and the site renders accordingly.

12 color schemes

  • Sapphire #0369a1
  • Indigo #4f46e5
  • Cobalt #2563eb
  • Trust #0d9488
  • Commerce #16a34a
  • Signal #f59e0b
  • Coral #f43f5e
  • Aubergine #7c3aed
  • Midnight #1e1b4b
  • Stone #78716c
  • Carbon #27272a
  • Neutral #64748b

8 font pairs

  • Effortless native

    System UI

  • Workhorse modern

    Inter

  • Vercel signature

    Geist Sans

  • Technical authority

    IBM Plex

  • Friendly geometric

    DM Sans

  • Considered prose

    Editorial

  • Headline drama

    Magazine

  • Open + readable

    Humanist

8 header styles

  • Sticky

    Slides into view on scroll up, hides on scroll down

  • Solid

    Always opaque, fixed at top, never transparent

  • Transparent

    See-through over the hero, fills on scroll

  • Centered

    Logo centered, nav split left + right

  • Minimal

    Logo only, no nav (single-page sites)

  • Split

    Primary nav left, utility nav + CTA right

  • Banner

    Announcement bar above the main nav

  • Glass

    Frosted backdrop blur over hero imagery

6 footer styles

  • Dark

    Brand-dark background, light text, multi-column

  • Light

    Surface-alt background, dark text, restrained

  • Columns

    4-5 column nav with social row underneath

  • Minimal

    Single-row copyright + 4 essential links

  • Big

    Newsletter signup + 6 columns + brand statement

  • Stacked

    Mobile-first single column, even on desktop

14 native Gutenberg blocks

  • brndle/hero

    Full-width hero, eyebrow + CTAs + image + logo strip; Dark/Light/Gradient variations

  • brndle/stats

    Key metrics row ("100 Lighthouse Score", "0 KB JS")

  • brndle/features

    Alternating feature rows with images + bullets

  • brndle/content-image-split

    Side-by-side content + media block

  • brndle/how-it-works

    Numbered process steps, horizontal or vertical

  • brndle/comparison-table

    Feature comparison grid with optional highlighted column

  • brndle/pricing

    2-3 column pricing table with featured-plan highlighting

  • brndle/testimonials

    Customer testimonial cards with avatars + star ratings

  • brndle/team

    Team cards with photo, role, bio, social links

  • brndle/logos

    Trust bar with company logos or text fallback

  • brndle/video-embed

    YouTube / Vimeo / self-hosted video wrapper

  • brndle/faq

    Accessible accordion FAQ, emits FAQPage JSON-LD

  • brndle/cta

    Call-to-action banner with primary + secondary buttons

  • brndle/lead-form

    Email-capture with REST submission + Mailchimp passthrough

The benchmark, six principles

Six things every Brndle reference implementation must do, no matter the runtime.

A theme's tech stack varies. Its file system, template language, and build tooling vary. None of that is an excuse for shipping inaccessible markup, render-blocking JS, or a locked Pro tier. The Brndle theme for WordPress is one reference for the six below. The Astro, Ghost, and Shopify references will be evaluated against the same six.

  1. Sage + Acorn

    Laravel Blade templating inside WordPress. Roots ecosystem. The agency standard for modern WP themes.

  2. Tailwind CSS v4

    Utility-first, zero runtime JS, dark-mode aware, design tokens in CSS. Same vocabulary as the rest of frontend.

  3. Vite 7

    HMR dev server, optimized prod bundle, ESM-first. Builds in seconds, not minutes.

  4. Server-rendered blocks

    apiVersion 3 Gutenberg blocks rendered server-side. No client React hydration on content pages.

  5. ~0 KB JS

    Content pages ship effectively zero JavaScript. Editor blocks register in admin only.

  6. 100% GPL-2.0+

    No proprietary code, no locked features, no telemetry. Modify, fork, ship to clients without a license check.

Cross-stack roadmap

One benchmark, many runtimes.

Brndle starts on WordPress because that is where Wbcom Designs has been since 2013. The design system, the readability rules, and the accessibility bar are runtime-agnostic. Same tokens, same scheme vocabulary, same Lighthouse target, evaluated against the same six principles. Shopify, Astro, Ghost, and static-only references follow.

  1. Now

    WordPress

    Shipping

    github.com/brndle-themes/brndle - v1 with 12 schemes, 8 fonts, 14 blocks

  2. Q3 2026

    Astro

    In development

    Same readability + accessibility standard, .astro components, Cloudflare Workers deploy template

  3. Q4 2026

    Ghost

    In design

    Handlebars templates, same scheme + font + header/footer vocabulary

  4. Q1 2027

    Shopify

    Researching

    Liquid templates, OS 2.0 sections, same design system, same a11y + perf bar

  5. Later

    Static

    Exploring

    Brndle for 11ty / Eleventy / Hugo - same tokens, different runtime

Install

Three paths in. Pick one.

No license check, no activation key, no telemetry. Drop in, activate, configure in the settings panel.

  1. 01

    Release zip (recommended)

    Download brndle-x.x.x.zip from GitHub Releases. WP admin → Appearance → Themes → Add New → Upload Theme. Activate. Done.

    Download latest release
  2. 02

    From source (development)

    git clone https://github.com/brndle-themes/brndle.git \
      wp-content/themes/brndle
    cd wp-content/themes/brndle
    composer install
    npm install
    npm run build && npm run admin:build && npm run blocks:build

    Then activate in WP admin. Requires WP 6.6+, PHP 8.2+, Node 20+, Composer.

  3. 03

    Configure

    After activation, open Brndle in the WP admin sidebar. Walk the tabs (Site Identity → Colors → Typography → Header → Footer → Performance). Save. Frontend re-renders.

    Read the docs

Community + license

100% GPL-2.0+. Free to fork, modify, ship.

Brndle is published under GPL-2.0+. Use it on unlimited client sites. Modify it. Re-ship it. White-label it. The only ask: keep the license header and contribute back when you build something useful on top.

Star on GitHub Open an issue

License
GPL-2.0+, same as WordPress core
Bug tracker
GitHub Issues only, no email triage
Roadmap
GitHub Projects, public board
Contributing
PRs welcome - read CONTRIBUTING.md before opening
Maintainer
Wbcom Designs - WordPress agency since 2013

Questions we get asked

Eight answers, all visible. No accordion to click through.

Is Brndle actually free?
Yes. 100% GPL-2.0+. No paid tier, no trial, no upsell. Free release zip from GitHub Releases. The source is open at github.com/brndle-themes/brndle. Contribute, fork, modify, ship to clients - all without paying.
Why no Pro version?
The WordPress theme market does not need another locked Pro tier. Brndle ships every capability in the free version. Agencies can use it on unlimited client sites without a license check or activation key. Wbcom Designs sustains Brndle through other products and services - Brndle itself is a contribution to the WordPress commons.
What is "Lighthouse 100" specifically?
On a default Brndle install, every page (home, archive, single post, page) scores 100 in Lighthouse Performance + Accessibility + Best Practices + SEO on mobile and desktop. Achieved by zero KB JS on content pages, system-ui + variable fonts, lazy-loaded images by default, and no third-party embeds in the default config.
Does it require a page builder?
No. Brndle ships 14 native Gutenberg blocks (apiVersion 3, server-rendered). The block editor is the page builder. Elementor, Divi, Beaver Builder, Bricks, Oxygen - none required, none supported. If you need them, use a different theme.
What about Astro + Ghost themes?
Brndle for WordPress is the first ship. Brndle for Astro is in active development (target Q3 2026). Brndle for Ghost is in design (target Q4 2026). Same design system across all three - 12 schemes, 8 font pairs, the same component vocabulary. Each ships as a separate open-source project under the brndle-themes GitHub org.
Plugin compatibility?
Built-in support for Yoast SEO + RankMath (breadcrumbs, JSON-LD), WooCommerce (gallery zoom, lightbox, slider with theme-consistent wrappers), and WPML + Polylang (automatic hreflang). Brndle assumes WP 6.6+ and PHP 8.2+.
Where do I report bugs / request features?
GitHub Issues at github.com/brndle-themes/brndle/issues. We use GitHub Projects to track the public roadmap. Pull requests welcome.
Who maintains Brndle?
Wbcom Designs - WordPress agency since 2013. 4.7/5 on Trustpilot from 90+ reviews. We ship community + commercial WordPress plugins (BuddyX, Reign, Jetonomy, WPMediaVerse, Learnomy, WP Career Board) plus AI workflows for enterprise teams.

The benchmark is the contract. The themes are the proof.

Brndle for WordPress is the first proof. Astro, Ghost, Shopify and static-only references follow. Read the source, run it locally, ship it to clients - all under GPL. Per-topic benchmark writeups (readability, accessibility, performance, semantics) land alongside each reference.