MC-6271: Add docs for content type forms

Merged with MC-6270

Author: bdenham

docs/configurations/option-menu-configurations.md

@@ -1,4 +1,8 @@
 # Option menu configurations
 
-{: .bs-callout .bs-callout-info }
-The development of this topic is currently **IN PROGRESS**.
+---
+
+The development of this topic is currently **IN PROGRESS**.
+
+---
+

docs/create-basic-content-type/step-3-add-components.md

@@ -5,11 +5,38 @@ The development of this tutorial is currently **IN PROGRESS**.
 
 ***
 
-Components are the JavaScript files that define the behaviors of your content type when they appear on the stage in the Admin UI (using the `preview.js` component) and in the storefront (using the `master.js` component). As such, they are complementary to the templates you added previously in Step 2, acting as the view models to the template's views. 
+In this step, we will create a preview component in order to show you how to customize the Quote options menu.
 
-## Configuration
+## About components
 
-In your configuration file, reference your JavaScript component (`preview.js`) as shown here within the `type` element:
+Components are the JavaScript files that define the behaviors of your content type when they appear on the stage in the Admin UI (using the `preview.js` component) and in the storefront (using the `master.js` component). As such, they are complementary to the templates you added previously in Step 2, acting as the view models to the template's views.
+
+Custom component files are completely optional. If they are not added to your content type, Page Builder will use these defaults:
+
+- Default preview component: `Magento_PageBuilder/js/content-type/preview`
+- Default master component: `Magento_PageBuilder/js/content-type/master`
+
+Reasons for adding your own preview component include customizing options menus and adding user-interactivity that your content type needs to fulfill its function when displayed on the Admin stage. Adding your own master component is necessary if you want to... **[Reviewer: please give some examples of when custom master components might be necessary.]**
+
+## Component conventions
+
+The conventions for naming your components and adding them to your module are as follows:
+
+- Your preview component must be named `preview.js` and placed here in your module (`view/adminhtml/web/js/content-type/example-quote/`):
+
+  ![Create config file](../images/step3-add-component.png)
+
+- Your master component must be named `master.js` and placed here in your module (`view/frontend/web/js/content-type/example-quote/`):
+
+  ![Create config file](../images/step3-add-master-component.png)
+
+We will not create a master component for our Quote example, but the location is given here if you need to include one for more complex content types.
+
+Before continuing, add the preview component file (``preview.js`) to your `PageBuilderQuote` module within the directory structure noted.
+
+## Component configuration
+
+In your configuration file, reference your Admin `preview_component` (`preview.js`) as shown here:
 
 ```xml
 <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
@@ -24,20 +51,136 @@ In your configuration file, reference your JavaScript component (`preview.js`) a
 </config>
 ```
 
-The following table describes each component-related attribute from the Quote configuration.
+A description of each component-related attribute from the Quote configuration follows:
 
 | Attribute           | Description                                                  |
 | ------------------- | ------------------------------------------------------------ |
 | `component`         | There are two component types to choose from: `content-type` and `content-type-collection`. Use `Magento_PageBuilder/js/content-type` for static content types that do not have children (like our Quote). Use `Magento_PageBuilder/js/content-type-collection` for content types that can contain children (container content types). |
-| `preview_component` | Optional. The `preview.js` file provides rendering logic to the Admin preview template. If your content type does not require any changes to the standard option menu (shown on mouseover) for a content type or other user-interactivity in the Admin, you can omit this attribute from the the `type` element. When you omit this attribute, Page Builder will use `Magento_PageBuilder/js/content-type/preview` by default. |
-| `master_component`  | Optional. The `master.js` file provides rendering logic to the master format storefront template. As with the `preview_component`, if your content type does not require any specific user-interactivity or other behavior when it's displayed in the storefront, you can simply omit this attribute from the the `type` element. When you omit this attribute, Page Builder will use `Magento_PageBuilder/js/content-type/master` by default. In |
+| `preview_component` | Optional. The `preview.js` file provides rendering logic to the Admin preview template. If your content type does not require any changes to Page Builder's standard rendering logic, you can omit this attribute from the the `type` element. When you omit the attribute, Page Builder will use `Magento_PageBuilder/js/content-type/preview` by default.<br /><br />However, if you want to make changes to the option menu for your content type, or other customize other user-interactivity in the Admin, you need to create your own preview component as we have done for the Quote content type. |
+| `master_component`  | Optional. The `master.js` file provides rendering logic to the master format storefront template. As with the `preview_component`, if your content type does not require any specific user-interactivity or other behavior when it's displayed in the storefront, you can simply omit this attribute from the the `type` element. When you omit the attribute, Page Builder will use `Magento_PageBuilder/js/content-type/master` by default. <br /><br />In the Quote configuration, the `master_component` attribute is only included for discussion. It simply points to the Page Builder default `master.js` component that would be used the attribute was omitted. |
+
+## Quote `preview_component`
+
+The Quote `preview_component`  (`preview.js`) example is shown here in full for you to copy into your `preview.js` file, followed by an explanation of its key parts. 
+
+```js
+define([
+  'Magento_PageBuilder/js/content-type/preview',
+], function (PreviewBase) {
+  'use strict';
+  var $super;
+
+  function Preview(parent, config, stageId) {
+    PreviewBase.call(this, parent, config, stageId);
+  }
+
+  Preview.prototype = Object.create(PreviewBase.prototype);
+  $super = PreviewBase.prototype;
+
+  Preview.prototype.retrieveOptions = function retrieveOptions() {
+    var options = $super.retrieveOptions.call(this, arguments);
+    //console.log(options);
+
+    // Change option menu title
+    options.title.preview.config.label = "Quote Menu";
+
+    // Change option menu icons
+    options.remove.icon = "<i class='icon-admin-pagebuilder-error'></i>";
+
+    // Change tooltips
+    options.edit.title = "Open Editor";
+    options.remove.title = "Delete";
+    // options.move.title = "Move";
+    // options.duplicate.title = "Duplicate";
+
+    // Remove menu options
+    // delete options.move;
+    // delete options.duplicate;
+    // delete options.edit;
+    // delete options.remove;
+
+    return options;
+  };
+  return Preview;
+});
+```
+
+### Extend from `Preview`
+
+The first thing we do in our preview component is extend Page Builder's `Preview` class (`magento2-page-builder/app/code/Magento/PageBuilder/view/adminhtml/web/ts/js/content-type/preview.ts`) by declaring it as a dependency and calling it from the preview component's constructor as follows:
+
+```js
+define([
+  'Magento_PageBuilder/js/content-type/preview',
+], function (PreviewBase) {
+  'use strict';
+  var $super;
+
+  function Preview(parent, config, stageId) {
+    PreviewBase.call(this, parent, config, stageId);
+  }
+
+  Preview.prototype = Object.create(PreviewBase.prototype);
+  $super = PreviewBase.prototype;
+```
+
+You don't have to extend `Preview` this way, but if you do, you get access to both its public and protected functions. In our Quote example, we need access to one protected function, discussed next.
+
+### Customize the options menu
+
+Our goal for the Quote preview component is to customize the default Page Builder options menu for a content type, as shown here:
+
+![Create config file](../images/options-menu-default.png)
+
+To do this, we need to override the protected `retrieveOptions()` function from the `Preview` class so we can change various options as shown here: 
+
+```js
+Preview.prototype.retrieveOptions = function retrieveOptions() {
+  var options = $super.retrieveOptions.call(this, arguments);
+  //console.log(options);
+
+  // Change option menu title
+  options.title.preview.config.label = "Quote Menu";
+  
+  // Change option menu icons
+  options.remove.icon = "<i class='icon-admin-pagebuilder-error'></i>";
+
+  // Change tooltips
+  options.edit.title = "Open Editor";
+  options.remove.title = "Delete";
+  // options.move.title = "Move";
+  // options.duplicate.title = "Duplicate";
+
+  // Remove menu options
+  // delete options.move;
+  // delete options.duplicate;
+  // delete options.edit;
+  // delete options.remove;
+
+  return options;
+};
+```
+
+In the preceding code, we made changes to the options menu title, icons, and tooltips. You can also remove options from the menu. For example, if you don't want end-users to move or duplicate your content type, you can remove those options from your menu using `delete options.move` and `delete options.duplicate` as shown commented out in the code.
+
+![Create config file](../images/options-menu-custom.png)
+
+{: .bs-callout .bs-callout-info }
+Even though you can change the base option menu properties as described, we suggest you stick the the default options as much as possible to provide end-users with a consistent experience across Magento's content types and other third-party content types that are included as time goes on.
+
+### Other changes
+
+Other changes and additions you can make to your preview component include:
+
+**[Reviewer: Please include a list of other changes or additions that developers might make in their own preview component]**
+
+
 
-## Location
+## Quote `master_component`
 
-Add them to your module here (`view/adminhtml/web/js/content-type/example-quote/`):
+As mentioned previously, our Quote content type has no need for a master.js component file. Instead, we are using Page Builder's default master component file: `Magento_PageBuilder/js/content-type/master`. More information on master components and their usage can be found **[where?]** 
 
-![Create config file](../images/step3-add-component.png)
+## Next
 
-## Create preview component
+[Step 4: Add form](step-4-add-form.md)
 
-The remainder of this topic is in progress.