Download websites that use Page Builder Framework

About Page Builder Framework

A WordPress theme that has reached 112 tagged releases is being maintained rather than merely published, and Page Builder Framework belongs in that group. First released in 2017, written in PHP and distributed under GPL v2, the theme is filed in our records under MapSteps, sits in our WordPress themes data and appears on 1,886 sites as of October 2026.

The release cadence follows from the design intent. Page Builder Framework is deliberately close to empty. The theme supplies a fast, standards-clean base and then steps aside so that a drag-and-drop builder owns the layout instead. A theme in that role has to track every builder it supports as well as WordPress core, which is why the changelog runs long while each individual entry stays narrow.

Version spread is where this becomes interesting to anyone studying WordPress maintenance behaviour. The build we record most often is 2.11.10, but a single dominant release across a long history means the remainder is scattered over installs that stopped updating at some point and never resumed. Themes are updated by whoever administers the site, never by the vendor, so a distribution of versions is really a distribution of administrative attention.

One consequence of the design is worth spelling out, because it changes what the row means. A base theme this thin is almost never the whole story on a site. Something else is drawing the layout, which means a domain in this list will usually carry a page builder plugin alongside the theme, plus whatever form, gallery and optimisation add-ons that builder pulls in behind it. The theme row is therefore a hinge rather than an endpoint, and the interesting work starts when you join it against the rest of the stack recorded for the same domain.

Two audiences care about that. Agencies and freelance developers use a theme like this as their standard starting point, so a list of sites running it is close to a list of sites built by people who work in volume and reuse the same base. Plugin and theme vendors selling into the WordPress professional market are looking at the same population from the other side, because a site on a builder-agnostic base is a site whose owner has already accepted paying for add-ons.

Detection here is inferential. Theme identity is read from asset paths and stylesheet headers that the front end has to expose, and a site behind aggressive caching, a heavy optimisation plugin or a rewritten asset pipeline can hide those markers entirely, so the recorded count should be read as a floor rather than a census. Version strings are more fragile still, because they come from files a hardened install may not serve at all.

Checking one domain tells you what one site runs. The downloadable list answers the questions that only exist in aggregate: how many sites moved off this theme between exports, which hosting providers concentrate its installs, and whether the sites stuck on old builds cluster by country or by registrar. Questions of that shape are questions about a population, and a lookup tool cannot express them.