Skip to content

Commit 3dc860a

Browse files
committed
PB-461: Fixed reference typo in extension docs
1 parent 4bc0b5b commit 3dc860a

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/extend-existing-content-type/step-3-extend-forms.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
# Step 3: Extend forms
22

3-
In this step, you will customize the Banner form (`pagebuilder_banner_form.xml`) by adding a form field for entering a `max-height` value for the `collage-left` and `collage-right` appearances.
3+
In this step, you will customize the Banner form (`pagebuilder_banner_form.xml`) by adding a form field for entering a `max-height` value for the `collage-left` and `collage-right` appearances.
44

55
## Create the appearance form
66

77
Page Builder forms are UI component forms. This means they follow the same conventions as any other UI component form in Magento. If you are not already familiar with UI component forms, you can learn more about them from the [UI Components Guide](https://devdocs.magento.com/guides/v2.3/ui_comp_guide/concepts/ui_comp_xmldeclaration_concept.html). For this tutorial, we provide you with the basic markup for setting up an empty form.
88

9-
Your file structure for the Banner extension form and corresponding layout should look like this:
9+
Your file structure for the Banner extension form and corresponding layout should look like this:
1010

1111
![Extension forms file structure](../images/extension-forms-files.png){:width="544px" height="auto"}
1212

1313
### Extension form
1414

15-
When customizing an existing form, make sure you name your form with the same name as the existing content type's form. In our case, we are customizing the Banner's form, which means we must name our form: `page-banner-form.xml`. Here's the basic XML configuration for the Banner form extension:
15+
When customizing an existing form, make sure you name your form with the same name as the existing content type's form. In our case, we are customizing the Banner's form, which means we must name our form: `pagebuilder-banner-form.xml`. Here's the basic XML configuration for the Banner form extension:
1616

1717
```xml
1818
<?xml version="1.0" encoding="UTF-8"?>
@@ -45,17 +45,17 @@ When customizing an existing form, make sure you name your form with the same na
4545
</settings>
4646
</dataProvider>
4747
</dataSource>
48-
48+
4949
<!--Add Fieldsets and fields-->
50-
50+
5151
</form>
5252
```
5353

5454
## Add fieldsets and fields
5555

5656
Before you add a field to the form of an existing content type, you need to know where to add it. In other words, you need to decide which fieldset to put your field in. We want to put our new `max_height` field below the Banner's existing `min_height` field, which is in the the `appearance_fieldset`.
5757

58-
The markup for adding the field to the fieldset looks like this:
58+
The markup for adding the field to the fieldset looks like this:
5959

6060
```xml
6161
<fieldset name="appearance_fieldset"

0 commit comments

Comments
 (0)