Widgets (component variables)
Give a component its own fields (text, image, select, color...) so every instance is filled in through a simple form.
A widget is a component with variables. You define fields on the component (title, image, button link, color and so on), use them inside the component, and each instance gets an Edit content form instead of free editing. The fields are defined from the component's Variables option. Each field has a type, a title, a description and a default value. Instances merge their own values with the defaults. Use widgets for blocks that non-designers fill in: team cards, pricing boxes, banners, feature rows.
How it works
- Field types (html list.settings): Input, Textarea, Select, Image, File, Toggle, Options, Date, Color, Repeater (BLOCKS), Component.
- Per field: Title, Description, Default Value; Select and Options also take a list of options (title/value).
- Field names are slugged; a duplicate name is refused ('Provided name alredy exist.').
- Inside the component the values are available to dynamic text and attributes as the 'widget' object (mdVars merge sets data.widget), for example widget.<field>.
- Each instance stores its values as JSON in the instance's text slot; mdVars merge fills missing keys with defaults and drops keys that are no longer defined.
- An instance of a component with variables shows an 'Edit content' button in the Content panel; the canvas locks its inner elements (dh-lock).
- Stored on the component.
- MCP limits: variable names a-z A-Z 0-9 - _, max 40 characters; at most 50 variables; at most 500 strings of up to 2000 characters; no ${...} in values.
When to use it
- A team member card with name, role and photo fields
- A pricing box whose plan name, price and features are filled per instance
- A banner where editors choose a color from a Select
Limitations
- Inner elements of a widget instance cannot be edited directly on the canvas.
Availability
- Works in Designer and MCP.
- Included in every plan.
- Limits: MCP only: max 50 variables per component, names up to 40 characters, strings up to 2000 characters.
How to use it.
- Right click the component in the Components tab and choose Variables.
- Create a field, pick its type and set a default value.
- Bind the field inside the component (dynamic text or attribute using widget.<field>).
- Select an instance and click Edit content to fill in its values.
Questions.
What field types can a widget have?
What happens to instances when I add a field?
Related features.
Component repeater field
A repeater field inside a widget lets each instance hold a list of items, rendered by repeating an element.
Nested components
Put instances of components inside other components, or let a widget field choose which component to render.
Reusable components
Turn any group of elements into a named component you can reuse across every page of the site.
Browse other features
Designer
Bring your ideas to life with our visual website builder. Drag and drop with ease, or dive into coding when needed.
→AI Studio
Describe it and AI builds it. Every change lands in the same project you can open in the Designer.
→MCP
Connect Claude Code, Cursor or any MCP client and build whole sites with your own agent.
→CMS
Create, organize, and manage your dynamic content with the maximum freedom and flexibility of our visual CMS.
→SEO
Divhunt delivers ultra-fast & structured sites that are good for ranking by default, while offering complete control for customization.
→REST API
Easily link to any REST API endpoint with instant preview and expand your site’s functionality smoother than ever before.
→Plugins
Divhunt offers an open platform for creating plugins to upgrade features, add new capabilities, and simplify building better sites.
→Localization
Localize everything from static pages and CMS content to URLs and metadata, in up to 15 languages with no add-on.
→Interactions
Visually create animations and interactions with a simple, intuitive timeline. Build smooth, engaging experiences without code.
→Custom Files
Manage JS and CSS files with a structure developers love, combining folders and clean organization.
→Memberships
Create plans, decide who sees what and connect it all to your CMS. Build courses, communities or client portals.
→