This project is not covered by Drupal’s security advisory policy.
Frame lets content editors compose whole pages visually from the components of your theme, without asking a developer and without being able to break the design. Developers keep writing components the way they already do, as core Single Directory Components, and every one of them is a block in the editor the moment it exists.
Unlike builders where components are created and styled in the browser, in Frame components live only in code: a YAML file, a Twig template and CSS, in git, reviewed and deployed with the theme. The builder is design-system oriented: spacing, colours, type scale, sizes and breakpoints are declared once as the theme's design tokens, editors pick from those and nothing else, and the theme's SCSS reads the same values. Drupal renders the published page as normal component markup, so visitors load no editor code.
Interactive parts do not need a decoupled front end. A component that needs behaviour in the browser, such as a filter, a table or a tooltip, is the same kind of component with a small React bundle: one React per page, working after ajax, in modals and with BigPipe, and fed by Views as its JSON API. Teams get one component library for the design system, the page builder and the interactive widgets.
Features
- SDC components as blocks, with nothing to register: props become fields, slots become drop zones. Components written for UI Patterns 2 are SDCs and work too.
- AI assistant: a chat that builds a page from your components, checks the result and corrects it (AI module, any provider).
- Paragraphs as blocks, edited with their own form, and shared across pages through the Paragraphs Library.
- Tokens in every text field, with autocomplete and a token browser (Token module supported).
- Metatag on landing pages, filled by the assistant on request.
- Fields, Views and Drupal blocks on the canvas; fields with any formatter.
- Media Library pictures with image styles and responsive image styles.
- Layouts: columns, flex, stack, with spacing, size, alignment and background from the theme's tokens.
- Library of saved blocks, reused linked or as a copy, with usage tracking (Entity Usage).
- Preview at the theme's breakpoints, undo and redo, a history of changes, drafts kept per user.
- Translations, revisions and content moderation for layouts.
- React components with a shared build and test setup: a subtheme needs no Vite or Jest config of its own.
- Recipes that set a site up in one command, and a ready set of components: hero, card, columns, accordion, call to action and more.
Project information
- Ecosystem: UI Builder, Starter Builder Frontend Theme
- Created by zviryatko on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
