You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/create-basic-content-type/step-1-add-configuration.md
+10-34Lines changed: 10 additions & 34 deletions
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,13 @@ The development of this tutorial is currently **IN PROGRESS**.
5
5
6
6
***
7
7
8
-
The configuration file defines the basic settings and files that compose your content type.
8
+
The configuration file defines the settings and references to your content type files. You will return to this file often to update references and change settings during the development process.
9
9
10
-
## Convention
10
+
Files referenced from the configuration include the HTML templates, the JavaScript components, the icon displayed for your content type in the Page Builder panel, and the UI component form for your content type editor within the Admin.
By convention, Page Builder requires the configuration for a content type to be in the `adminhtml` area within a directory named `pagebuilder` and a subdirectory named `content_type` or `content-type`.
13
17
@@ -16,15 +20,14 @@ The name of your configuration file should also reflect the name of your content
If your content type name uses multiple words, use underscores to separate the words in the name.
23
+
If your content type name uses multiple words, use underscores to separate the words in the name.
20
24
21
25
## Example configuration
22
26
23
-
{: .bs-callout .bs-callout-info }
24
27
In this example, only a subset of configuration elements are described (enough to understand the configuration file's basic role). For more details, refer to [Content type configurations](../configurations/content-type-configuration.md) and [Additional configurations](../configurations/additional-configurations.md).
25
28
26
29
27
-
The following configuration shows the complete configuration file for our Quote content type. An overview of these elements and attributes are described in the tables that follow.
30
+
The following configuration is from the Quote content type. An overview of these elements and attributes are described in the tables that follow.
28
31
29
32
```xml
30
33
<?xml version="1.0"?>
@@ -49,34 +52,7 @@ The following configuration shows the complete configuration file for our Quote
@@ -168,7 +144,7 @@ The `<appearance>` attributes are described as follows:
168
144
169
145
## The `elements` element
170
146
171
-
The purpose of `<elements>` as defined within an appearance is to map the data from the content type's edit form to the content type's master format so that the values entered in the form can be stored and rendered correctly on the Admin stage and storefront. These elements will be explained more fully in [Step 4: Add form](step-4-add-form.md)
147
+
The purpose of `<elements>` as defined within an appearance is to map the data from the content type's edit form to the content type's master format so that the values entered in the form can be stored and rendered correctly on the Admin stage and storefront. We will describe the `elements` in [Step 4: Add form](step-4-add-form.md)
0 commit comments