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
1.**Add configuration**: Create an XML file to define your content type and reference the other files that control the appearance and behavior of your content type.
41
-
2.**Add templates**: Create HTML templates that define the appearance of your content types on the Admin stage (preview.html) and the storefront (master.html).
41
+
2.**Add templates**: Create HTML templates that define the appearance of your content types on the Admin stage (`preview.html`) and the storefront (`master.html`).
42
42
3.**Add component**: Create a JavaScript file that defines the behavior of your content type on the Admin stage (preview.js) and the storefront (master.js).
43
43
4.**Add form**: Create a UI component form and a layout so users can edit your content type within the Page Builder editor.
44
44
5.**Add styles**: Create LESS files to style your content types when rendered in the Admin UI and on the storefront.
@@ -55,4 +55,4 @@ Before we get started, take a look at what you will be building. The directory s
55
55
The `PageBuilderQuote` module structure represents an overview of the conventions used for content types. Many of these conventions are simply those defined for developing UI components. However, the conventions specific to Page Builder content types appropriately start within the directories called `content_type` or `content-type`. Page Builder instantiates a content type from the files defined within these directories. We will discuss these content type conventions within each step of the process.
0 commit comments