## Passing dicts to module parameters
For modules with fields that expect dicts, you can pass them like you would other parameters. If it's cleaner to you or you plan to re-use the values, you can set the dict to a variable, and pass the variable to the parameter instead.
```jinja theme={null}
{% module "social_buttons",
path="@hubspot/social_sharing",
email={
"default": true,
"enabled": false,
"img_src": "https://..."
}
%}
```
### Passing fields that have dnd associated parameters
[Drag and drop tags](/cms/reference/hubl/tags/dnd-areas), such as `dnd_area`, come with a set of default parameters, such as `width`. While the design manager will prevent you from creating new fields that use one of these reserved parameters, modules created before drag and drop tags were introduced may already use a reserved parameter.
To fix this, you can use the `fields` parameter. Just like you would pass field data to a group, you can pass the field name as a key on the `fields` object. Its value must be consistent with the format the field type expects.
```jinja theme={null}
{% dnd_area "main_content" %}
{% dnd_section %}
{% dnd_column %}
{% dnd_row %}
{% dnd_module path="@hubspot/divider",
fields={width: "90"}
%}
{% end_dnd_module %}
{% end_dnd_row %}
{% end_dnd_column %}
{% end_dnd_section %}
{% end_dnd_area %}
```
## Setting default field values in templates
You can set default values for module fields at the template level by including parameters in the `dnd_module` tags. Below, learn how to set default field values in nested field groups, repeating fields, repeating field groups, and style fields.
### Nested field groups
Below is an example of a custom drag and drop module with a custom `style` field group containing other nested field groups. Compare its template-level configuration with how this same grouping would appear in the design manager.
```jinja theme={null}
{% dnd_module
path="/Nested_Module.module"
style={
"group":{
"section":{
"color_field":{
"color" : "#000",
"opacity" : 100
}
}
}
}
%}
{% end_dnd_module %}
```
### Repeating fields
You can set template-level default values for repeating fields by passing an array to the field's parameter. The array's items must be in the format expected based on the [field type](#field-based-parameters). For example:
* A simple text field only expects a string
* An image repeater field expects an image field object. This applies to [all of the other field types](#field-based-parameters).
```jinja theme={null}
{% module "recipe_card"
path='../modules/recipe_card.module',
ingredients=["Eggs","Ham","Cheese"]
%}
{% module "my_repeater_module"
path="/img_repeater_module",
label="img_repeater_module",
image=[
{
"src" : "https://www.hubspot.com/hubfs/WBZ%202025%20Rebrand/Hub%20Logos/Icons%20SVGs/marketing-hub-logo-small.svg",
"alt" : "Marketing Hub Logo",
"width" : 80,
"height" : 80
},{
"src" : "https://www.hubspot.com/hubfs/WBZ%202025%20Rebrand/Hub%20Logos/Icons%20SVGs/sales-hub-logo-small.svg",
"alt" : "Sales Hub Logo",
"width" : 80,
"height" : 80
}
]
%}
```
### Repeating field groups
Modules that contain repeating groups of fields, like you might see in a slideshow module or FAQ module, can have a template-level default set for those groups. To do this, pass an array of objects to your field group's parameter. The key-value pairs of the object are the field names and their values.
```jinja theme={null}
{% module path='../modules/slideshow.module',
slides=[
{
"caption":"Cute dog looking up",
"image_url":"http://example.com/image.jpg",
},
{
"caption":"Cuter cat not looking amused",
"image_url":"http://example.com/image2.jpg",
}
]
%}
```
### Style fields
you can explicitly set default values for [style fields](/cms/reference/fields/overview#style-fields) using the `styles` parameter.
This works just like other groups do, where the parameter is the name of the group. You pass an object to that parameter with all of the fields you wish to set.
```jinja theme={null}
{% dnd_module
path="./path/to/module",
styles={
"background_color":{
"color":"#123",
"opacity":50
}
}
%}
```
## Block syntax
While most modules have parameters that control default content, there may be situations where you need to add large code blocks to the default content of a module. For example, you may want to include a large block of HTML as the default content for a rich text or HTML module. Rather than trying to write that code into a value parameter, insert the module using a `{% module_block %}` tag, then include within it a `{% module_attribute %}` tag that specifies content by the name of the field.
As an example, the following code would insert a custom `` element into the `html` field of a default rich text module instance. ```jinja theme={null} {% module_block module "my_rich_text_module" path="@hubspot/rich_text", label="rich_text.module" %} {% module_attribute "html" %}
Hello there!
{% end_module_attribute %} {% end_module_block %} ``` Older HubSpot templates may contain the deprecated `widget_block`, `widget_attribute`, and `type_of_module` parameters. These parameters have been replaced by `{% module_block %}`/`{% module_attribute %}`. Learn more by expanding the section below.Add content here.
{% end_widget_attribute %} {% end_widget_block %} ```Hi {{ contact.firstname }},
Describe what you have to offer the customer. Why should they read? What did you promise them in the subject line? Tell them something cool. Make them laugh. Make them cry. Well, maybe don't do that...
Use a list to:
LINK TO A LANDING PAGE ON YOUR SITE (This is the really important part.)
Now wrap it all up with a pithy little reminder of how much you love them.
Aw. You silver-tongued devil, you.
Sincerely,
Your name
{% end_content_attribute %} ``` ## Parameters available for all modules While some modules have certain [special parameters](/cms/reference/hubl/tags/standard-tags), below is a list of parameters supported by all modules. | Parameter | Type | Description | Default | | ---------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `label` | String | The name of the module displayed in the content editor. This parameter can also be used to give users additional instructions. | | | `overrideable` | Boolean | Controls whether or not the module can be edited in the content editor, equivalent to the *Prevent editing in content editors* setting in the design manager. | `True` | | `no_wrapper` | Boolean | When set to `True`, removes the wrapping markup from around the content of a module.On pages, modules are always wrapped in a `