@carbon/ibm-products 2.1.3 → 2.2.0

package/scss/components/Cascade/_storybook-styles.scss

@@ -8,9 +8,8 @@
 @use '@carbon/styles/scss/theme' as *;
 @use '@carbon/styles/scss/spacing' as *;
 
-#storybook-docs .docs-story {
-  /* stylelint-disable-next-line carbon/layout-token-use */
-  padding: 30px 0;
+#root {
+  width: 100%;
 }
 
 .box {

package/scss/components/DataSpreadsheet/_storybook-styles.scss

@@ -4,9 +4,3 @@
 // This source code is licensed under the Apache-2.0 license found in the
 // LICENSE file in the root directory of this source tree.
 //
-
-$story-anchor: 'data-spreadsheet';
-div[id*='#{$story-anchor}'] .docs-story > div:first-child > div:first-child {
-  overflow: auto;
-  width: 100%;
-}

package/scss/components/Datagrid/_datagrid.scss

@@ -1,5 +1,5 @@
 //
-// Copyright IBM Corp. 2022, 2023
+// Copyright IBM Corp. 2022, 2022
 //
 // This source code is licensed under the Apache-2.0 license found in the
 // LICENSE file in the root directory of this source tree.
@@ -22,7 +22,6 @@
 
 // Datagrid uses the following Carbon for IBM Products components:
 // TODO: @use(s) of IBM Products component styles used by Datagrid
-@use '../ButtonMenu';
 
 // The block part of our conventional BEM class names (blockClass__E--M).
 $block-class: #{c4p-settings.$pkg-prefix}--datagrid;
@@ -34,8 +33,7 @@ $block-class: #{c4p-settings.$pkg-prefix}--datagrid;
     display: none;
   }
 
-  .#{c4p-settings.$carbon-prefix}--overflow-menu-options
-    > .#{c4p-settings.$pkg-prefix}--datagrid__row-size-dropdown {
+  .bx--overflow-menu-options > .c4p--datagrid__row-size-dropdown {
     left: $spacing-01;
     width: 112px;
   }

package/scss/components/Datagrid/_storybook-styles.scss

@@ -1,5 +1,5 @@
 //
-// Copyright IBM Corp. 2022, 2023
+// Copyright IBM Corp. 2022, 2022
 //
 // This source code is licensed under the Apache-2.0 license found in the
 // LICENSE file in the root directory of this source tree.
@@ -20,7 +20,7 @@ $block-class: #{c4p-settings.$pkg-prefix}--datagrid;
   height: 100vh;
 }
 
-.sb-show-main.sb-main-centered #storybook-root {
+.sb-show-main.sb-main-centered #root {
   width: 100%;
   height: 100vh;
   padding: $spacing-07;
@@ -114,17 +114,3 @@ $block-class: #{c4p-settings.$pkg-prefix}--datagrid;
   margin-right: $spacing-03;
   background-color: $field-01;
 }
-
-.#{c4p-settings.$carbon-prefix}--body--with-modal-open {
-  .#{$block-class}__mobile-toolbar-modal.#{c4p-settings.$carbon-prefix}--modal {
-    top: -$spacing-07;
-    left: -$spacing-07;
-    width: 100vw;
-  }
-}
-
-$story-anchor: 'datagrid';
-div[id*='#{$story-anchor}'] .docs-story > div:first-child > div:first-child {
-  overflow: auto;
-  width: 100%;
-}

package/scss/components/Datagrid/styles/_datagrid.scss

@@ -1,9 +1,10 @@
-//
-// Copyright IBM Corp. 2020, 2023
-//
-// This source code is licensed under the Apache-2.0 license found in the
-// LICENSE file in the root directory of this source tree.
-//
+/*
+* Licensed Materials - Property of IBM
+* 5724-Q36
+* (c) Copyright IBM Corp. 2020 - 2021
+* US Government Users Restricted Rights - Use, duplication or disclosure
+* restricted by GSA ADP Schedule Contract with IBM Corp.
+*/
 
 @use '@carbon/styles/scss/theme' as *;
 @use '@carbon/styles/scss/spacing' as *;
@@ -581,6 +582,12 @@
   width: 100%;
 }
 
+.#{c4p-settings.$carbon-prefix}--body--with-modal-open
+  .#{$block-class}__grid-container {
+  overflow: hidden;
+  height: 100vh;
+}
+
 .#{$block-class} .#{c4p-settings.$carbon-prefix}--modal {
   width: 100%;
 }
@@ -625,23 +632,3 @@
 .#{$block-class} .#{c4p-settings.$pkg-prefix}--datagrid__head-wrap {
   background-color: $layer-accent;
 }
-
-.#{$block-class}
-  .#{c4p-settings.$carbon-prefix}--action-list
-  .#{c4p-settings.$carbon-prefix}--btn.#{c4p-settings.$pkg-prefix}--button-menu {
-  padding: 0;
-}
-
-// TODO: Revisit batch action list button and button icon alignment after
-// https: //github.com/carbon-design-system/carbon/issues/14021 is fixed
-.#{$block-class}
-  .#{c4p-settings.$carbon-prefix}--action-list
-  .#{c4p-settings.$carbon-prefix}--btn {
-  align-items: center;
-}
-
-.#{$block-class}
-  .#{c4p-settings.$carbon-prefix}--action-list
-  .#{c4p-settings.$carbon-prefix}--btn__icon {
-  margin-top: 0;
-}

package/scss/components/Datagrid/styles/addons/_FilterFlyout.scss

@@ -75,13 +75,6 @@ $action-set-height: rem(64px);
 }
 
 // Carbon overrides
-.#{variables.$block-class}-filter-flyout__trigger.#{c4p-settings.$carbon-prefix}--btn {
-  display: flex;
-  width: 3rem;
-  height: 3rem;
-  justify-content: center;
-}
-
 .#{variables.$block-class}-filter-flyout__trigger--open.#{c4p-settings.$carbon-prefix}--btn.#{c4p-settings.$carbon-prefix}--btn--icon-only {
   position: relative;
   background-color: $layer-02;

package/scss/components/Datagrid/styles/addons/_FilterPanel.scss

@@ -124,10 +124,6 @@
 }
 
 .#{c4p-settings.$carbon-prefix}--btn.c4p--datagrid-filter-panel-open-button {
-  display: flex;
-  width: 3rem;
-  height: 3rem;
-  justify-content: center;
   border-right: 1px solid $layer-accent-01;
   border-bottom: none;
 }

package/scss/components/HTTPErrors/_storybook-styles.scss

@@ -0,0 +1,6 @@
+//
+// Copyright IBM Corp. 2021, 2021
+//
+// This source code is licensed under the Apache-2.0 license found in the
+// LICENSE file in the root directory of this source tree.
+//

package/scss/components/NotificationsPanel/_notifications-panel.scss

@@ -54,7 +54,7 @@ $block-class: #{c4p-settings.$pkg-prefix}--notifications-panel;
   top: $spacing-09;
   right: 0;
   overflow: auto;
-  min-width: 20rem;
+  min-width: 22.75rem;
   max-width: 22.75rem;
   min-height: 38.5rem;
   max-height: 38.5rem;

package/scss/components/NotificationsPanel/_storybook-styles.scss

@@ -10,14 +10,6 @@
 
 $storybook-block-class: #{c4p-settings.$pkg-prefix}--notifications-panel__story;
 
-.#{$storybook-block-class}--full-height {
-  height: 100vh;
-  max-height: var(--doc-story-height); // set in core if needed;
-}
-
-.#{$storybook-block-class}__add {
-  display: flex;
-  height: 100%;
-  align-items: center;
-  justify-content: center;
+.#{$storybook-block-class}--header {
+  @include theme(themes.$g100);
 }

package/scss/components/PageHeader/_page-header.scss

@@ -29,6 +29,7 @@ $block-class: #{$pkg-prefix}--page-header;
 $breadcrumb-block-class: #{$pkg-prefix}--breadcrumb-with-overflow;
 
 $raised-z-index: 99;
+/* stylelint-disable-next-line function-no-unknown */
 $z-index-header-minus: utilities.z('header') - 1;
 
 $left-section-std-width: 60%;

package/scss/components/PageHeader/_storybook-styles.scss

@@ -15,6 +15,15 @@
 
 $story-class: 'page-header-stories';
 
+// cspell:disable-next-line
+.sbdocs .#{$story-class}__viewport {
+  max-height: 500px;
+  background-color: $background;
+  box-shadow: 0 0 4px 1px $layer-accent-01;
+  color: $text-primary;
+  overflow-y: auto;
+}
+
 .#{$story-class}__content-switcher {
   justify-content: flex-start;
 }
@@ -57,34 +66,15 @@ $story-class: 'page-header-stories';
   flex-direction: column;
 }
 
-.#{$story-class}__viewport {
+.#{$story-class}__app--whole-page-scroll {
   overflow: hidden;
-  height: 100vh;
-}
-
-.#{$story-class}__viewport--scroll {
-  overflow-y: auto;
 }
 
-.#{$story-class}__viewport .#{$story-class}__content-container {
+.#{$story-class}__content-container {
   height: 100%;
-  overflow-y: auto;
-}
-
-.#{$story-class}__viewport
-  .#{$story-class}__content-container--with-global-header {
-  height: calc(100% - #{$spacing-09});
-  margin-top: $spacing-09;
+  padding: 0;
 }
 
-.#{$story-class}__viewport--scroll .#{$story-class}__content-container {
-  overflow-y: initial;
-}
-
-// cspell:disable-next-line
-.sbdocs .#{$story-class}__viewport {
-  max-height: 50vh;
-  background-color: $background;
-  box-shadow: 0 0 4px 1px $layer-accent-01;
-  color: $text-primary;
+.#{$story-class}__app--whole-page-scroll .#{$story-class}__content-container {
+  overflow-y: auto;
 }

package/scss/components/SidePanel/_side-panel.scss

@@ -64,6 +64,7 @@ $action-set-block-class: #{c4p-settings.$pkg-prefix}--action-set;
 
   position: fixed;
   // Need to disable stylelint until dart sass namespace support is added
+  /* stylelint-disable-next-line function-no-unknown */
   z-index: utilities.z('modal');
   top: $spacing-09;
   height: calc(100% - 3rem);
@@ -440,6 +441,7 @@ $action-set-block-class: #{c4p-settings.$pkg-prefix}--action-set;
 .#{$block-class}__overlay {
   position: fixed;
   // Need to disable stylelint until dart sass namespace support is added
+  /* stylelint-disable-next-line function-no-unknown */
   z-index: utilities.z('overlay');
   width: 100%;
   height: 100%;

package/scss/components/Tearsheet/_tearsheet.scss

@@ -30,6 +30,7 @@ $motion-duration: $duration-moderate-02;
 @include block-wrap($block-class) {
   &.#{$block-class} {
     // Need to disable stylelint until dart sass namespace support is added
+    /* stylelint-disable-next-line function-no-unknown */
     z-index: utilities.z('modal') + 1;
     align-items: flex-end;
     color: $text-primary;
@@ -43,6 +44,7 @@ $motion-duration: $duration-moderate-02;
 
   &.is-visible {
     // Need to disable stylelint until dart sass namespace support is added
+    /* stylelint-disable-next-line function-no-unknown */
     z-index: utilities.z('modal');
     align-items: flex-end;
     // stylelint-disable-next-line carbon/motion-duration-use, carbon/motion-easing-use
@@ -56,6 +58,7 @@ $motion-duration: $duration-moderate-02;
 
   &.#{$block-class}--stacked-1-of-2 {
     // Need to disable stylelint until dart sass namespace support is added
+    /* stylelint-disable-next-line function-no-unknown */
     z-index: utilities.z('modal') - 1;
     // stylelint-disable-next-line carbon/theme-token-use
     background-color: rgba($overlay-color, 0.33);
@@ -63,6 +66,7 @@ $motion-duration: $duration-moderate-02;
 
   &.#{$block-class}--stacked-1-of-3 {
     // Need to disable stylelint until dart sass namespace support is added
+    /* stylelint-disable-next-line function-no-unknown */
     z-index: utilities.z('modal') - 2;
     // stylelint-disable-next-line carbon/theme-token-use
     background-color: rgba($overlay-color, 0.11);
@@ -70,6 +74,7 @@ $motion-duration: $duration-moderate-02;
 
   &.#{$block-class}--stacked-2-of-3 {
     // Need to disable stylelint until dart sass namespace support is added
+    /* stylelint-disable-next-line function-no-unknown */
     z-index: utilities.z('modal') - 1;
     // stylelint-disable-next-line carbon/theme-token-use
     background-color: rgba($overlay-color, 0.25);
@@ -146,14 +151,12 @@ $motion-duration: $duration-moderate-02;
     padding: $spacing-06 $spacing-07;
     border-bottom: 1px solid $border-subtle-01;
     margin: 0;
-    background-color: $layer;
   }
 
   &.#{$block-class}--narrow .#{$block-class}__header {
     padding: $spacing-05;
     border-bottom: 1px solid $border-subtle-01;
     margin: 0;
-    background-color: $layer;
   }
 
   .#{$block-class}__header-content {
@@ -267,15 +270,11 @@ $motion-duration: $duration-moderate-02;
   .#{$block-class}__main {
     display: flex;
     flex-direction: row;
-    background-color: $background;
+    background-color: $layer;
     grid-column: 1 / -1;
     grid-row: 1 / -1;
   }
 
-  &.#{$block-class}--narrow .#{$block-class}__main {
-    background-color: $layer;
-  }
-
   .#{$block-class}__main .#{$block-class}__influencer {
     border-right: none;
     border-left: 1px solid $border-subtle-01;

package/scss/components/WebTerminal/_storybook-styles.scss

@@ -1,5 +1,5 @@
 //
-// Copyright IBM Corp. 2021, 2023
+// Copyright IBM Corp. 2021, 2022
 //
 // This source code is licensed under the Apache-2.0 license found in the
 // LICENSE file in the root directory of this source tree.
@@ -34,13 +34,3 @@ $storybook-block-class: #{c4p-settings.$pkg-prefix}--notifications-panel__story;
     font-size: 14px;
   }
 }
-
-$story-anchor: 'web-terminal';
-#storybook-docs {
-  ul {
-    list-style: initial;
-  }
-  ol {
-    list-style: decimal;
-  }
-}

package/scss/global/styles/_display-box.scss

@@ -22,7 +22,6 @@ $indicator-height: $spacing-04;
   position: relative;
   display: inline-block;
   padding-top: $spacing-05; // space for the indicators
-  margin-top: $spacing-09; // provides space in docs
   color: $text-helper;
 }
 

package/es/components/APIKeyModal/APIKeyModal.docs-page.js

@@ -1,26 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import { useOf } from '@storybook/blocks';
-import { storyDocsGuidelines } from '../../global/js/utils/story-helper';
-import * as stories from './APIKeyModal.stories';
-var DocsPage = function DocsPage() {
-  var _useOf = useOf('meta', ['meta']),
-    csfFile = _useOf.csfFile;
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    altGuidelinesHref: [storyDocsGuidelines(csfFile), {
-      href: 'https://www.carbondesignsystem.com/components/modal/usage',
-      label: 'Carbon Modal usage guidelines'
-    }, {
-      href: 'https://react.carbondesignsystem.com/?path=/docs/modal--default',
-      label: 'Carbon Modal documentation'
-    }],
-    blocks: [{
-      story: stories.Edit,
-      description: "API key creation / generation is assumed to be the default mode for this modal.\nTo enable key editing you have to set the `edit` prop to true and supply any\nother edit related props with the relevant input."
-    }, {
-      description: "By default generate and edit only supply a name input for your key. If you need additional input you should use custom steps",
-      story: stories.CustomEdit
-    }]
-  });
-};
-export default DocsPage;

package/es/components/AboutModal/AboutModal.docs-page.js

@@ -1,21 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import * as stories from './AboutModal.stories';
-var DocsPage = function DocsPage() {
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    guidelinesHref: "https://pages.github.ibm.com/cdai-design/pal/patterns/about-modal/usage",
-    blocks: [{
-      story: stories.aboutModal
-    }, {
-      story: stories.fullyLoaded
-    }, {
-      title: 'Overriding the Carbon theme',
-      description: 'The design recommendation is to use a dark theme for the AboutModal if the application is currently using a light theme, and vice versa. The theme applied to the AboutModal can easily be customized as follows:',
-      source: {
-        language: 'css',
-        code: ".#{$pkg-prefix}--about-modal {\n  @include carbon--theme(\n    $theme: $carbon--theme--g90\n  );\n}"
-      }
-    }]
-  });
-};
-export default DocsPage;

package/es/components/Cascade/Cascade.docs-page.js

@@ -1,22 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import * as stories from './Cascade.stories';
-import { useOf } from '@storybook/blocks';
-import { storyDocsGuidelines } from '../../global/js/utils/story-helper';
-var DocsPage = function DocsPage() {
-  var _useOf = useOf('meta', ['meta']),
-    csfFile = _useOf.csfFile;
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    altGuidelinesHref: [storyDocsGuidelines(csfFile), {
-      href: 'https://www.carbondesignsystem.com/guidelines/motion/overview/',
-      label: 'Carbon motion guidelines'
-    }],
-    blocks: [{
-      story: stories.WithoutGrid
-    }, {
-      description: 'When using `Cascade` with  grid support its important that you follow the example code structure and provide the rows and columns. The component will assume this structure and add the appropriate CSS classes to the columns.',
-      story: stories.WithGrid
-    }]
-  });
-};
-export default DocsPage;

package/es/components/CreateFullPage/CreateFullPage.docs-page.js

@@ -1,39 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import * as stories from './CreateFullPage.stories';
-var DocsPage = function DocsPage() {
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    altGuidelinesHref: "https://pages.github.ibm.com/cdai-design/pal/patterns/creation-flows/usage#full-page",
-    blocks: [{
-      description: "There are **2** components that make up a Create Full Page component, which can\nbe used in unison to create the desired look, or flow. Please note, to utilize\nthe Create Full Page component, you'll need to have a minimum of two steps. If\nyou are looking for a one step creation flow, consider Create Tearsheet, Create\nSide Panel, or Create Modal."
-    }, {
-      story: stories.createFullPage,
-      description: "This is used when you have one section per step. This can be created by passing\nin the overall `<CreateFullPage />` component and the `<CreateFullPageStep />`\ncomponent with form items as children:\n",
-      source: {
-        code: "<CreateFullPage {...props}>\n      <CreateFullPageStep\n          title=\"Required title\"\n          subtitle=\"Optional subtitle\"\n          description=\"Optional description\"\n          onNext={() => {'Optional function'}}\n          >\n          <Row>\n            <Column xlg={5} lg={5} md={4} sm={4}>\n              <TextInput\n                id=\"test-1\"\n                invalidText=\"A valid value is required\"\n                labelText=\"Topic name\"\n                placeholder=\"Enter topic name\"\n              />\n            </Column>\n          </Row>\n      </CreateFullPageStep>\n    </CreateFullPage>"
-      }
-    }, {
-      story: stories.createFullPageWithSections,
-      description: "This is used when you have several sections per step. This can be created by\npassing in the overall `<CreateFullPage />` component and the\n`<CreateFullPageStep />` component for the first `section`. All additional\n`sections` must be passed in as children, as shown below:",
-      source: {
-        code: "<CreateFullPageStep\n    title=\"Required title\"\n    subtitle=\"Optional subtitle\"\n    description=\"Optional description\"\n    onNext={() => {'Optional function'}}\n    >\n    <Row>\n      <Column xlg={5} lg={5} md={4} sm={4}>\n        <fieldset className={`#{$pkg-prefix}--create-full-page__step-fieldset`}>\n          <TextInput\n            id=\"test-1\"\n            invalidText=\"A valid value is required\"\n            labelText=\"Topic name\"\n            placeholder=\"Enter topic name\"\n          />\n        </fieldset>\n      </Column>\n    </Row>\n    <span className={`#{$pkg-prefix}--create-full-page__section-divider`} />\n    <h5 className={`#{$pkg-prefix}--create-full-page__step-title`}>Required title</h5>\n    <h6 className={`#{$pkg-prefix}--create-full-page__step-subtitle`}>\n      Optional subtitle\n    </h6>\n    <p className={`#{$pkg-prefix}--create-full-page__step-description`}>\n      Optional description\n    </p>\n    <Row>\n      <Column xlg={5} lg={5} md={4} sm={4}>\n        <fieldset className={`#{$pkg-prefix}--create-full-page__step-fieldset`}>\n          <TextInput\n            id=\"test-2\"\n            invalidText=\"A valid value is required\"\n            labelText=\"Topic name\"\n            placeholder=\"Enter topic name\"\n          />\n        </fieldset>\n      </Column>\n    </Row>\n</CreateFullPageStep>"
-      }
-    }, {
-      title: 'Using custom components',
-      description: "It is possible to use custom components that return `CreateFullPageStep`s in\norder to help reduce the amount of logic in the component that contains the main\n`CreateFullPage`. _It is required that each child of the `CreateFullPage` either\nbe a custom step or a `CreateFullPageStep`_. An example of this could look like\nthe following:",
-      source: {
-        code: "const CreateStepCustom = ({ subtitle, ...rest }) => {\n  return (\n    <CreateFullPageStep\n      {...rest}\n      subtitle={subtitle}\n      title=\"Step 1\"\n      onNext={() => console.log('optional validation check')}\n      onMount={() => console.log('optional onMount fn')}\n      disableSubmit={false}\n    >\n      step content here\n    </CreateFullPageStep>\n  );\n};\n\nconst CreateComponent = () => {\n  return (\n    <CreateFullPage {...createFullPageProps}>\n      <CreateStepCustom subtitle=\"Custom step subtitle\" />\n      <CreateFullPageStep\n        title=\"Topic name\"\n        fieldsetLegendText=\"Topic information\"\n        disableSubmit={!value}\n        subtitle=\"This is the unique name used to recognize your topic\"\n        description=\"It will also be used by your producers and consumers as part of the\n        connection information, so make it something easy to recognize.\"\n      >\n        Content for second step\n      </CreateFullPageStep>\n    </CreateFullPage>\n  );\n};"
-      }
-    }, {
-      title: 'Using dynamic steps',
-      description: "The use of dynamic steps can be utilized in a scenario when the user makes a\ncertain selection on one step that effects which steps will follow it, this is\ncontrolled via the `includeStep` prop. See abbreviated example below:",
-      source: {
-        code: "import { useState } from 'react';\n\nconst CreateFlow = () => {\n  const [shouldIncludeAdditionalStep, setShouldIncludeAdditionalStep] =\n    useState(false);\n  return (\n    <CreateFullPage {...createFullPageProps}>\n      <CreateFullPageStep {...step1Props}>\n        Step 1 content\n        <Checkbox\n          labelText={`Include additional step`}\n          id=\"include-additional-step-checkbox\"\n          onChange={(value) => setShouldIncludeAdditionalStep(value)}\n          checked={shouldIncludeAdditionalStep}\n        />\n      </CreateFullPageStep>\n      <CreateFullPageStep\n        {...step2Props}\n        includeStep={shouldIncludeAdditionalStep}\n      >\n        Dynamic step content\n      </CreateFullPageStep>\n      <CreateFullPageStep {...step3Props}>\n        Final step content\n      </CreateFullPageStep>\n    </CreateFullPage>\n  );\n};"
-      }
-    }, {
-      title: 'Class names',
-      description: "Additionally, to get the preferred styling when including your own children as\nsections, you can utilize the below included class names.\n\n| Class name                                           | Element     | Features                                                   |\n| ---------------------------------------------------- | ----------- | ---------------------------------------------------------- |\n| `#{$pkg-prefix}--create-full-page__step-title`       | title       | `productive-heading-04` & `margin-bottom` of `$spacing-05` |\n| `#{$pkg-prefix}--create-full-page__step-subtitle`    | subtitle    | `productive-heading-01` & `margin-bottom` of `$spacing-03` |\n| `#{$pkg-prefix}--create-full-page__step-description` | description | `body-long-01` & `margin-bottom` of `$spacing-06`          |\n| `#{$pkg-prefix}--create-full-page__step-fieldset`    | fieldset    | `margin-bottom` of `$spacing-05` to all children elements  |\n| `#{$pkg-prefix}--create-full-page__section-divider`  | divider     | Includes a `1px` divider line inside the `main` content    |\n"
-    }]
-  });
-};
-export default DocsPage;

package/es/components/CreateModal/CreateModal.docs-page.js

@@ -1,24 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import * as stories from './CreateModal.stories';
-var DocsPage = function DocsPage() {
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    altGuidelinesHref: "https://pages.github.ibm.com/cdai-design/pal/patterns/creation-flows/usage#modal",
-    blocks: [{
-      story: stories.Default
-    }, {
-      title: 'Form validation',
-      description: "All forms, including that within the `CreateModal` should follow C&CS guidelines\nfor form validation.\n\nThis includes the following:\n\n- The `Submit` button in the modal should be disabled, until all required inputs\n  are filled in and valid\n- All required inputs should _only_ throw an invalid error _after_ the element\n  loses focus\n- All optional form fields should have an `(optional)` text at the end of the\n  input `labelText`. Optional should always be in parentheses\n\nYou can find more information on how to validate your form fields in\n[Carbon's Form usage page](https://www.carbondesignsystem.com/components/form/usage)."
-    }, {
-      title: 'Overriding Carbon theme',
-      description: "The design recommendation is to use a dark theme for the CreateModal if the\napplication is currently using a light theme, and vice versa. The theme applied\nto the CreateModal can easily be customized as follows:\n\nIn SCSS:",
-      source: {
-        language: 'css',
-        code: "  .#{$pkg-prefix}--create-modal {\n    @include carbon--theme(\n      $theme: $carbon--theme--g90\n    );\n  }"
-      }
-    }, {
-      description: "Alternatively, the required Carbon theme can be set as above in a custom CSS\nclass which is then applied to the CreateModal using the `className` prop."
-    }]
-  });
-};
-export default DocsPage;

package/es/components/CreateSidePanel/CreateSidePanel.docs-page.js

@@ -1,18 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import * as stories from './CreateSidePanel.stories';
-var DocsPage = function DocsPage() {
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    altGuidelinesHref: [{
-      href: 'https://pages.github.ibm.com/cdai-design/pal/patterns/creation-flows/usage#side-panel',
-      label: 'Carbon create flows side panel usage guidelines'
-    }],
-    blocks: [{
-      story: stories.Default
-    }, {
-      title: 'Form validation',
-      description: "All forms, including that within the `CreateSidePanel` should follow C&CS\nguidelines for form validation.\n\nThis includes the following:\n\n- The `Submit` button in the side panel should be disabled, until all required\n  inputs are filled in and valid\n- All required inputs should _only_ throw an invalid error _after_ the element\n  loses focus\n- All optional form fields should have an `(optional)` text at the end of the\n  input `labelText`. Optional should always be in parentheses\n\nYou can find more information on how to validate your form fields in\n[Carbon's Form usage page](https://www.carbondesignsystem.com/components/form/usage)."
-    }]
-  });
-};
-export default DocsPage;

package/es/components/CreateTearsheet/CreateTearsheet.docs-page.js

@@ -1,29 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import * as stories from './CreateTearsheet.stories';
-var DocsPage = function DocsPage() {
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    altGuidelinesHref: "https://pages.github.ibm.com/cdai-design/pal/patterns/creation-flows/usage#wide-tearsheet",
-    blocks: [{
-      story: stories.multiStepTearsheet,
-      description: "This is used when you have one section per step. This can be created by passing\nin the overall `<CreateTearsheet />` component and the `<CreateTearsheetStep />`\ncomponent with form items as children:",
-      source: {
-        code: "    <CreateTearsheet {...props}>\n      <CreateTearsheetStep\n          title=\"Required title\"\n          subtitle=\"Optional subtitle\"\n          description=\"Optional description\"\n          onNext={() => {'Optional function'}}\n          disableSubmit={}\n          >\n        <TextInput\n          id=\"test-1\"\n          invalidText=\"A valid value is required\"\n          labelText=\"Topic name\"\n          placeholder=\"Enter topic name\"\n        />\n      </CreateTearsheetStep>\n    </CreateTearsheet>"
-      }
-    }, {
-      title: 'Using custom components',
-      description: "It is possible to use custom components that return `CreateTearsheetStep`s in\norder to help reduce the amount of logic in the component that contains the main\n`CreateTearsheet`. _It is required that each child of the `CreateTearsheet`\neither be a custom step or a `CreateTearsheetStep`_. An example of this could\nlook like the following:",
-      source: {
-        code: "const CreateStepCustom = ({ subtitle, ...rest }) => {\n  return (\n    <CreateTearsheetStep\n      {...rest}\n      subtitle={subtitle}\n      title=\"Step 1\"\n      onNext={() => console.log('optional validation check')}\n      onMount={() => console.log('optional onMount fn')}\n      disableSubmit={false}\n    >\n      step content here\n    </CreateTearsheetStep>\n  );\n};\n\nconst CreateComponent = () => {\n  return (\n    <CreateTearsheet {...createTearsheetProps}>\n      <CreateStepCustom subtitle=\"Custom step subtitle\" />\n      <CreateTearsheetStep\n        title=\"Topic name\"\n        fieldsetLegendText=\"Topic information\"\n        disableSubmit={!value}\n        subtitle=\"This is the unique name used to recognize your topic\"\n        description=\"It will also be used by your producers and consumers as part of the\n        connection information, so make it something easy to recognize.\"\n      >\n        Content for second step\n      </CreateTearsheetStep>\n    </CreateTearsheet>\n  );\n};"
-      }
-    }, {
-      title: 'Using dynamic steps',
-      description: "The use of dynamic steps can be utilized in a scenario when the user makes a\ncertain selection on one step that effects which steps will follow it, this is\ncontrolled via the `includeStep` prop. See abbreviated example below:",
-      code: "import { useState } from 'react';\n\nconst CreateFlow = () => {\n  const [shouldIncludeAdditionalStep, setShouldIncludeAdditionalStep] =\n    useState(false);\n  return (\n    <CreateTearsheet {...createTearsheetProps}>\n      <CreateTearsheetStep {...step1Props}>\n        Step 1 content\n        <Checkbox\n          labelText={`Include additional step`}\n          id=\"include-additional-step-checkbox\"\n          onChange={(value) => setShouldIncludeAdditionalStep(value)}\n          checked={shouldIncludeAdditionalStep}\n        />\n      </CreateTearsheetStep>\n      <CreateTearsheetStep\n        {...step2Props}\n        includeStep={shouldIncludeAdditionalStep}\n      >\n        Dynamic step content\n      </CreateTearsheetStep>\n      <CreateTearsheetStep {...step3Props}>\n        Final step content\n      </CreateTearsheetStep>\n    </CreateTearsheet>\n  );\n};"
-    }, {
-      title: 'Class names',
-      description: "Additionally, to get the preferred styling when including your own children as\nsections, you can utilize the below included class names.\n\n| Class name                                            | Element     | Features                                                   |\n| ----------------------------------------------------- | ----------- | ---------------------------------------------------------- |\n| `#{$pkg-prefix}--create-tearsheet__step--title`       | title       | `productive-heading-04` & `margin-bottom` of `$spacing-05` |\n| `#{$pkg-prefix}--create-tearsheet__step--subtitle`    | subtitle    | `productive-heading-01` & `margin-bottom` of `$spacing-03` |\n| `#{$pkg-prefix}--create-tearsheet__step--description` | description | `body-long-01` & `margin-bottom` of `$spacing-06`          |\n| `#{$pkg-prefix}--create-tearsheet__step--fieldset`    | fieldset    | `margin-bottom` of `$spacing-05` to all children elements  |\n| `#{$pkg-prefix}--create-tearsheet__section--divider`  | divider     | Includes a `1px` divider line inside the `main` content    |\n"
-    }]
-  });
-};
-export default DocsPage;

package/es/components/EditFullPage/EditFullPage.docs-page.js

@@ -1,39 +0,0 @@
-import React from 'react';
-import { StoryDocsPage } from '../../global/js/utils/StoryDocsPage';
-import * as stories from './EditFullPage.stories';
-var DocsPage = function DocsPage() {
-  return /*#__PURE__*/React.createElement(StoryDocsPage, {
-    altGuidelinesHref: "https://pages.github.ibm.com/cdai-design/pal/patterns/edit/usage#full-page-edit",
-    blocks: [{
-      description: "There are **2** components that make up a Create Full Page component, which can\nbe used in unison to create the desired look, or flow. Please note, to utilize\nthe Create Full Page component, you'll need to have a minimum of two steps. If\nyou are looking for a one step creation flow, consider Create Tearsheet, Create\nSide Panel, or Create Modal."
-    }, {
-      story: stories.editFullPage,
-      description: "This is used when you have one section per step. This can be created by passing\nin the overall `<CreateFullPage />` component and the `<CreateFullPageStep />`\ncomponent with form items as children:",
-      source: {
-        code: "<CreateFullPage {...props}>\n      <CreateFullPageStep\n          title=\"Required title\"\n          subtitle=\"Optional subtitle\"\n          description=\"Optional description\"\n          onNext={() => {'Optional function'}}\n          >\n          <Row>\n            <Column xlg={5} lg={5} md={4} sm={4}>\n              <TextInput\n                id=\"test-1\"\n                invalidText=\"A valid value is required\"\n                labelText=\"Topic name\"\n                placeholder=\"Enter topic name\"\n              />\n            </Column>\n          </Row>\n      </CreateFullPageStep>\n    </CreateFullPage>"
-      }
-    }, {
-      story: stories.editFullPageWithSections,
-      description: "This is used when you have several sections per step. This can be created by\npassing in the overall `<CreateFullPage />` component and the\n`<CreateFullPageStep />` component for the first `section`. All additional\n`sections` must be passed in as children, as shown below:",
-      source: {
-        code: "<CreateFullPageStep\n    title=\"Required title\"\n    subtitle=\"Optional subtitle\"\n    description=\"Optional description\"\n    onNext={() => {'Optional function'}}\n    >\n    <Row>\n      <Column xlg={5} lg={5} md={4} sm={4}>\n        <fieldset className={`#{$pkg-prefix}--create-full-page__step-fieldset`}>\n          <TextInput\n            id=\"test-1\"\n            invalidText=\"A valid value is required\"\n            labelText=\"Topic name\"\n            placeholder=\"Enter topic name\"\n          />\n        </fieldset>\n      </Column>\n    </Row>\n    <span className={`#{$pkg-prefix}--create-full-page__section-divider`} />\n    <h5 className={`#{$pkg-prefix}--create-full-page__step-title`}>Required title</h5>\n    <h6 className={`#{$pkg-prefix}--create-full-page__step-subtitle`}>\n      Optional subtitle\n    </h6>\n    <p className={`#{$pkg-prefix}--create-full-page__step-description`}>\n      Optional description\n    </p>\n    <Row>\n      <Column xlg={5} lg={5} md={4} sm={4}>\n        <fieldset className={`#{$pkg-prefix}--create-full-page__step-fieldset`}>\n          <TextInput\n            id=\"test-2\"\n            invalidText=\"A valid value is required\"\n            labelText=\"Topic name\"\n            placeholder=\"Enter topic name\"\n          />\n        </fieldset>\n      </Column>\n    </Row>\n</CreateFullPageStep>"
-      }
-    }, {
-      title: 'Using custom components',
-      description: "It is possible to use custom components that return `CreateFullPageStep`s in\norder to help reduce the amount of logic in the component that contains the main\n`CreateFullPage`. _It is required that each child of the `CreateFullPage` either\nbe a custom step or a `CreateFullPageStep`_. An example of this could look like\nthe following:",
-      source: {
-        code: "const CreateStepCustom = ({ subtitle, ...rest }) => {\n  return (\n    <CreateFullPageStep\n      {...rest}\n      subtitle={subtitle}\n      title=\"Step 1\"\n      onNext={() => console.log('optional validation check')}\n      onMount={() => console.log('optional onMount fn')}\n      disableSubmit={false}\n    >\n      step content here\n    </CreateFullPageStep>\n  );\n};\n\nconst CreateComponent = () => {\n  return (\n    <CreateFullPage {...createFullPageProps}>\n      <CreateStepCustom subtitle=\"Custom step subtitle\" />\n      <CreateFullPageStep\n        title=\"Topic name\"\n        fieldsetLegendText=\"Topic information\"\n        disableSubmit={!value}\n        subtitle=\"This is the unique name used to recognize your topic\"\n        description=\"It will also be used by your producers and consumers as part of the\n        connection information, so make it something easy to recognize.\"\n      >\n        Content for second step\n      </CreateFullPageStep>\n    </CreateFullPage>\n  );\n};"
-      }
-    }, {
-      title: 'Using dynamic steps',
-      description: "The use of dynamic steps can be utilized in a scenario when the user makes a\ncertain selection on one step that effects which steps will follow it, this is\ncontrolled via the `includeStep` prop. See abbreviated example below:",
-      source: {
-        code: "import { useState } from 'react';\n\nconst CreateFlow = () => {\n  const [shouldIncludeAdditionalStep, setShouldIncludeAdditionalStep] =\n    useState(false);\n  return (\n    <CreateFullPage {...createFullPageProps}>\n      <CreateFullPageStep {...step1Props}>\n        Step 1 content\n        <Checkbox\n          labelText={`Include additional step`}\n          id=\"include-additional-step-checkbox\"\n          onChange={(value) => setShouldIncludeAdditionalStep(value)}\n          checked={shouldIncludeAdditionalStep}\n        />\n      </CreateFullPageStep>\n      <CreateFullPageStep\n        {...step2Props}\n        includeStep={shouldIncludeAdditionalStep}\n      >\n        Dynamic step content\n      </CreateFullPageStep>\n      <CreateFullPageStep {...step3Props}>\n        Final step content\n      </CreateFullPageStep>\n    </CreateFullPage>\n  );\n};"
-      }
-    }, {
-      title: 'Class names',
-      description: "Additionally, to get the preferred styling when including your own children as\nsections, you can utilize the below included class names.\n\n| Class name                                           | Element     | Features                                                   |\n| ---------------------------------------------------- | ----------- | ---------------------------------------------------------- |\n| `#{$pkg-prefix}--create-full-page__step-title`       | title       | `productive-heading-04` & `margin-bottom` of `$spacing-05` |\n| `#{$pkg-prefix}--create-full-page__step-subtitle`    | subtitle    | `productive-heading-01` & `margin-bottom` of `$spacing-03` |\n| `#{$pkg-prefix}--create-full-page__step-description` | description | `body-long-01` & `margin-bottom` of `$spacing-06`          |\n| `#{$pkg-prefix}--create-full-page__step-fieldset`    | fieldset    | `margin-bottom` of `$spacing-05` to all children elements  |\n| `#{$pkg-prefix}--create-full-page__section-divider`  | divider     | Includes a `1px` divider line inside the `main` content    |\n"
-    }]
-  });
-};
-export default DocsPage;