Skip to content

FrameThe Last Page Builder You'll Ever Need. Drupal Edition.

Editors build pages by dragging the components your theme already has. Drupal renders them. Works with SDC and UI Patterns 2 components, Paragraphs, Token, Metatag and an AI chat that builds the page for you. Free and open source.

Frame

Watch a page get built ​

The AI assistant rebuilds the homepage of Umami from the theme's components. A React component is dragged into the middle of it and set up with the mouse, copied to a new page, and two editors work on that page at once. Then the files of the component: YAML, Twig and React. Turn the subtitles on for the narration.

Old way, new way ​

Both ways end at the same component; Frame reads its schema for the restOld way: Paragraph firstNew way: component onlyDesignSchema, fieldsParagraph typeTwig templateor a field mappingDesignno paragraph type, no Twig glueComponent*.component.ymlFrame, from the component's schema, for both waysfields in the editor Β· storage Β· rendering Β· translations Β· versions and migrations Β· the AI assistant
Old way
  1. Design
  2. Schema and fields
  3. Paragraph type
  4. Twig template
  5. Component
New way
  1. Design
  2. Component

Frame does the rest from the component's schema: fields in the editor, storage, rendering, translations, versions and migrations, the AI assistant.

The old way keeps working: paragraph types are blocks of the editor, edited with their own form and rendered by their templates. Use it where content needs Drupal fields, revisions or reuse outside pages. For the rest, write the component once and place it.

Why this one is the last ​

It is your design system, not ours ​

The editor has no blocks of its own to restyle. It reads the components of your theme, and spacing, colours, type scale, sizes and breakpoints from the theme's design tokens. Editors can only pick what the design allows, and your SCSS uses the same values.

It is Drupal all the way down ​

Fields with any formatter, views, blocks, the Media Library, responsive images, translations, revisions, content moderation. The content form in the editor is Drupal's node form, with every widget.

Nothing of the editor on the published page ​

Drupal renders the layout as normal SDC markup. Visitors load your components and nothing else: no editor code, no runtime of the editor.

No lock-in ​

Components are core SDCs and work in Twig without the editor. Content in paragraphs and fields stays in paragraphs and fields. The layout is JSON on the page, with versions and migrations for your components.

Works with what your site already runs ​

What you get in the editor
Single Directory Components (core)every component of the theme and its base themes as a block; a ready set in the base theme: hero, card, columns, accordion, call to action…
UI Patterns 2its components are core SDCs, so a theme's existing component library is offered as it is
Paragraphs and Paragraphs Libraryparagraph types as blocks with their own form; shared paragraphs from the library, with revisions
Tokenautocomplete and a token browser in text fields; core tokens, the Token module's and the ones other modules add
Metatagmeta tags on landing pages, filled by the assistant on request
AIa chat in the editor that builds and changes pages, with any provider of the AI module
Media Library, Responsive Imagepictures picked from the media library, with image styles and responsive image styles
Views and blocksany view or Drupal block placed on the page; a view can be drawn by an interactive component
Entity Usagewhere media, paragraphs and saved blocks are used
Content Moderation, translationsdrafts, workflow states and translated layouts

In the editor ​

AI assistant
AI assistantAsk for a page, get one made of your components.
Fields from props
Fields from propsEach prop of a component is a field.
Layout and style
Layout and styleSpacing, size, alignment and background from the theme's tokens.
Paragraphs
ParagraphsA paragraph, edited with its own form.
Tokens
TokensThe token browser.
Library
LibrarySaved blocks, reused on other pages.
Preview
PreviewThe page at the theme's breakpoints.
History
HistoryEvery change, one click to go back.
Published
PublishedThe page, rendered by Drupal.

All of them, with explanations: Gallery.

One command sets a site up ​

With the theme in themes/contrib/frame (Getting started), a recipe adds the Landing page content type, media, responsive images, paragraphs with the library, meta tags, the assistant and a role for editors:

bash
composer require drupal/paragraphs drupal/entity_usage drupal/field_group drupal/metatag drupal/ai
drush recipe themes/contrib/frame/recipes/frame_editor_full --input=frame_editor.theme=my_theme

Take only what you need: each part is its own recipe. The whole way from an empty Drupal to a published page is in Build a site.

Interactive components use React ​

Components that need behaviour in the browser (filters, tables, tooltips) are written in React and stay normal Drupal components: place them in the editor or in Twig. A React component is a *.component.yml, a Twig file with the mount point and an index.jsx with a Drupal behavior. Nothing else to register: the build finds the folder. See Creating a component and React + Drupal behaviors.