Layout Builder Kit

Introduction

Layout Builder Kit is a project of Performant Labs. Our other projects are:

• Campaign Kit, a flexible donation system made entirely in Drupal

• Payment Stripe, a Payment module plugin for Campaign Kit

• and the Drupal Quality Initiative, a standards system to help teams and module builders improve the code they ship.

The kit has the following components:

• Book Navigation

• Icon Text

• Image

• Rich Text

• Tab

• Video

In Drupal 8, you will see the words Block and Component used interchangeably; they are the same thing for our purposes.

Be sure to read the Known Issues. If there is a bug that's not known yet, please file a bug.

Some sites like to use Asset Injector to make page-specific theme CSS and Javascript customizations. Be careful, using this too much makes the site brittle and it can become difficult to track down errors. Do your best to keep theme changes in the primary CSS file of the site theme.

Other Layout Builder Kit Resources

The slide deck for BADCamp 2019 is "Start using the Emerging Layout Builder Ecosystem." The video is coming soon.

Did you know that Paragraphs has an Ecosystem, Too?

Testing a SimplyTest.me

1. Go to "SimplyTest.me."

2. Select "layout_builder_kit" and the latest version.

3. Click "Launch sandbox;" let the sandbox initializ.

4. From the Drupal screen that appears, login with:

   1. Username: admin

   2. Password: admin

5. Add Layout Builder components via Structure > Block layout OR by enabling Layout Builder on a content type and adding components to the layout of that content type.

Contributing New Components

We are happy to consider adding your component to the kit but create an issue so we can discuss your ideas first.

When coding, follow the lead of the other components and use these guidelines:

1. Subclass the class LBKBaseComponent. This is where common functionality goes, like the title, the class textfield and multilingual support (in the future).

2. Use LBK as the class prefix to prevent name collisions with other component libraries.

3. Make sure it meets Drupal Quality Initiative Level 1.