A toolkit, not a theme skin

APB is a set of Drupal paragraph types with a shared field vocabulary: width, columns, color style, intro, container. Learn one component and the next one feels familiar. That is the whole product idea, and it is why we did not ship fifty layouts.

Version 2.1.0 is what this site runs. The modules are tagged. Composer lock is committed. A client install is the same graph of packages, pointed at their database.

Fifteen components

Each card opens the frozen example page for that component. We leave those pages alone so documentation and this product site do not drift apart.

Accordion

Stack long answers so a page stays readable until someone wants the detail.

Carousel

Walk a visitor through a set of stories without dumping every image on the page at once.

Feature box

Cards with a photo, a line of copy, and a place to send people next.

Image gallery

A grid that opens in a lightbox. Crops stay consistent because the editor never bypasses them.

Infinite logos

A quiet strip of marks that keeps moving. Useful when the proof is the company you keep.

Links

Lists that can be plain, overlay, or thumbnail. The editor picks the density.

Overlay content

Open a deeper piece without leaving the page. Good for video and for the extra paragraph nobody wants in the hero.

Profiles

People, with a photo and a bio that opens when you actually want it.

Read more

Keep the first screen honest. Let the rest of the copy wait behind a control.

Simple content

Columns, images, backgrounds, and the odd full-bleed band when the page needs air.

Slideshow

A full-width opening that can take a photo, a video, and a sentence that has to land.

Special list

Icon, title, a little body. The workhorse for “here is what you get.”

Tabs

Related chunks side by side. On a phone they become an accordion, which is the right call.

Video

File or remote. Grid or player. The media library stays in charge of the file.

Views

Drop an existing Drupal View into the page as itself or as boxed cards.

Who it is for

You work in the paragraph field. You do not ask for a new content type every time marketing wants a band of cards. If a component is missing a control you need weekly, that is feedback we want — that is how the last eight years of fields got here.

Config lives in the modules. Releases are tags. You do not fork Twig on the client site to “tweak the gallery.” If the gallery is wrong, the fix goes to git.aero.net and comes back through Composer, the same way Drupal core does.

Membership groups, education, nonprofits, foundations. The sites that have to explain, enroll, and keep records. APB will not replace your CRM. It will stop the public pages from becoming a second, worse CMS next to it.

Next

Request a demo
Talk to Aero