MC-5769: Complete content type tutorial

bdenham · bdenham · commit 16c79db3e6fe · 2018-12-08T11:16:56.000-06:00
Syncing link fixes with devdocs_internal
diff --git a/docs/configurations/panel-configurations.md b/docs/configurations/panel-configurations.md
@@ -17,9 +17,6 @@ These groups are defined in the Page Builder `group.xml` file and can be extende
 ## Overview
 
 This topic describes four ways to customize the Page Builder panel:
-
-- [Panel groups and configurations](#panel-groups-and-configurations)
-    - [Overview](#overview)
     - [Rename panel groups](#rename-panel-groups)
     - [Reorder panel groups](#reorder-panel-groups)
     - [Add new panel groups](#add-new-panel-groups)
diff --git a/docs/create-basic-content-type/step-2-add-templates.md b/docs/create-basic-content-type/step-2-add-templates.md
@@ -55,7 +55,7 @@ Content types cannot be rendered without these templates. Add them to your modul
 
     ![Admin preview.html template](../images/drag-content-type-to-stage.png) 
 
-    Notice that you also have an options menu when you hover over your content type. This is provided by including the `<render args="getOptions().template" />` within your `preview.html` template. See [Option menu configurations](option-menu-configurations.md) for more details.
+    Notice that you also have an options menu when you hover over your content type. This is provided by including the `<render args="getOptions().template" />` within your `preview.html` template. See [Option menu configurations](../configurations/option-menu-configurations.md) for more details.
 
 ## Create the `master_template`
 
diff --git a/docs/how-to/how-to-add-custom-toolbar.md b/docs/how-to/how-to-add-custom-toolbar.md
@@ -13,7 +13,7 @@ To add a custom toolbar to a Page Builder content block:
 1. [Add a toolbar configuration](#toolbarConfig)
 2. [Add a toolbar template](#toolbarTpl)
 
-## Add a toolbar configuration
+## Add a toolbar configuration {#toolbarConfig}
 
 To add a Toolbar configuration to your content block, you need to create a new instance of the `Toolbar` class, then add configuration options to it. 
 
@@ -63,7 +63,7 @@ Option property descriptions:
 | `label`             | Label of the option. If no icon is specified, this will be displayed               |
 | `icon`              | Name of CSS class to use for the icon.                                             |
 
-## Add toolbar template
+## Add toolbar template {#toolbarTpl}
 
 In your content block template, add the toolbar events to your main toolbar container, and insert the toolbar template:
 
diff --git a/docs/how-to/how-to-develop-container-content-type.md b/docs/how-to/how-to-develop-container-content-type.md
@@ -9,7 +9,7 @@ Each container group has 3 containers in a grid and styled differently based on
 
 ## Before you begin
 
-For creating a generic content type and content type collection, see [How to add a new content type][].
+For creating a generic content type and content type collection, see [How to develop a new content type][].
 
 Make sure you know how to register your custom module.
 See [Register your component](https://devdocs.magento.com/guides/v2.2/extension-dev-guide/build/component-registration.html) in devdocs.
@@ -1027,7 +1027,7 @@ Use the configuration form in the container group's edit panel to switch between
 
 ![Custom Containers Form](../images/custom-containers-form.png)
 
-[How to add a new content type]: how-to-add-new-content-type.md
+[How to develop a new content type]: how-to-develop-new-content-type.md
 [Register your component]: https://devdocs.magento.com/guides/v2.2/extension-dev-guide/build/component-registration.html
 [custom container]: #custom-container
 [custom container group]: #custom-container-group
diff --git a/docs/how-to/how-to-use-image-uploader.md b/docs/how-to/how-to-use-image-uploader.md
@@ -7,15 +7,11 @@ This topic describes how to add a reusable image uploader component to the PageB
 ## Overview
 
 To add image uploader customization to PageBuilder:
-
-- [How to use the Image Uploader](#how-to-use-the-image-uploader)
-    - [What's in this topic](#whats-in-this-topic)
-    - [Overview](#overview)
     - [Add configuration for the uploader](#add-configuration-for-the-uploader)
-    - [Update the `<YourModule>/view/adminhtml/web/js/content-type/<content_type_name>/preview.js` file {#js-file}](#update-the-yourmoduleviewadminhtmlwebjscontent-typecontenttypenamepreviewjs-file-js-file)
-    - [Update the preview template to display the uploader component {#preview}](#update-the-preview-template-to-display-the-uploader-component-preview)
+    - [Update the `<YourModule>/view/adminhtml/web/js/content-type/<content_type_name>/preview.js` file {#js-file}](#js-file)
+    - [Update the preview template to display the uploader component {#preview}](#preview)
 
-## Add configuration for the uploader
+## Add configuration for the uploader {#add-configuration-for-the-uploader}
 
 Use `additional_data` in your `<YourModule>/view/base/pagebuilder/content_type/<content-type-name>.xml` XML config file to add the image uploader custom configuration to a content type:
 
diff --git a/docs/migration/migrate-custom-content-types-from-bluefoot.md b/docs/migration/migrate-custom-content-types-from-bluefoot.md
@@ -185,8 +185,8 @@ Run the following command on the server to initiate your module's migration proc
 
 You have migrated your old BlueFoot content type into your new PageBuilder content type!
 
-[PageBuilder migration API]: bluefoot-data-migration.md
-[BlueFoot data migration]: bluefoot-data-migration.md
+[PageBuilder migration API]: migrate-from-bluefoot.md
+[BlueFoot data migration]: migrate-from-bluefoot.md
 [`composer.json`]: https://devdocs.magento.com/guides/v2.2/extension-dev-guide/build/composer-integration.html
 [versioning policy]: https://devdocs.magento.com/guides/v2.2/extension-dev-guide/versioning/
 [module lifecycle]: https://devdocs.magento.com/guides/v2.2/extension-dev-guide/prepare/lifecycle.html
diff --git a/docs/reference/architecture.md b/docs/reference/architecture.md
@@ -24,6 +24,7 @@ This allows the content to be displayed with minimum changes to the Magento stor
 To display Page Builder content on storefront Magento and third party systems need to do the following
 
 Use the following steps to display PageBuilder content on a Magento storefront or third-party system:
+
 <!-- {% raw %} -->
 1. Replace all Magento directives such as `{{image url=path/to/image.png}}`
 2. Add custom stylesheet to provide the base styles that user can't edit.
@@ -84,13 +85,13 @@ A Mass converter modifies data for all content type elements.
 For example, the content type of two elements, main and image has data stored in the fields `border`, `border_color`, `border_width`, `background_image`.
 A mass converter allows you to modify all these fields.
 
-For more information, read about how [data is stored internally](#Data store). 
+For more information, read about how [data is stored internally](#Datastore). 
 
 ### Element converter
 
 An element converter modifies a single field at a time.
 
-## Data store
+## Datastore
 
 Data for content types are stored in a simple object called the DataStore `Magento_PageBuilder/js/data-store`.
 
@@ -100,7 +101,7 @@ You can use the `subscribe` method to subscribe to changes in the data and perfo
 
 ## Content type configuration
 
-Please see [content type configuration](../configurations/content-type-configuration.md#Converter Interfaces) for information on content type configuration.
+Please see [content type configuration](../configurations/content-type-configuration.md) for information on content type configuration.
 
 ## Appearances
 
diff --git a/docs/reference/events.md b/docs/reference/events.md
@@ -1,4 +1,4 @@
-# Events
+# Events {#events}
 
 This document contains reference information for events dispatched in Page Builder.
 
@@ -7,9 +7,7 @@ This document contains reference information for events dispatched in Page Build
 
 ## Events list {#eventslist}
 
-- [Events](#events)
-    - [Events list {#eventslist}](#events-list-eventslist)
-    - [`contentType:*` events](#contenttype-events)
+   - [`contentType:*` events](#contenttype-events)
         - [`contentType:createAfter`](#contenttypecreateafter)
         - [`contentType:mountAfter`](#contenttypemountafter)
         - [`contentType:dropAfter`](#contenttypedropafter)
@@ -304,7 +302,7 @@ All events starting with `contentType:` can also be called for specific content
 
 [Back to top]
 
-### `image:{{id}}:assignAfter`
+### `image:{{id}}:assignAfter` {#imageidassignafter}
 
 **Triggers**
 
@@ -373,7 +371,7 @@ Function
 
 [Back to top]
 
-### `stage:{{id}}:toggleFullscreen`
+### `stage:{{id}}:toggleFullscreen` {#stageidtogglefullscreen}
 
 **Triggers**
 
@@ -453,14 +451,14 @@ Error
 
 [Back to top]
 
-### `stage:{{id}}:readyAfter`
+### `stage:{{id}}:readyAfter` {#stageidreadyafter}
 
 **Triggers**
 
 * `Stage::ready`
 * `stage instance`
 
-### `stage:{{id}}:masterFormatRenderAfter`
+### `stage:{{id}}:masterFormatRenderAfter` {#stageidmasterformatrenderafter}
 
 **Triggers**
 
@@ -517,7 +515,7 @@ Error
 
 [Back to top]
 
-### `{{config.name}}:{{id}}:updateAfter`
+### `{{config.name}}:{{id}}:updateAfter` {#confignameidupdateafter}
 
 **Triggers**
 
diff --git a/docs/reference/master-format.md b/docs/reference/master-format.md
@@ -1,5 +1,4 @@
 # Master format
-
 <!-- {% raw %} -->
 PageBuilder uses XHTML with inline styles and data attributes as the master format for storage.
 
@@ -25,6 +24,7 @@ Contained:
 ### main element
 
 Attributes
+
 1. data-enable-parallax [1, 0]
 2. data-parallax-speed [0-1]
 3. data-background-images `{"desktop_image":"{{media url}}","mobile_image":"{{media url}}"}`
