It took the long way here

Aero has been building Drupal sites for organizations that cannot treat the homepage as a campaign that expires. Editors needed to change a band of cards without opening a ticket. Developers needed those bands to remain a module, not a paste of Twig in the theme.

APB started as that tension on client projects. It spent years as v1 on production properties. Version 2 is the rebuild for Drupal 11: the same job, cleaner field contracts, a distribution you can actually install twice and get the same site.

We still take feedback the old way. Someone tries to build a page, gets stuck, and we either teach the component or we change it. Eight years is a lot of stuck. That is why the field lists look the way they do.

Timeline from 2018 to 2026: client sites, editor feedback, Drupal 11, APB 2.1.

What goes on a client site

Not a plugin marketplace. A Composer project, a profile, and the components you enable.

The distribution

apbuilder_distribution installs Drupal, the APB stack, Gin, and the example content if you want it.

The host field

field_apb_pb_paragraphs on the content types you choose. Page, article, a custom bundle. Editors work there.

The theme

apbuilder_theme is a starting point. Client sites often sub-theme it. Tokens stay in settings, not in a pile of hex in CSS.

Next

Request a demo
Talk to Aero