diff --git a/.env.production b/.env.production
index d87d48531ab..9ac75645a90 100644
--- a/.env.production
+++ b/.env.production
@@ -1 +1 @@
-BACKEND_URI=https://carbondesignsystem.vercel.app/api/survey
+BACKEND_URI=https://carbondesignsystem.vercel.app/api/survey
\ No newline at end of file
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 449e1574f9a..ababb11c82d 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -1,32 +1,19 @@
# Default to system one design and one dev
-* @carbon-design-system/developers-system @carbon-design-system/design
-
-*.conf @vpicone
-# Vikki Paterson is code owner for Experimental IDE patterns
-src/pages/community/patterns/create-flows/* @vikkipaterson
-src/pages/community/patterns/delete-pattern/* @vikkipaterson
-src/pages/community/patterns/export-pattern/* @vikkipaterson
-src/pages/community/patterns/generate-an-api-key/* @vikkipaterson
-src/pages/community/patterns/import-pattern/* @vikkipaterson
-src/pages/community/patterns/remove-pattern/* @vikkipaterson
-
-# Vincent Snagg is code owner for Experimental Watson Health patterns
-src/pages/community/patterns/chatbot/* @vincentsnagg
+* @carbon-design-system/developers-system @carbon-design-system/design
-# Adriana Morales is code owner for Experimental Cloud PAL patterns
-src/pages/community/patterns/order-summary-template/* @adrianamorales
-src/pages/community/patterns/cards/* @adrianamorales
-src/pages/community/patterns/dashboard-widgets/* @adrianamorales
+# Diana Tran is the owner for Sustainability Software Patterns
-# Chris Reckling is the code owner for Experimental IoT patterns
-src/pages/community/patterns/login-pattern/* @lukefirth
+src/pages/community/patterns/login-pattern/* @dianatran18 @lukefirth
# Eliad Moosavi and Natasha Decoste are the code owners for Data Visualization
+
src/pages/data-visualization/* @theiliad @natashadecoste
-# Cal Smith for Angular tutorial
+# Zvonimir Fras for Angular tutorial
+
/src/pages/tutorial/angular/* @zvonimirfras
# Lee Chase for Vue tutorial
-/src/pages/tutorial/vue/* @lee-chase
+
+/src/pages/tutorial/vue/* @lee-chase
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/component-accessibility-deliverables.yaml b/.github/ISSUE_TEMPLATE/component-accessibility-deliverables.yaml
new file mode 100644
index 00000000000..7849bf9f340
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/component-accessibility-deliverables.yaml
@@ -0,0 +1,92 @@
+name: Component accessibility deliverables
+description: Submit the accessibility portion of your component
+title: '[Component name] component β accessibility '
+labels: 'accessibility'
+body:
+ - type: markdown
+ attributes:
+ value: |
+ Complete the following deliverables for Carbon to review the accessibility portion of the [component contribution process](https://carbondesignsystem.com/contributing/component/). To see examples, view the component accessibility guidelines on [Github](https://github.com/carbon-design-system/carbon/wiki/Component-Accessibility-Guidelines) or on [figma](https://www.figma.com/file/PmSOwLS3ldpSQtUf4xlaLD/component-accessibility-guidelines?type=design&node-id=434-4103&mode=design&t=qQ2DqDAiNaOLPlBC-0).
+
+ 1. Define component
+ 2. Document keyboard interactions
+ 3. Provide visual states
+ 4. Repeat steps 2 β 3 for each variant, if any
+ 5. Repeat step 3 for each child/subcomponent, if any
+
+ - type: markdown
+ attributes:
+ value: '## 1. Define component'
+
+ - type: checkboxes
+ id: type
+ attributes:
+ label: Component type
+ description:
+ variants are only when the interaction differs from default component,
+ not when there are only visual differences
+ options:
+ - label: Variant of existing component
+ - label: New component with no variants
+ - label: New component with variants
+ required: false
+
+ - type: checkboxes
+ id: subcomponent
+ attributes:
+ label: Can it be opened/expanded to reveal a child/subcomponent?
+ description:
+ if the child/subcomponent is non-interactive, visual states may not be
+ needed
+ options:
+ - label: Yes, it can
+ - label: No, it cannot
+ required: false
+
+ - type: markdown
+ attributes:
+ value: '## 2. Document keyboard interactions'
+
+ - type: checkboxes
+ id: keyboard
+ attributes:
+ label: Select all that apply
+ description:
+ options:
+ - label: '"Tab" moves between interactive components'
+ - label: Arrow keys move between component and subcomponent
+ - label: '"Enter" activates'
+ - label: '"Space" selects'
+ - label: '"Esc" closes'
+ required: false
+
+ - type: textarea
+ id: visual-examples
+ attributes:
+ label: Create keyboard interaction visual examples
+ description:
+ 'Provide screenshots or a figma link. In the early stages of
+ contribution, only low fidelity visuals are required, but high fidelity
+ visuals should be created by the time the component is ready to be
+ published. Duplicate the [figma
+ file](https://www.figma.com/file/PmSOwLS3ldpSQtUf4xlaLD/lo-fi-keyboard-interaction-visual?type=design&node-id=434-4103&t=kO1MZkuNTKMIAj0h-0)
+ to see examples and use the provided assets.'
+ validations:
+ required: true
+
+ - type: markdown
+ attributes:
+ value: '## 3. Provide visual states'
+ - type: textarea
+ id: visual-states
+ attributes:
+ label:
+ Focused and non-focused states for default, selected, error (if any) and
+ error + selected (if any)
+ description:
+ 'Provide screenshots or a figma link. This is in addition to what Carbon
+ may require. Duplicate the [figma
+ file](https://www.figma.com/file/PmSOwLS3ldpSQtUf4xlaLD/lo-fi-keyboard-interaction-visual?type=design&node-id=434-4103&t=kO1MZkuNTKMIAj0h-0)
+ to see examples and use the provided template.'
+ validations:
+ required: true
diff --git a/.github/workflows/platform-content-sync.yml b/.github/workflows/platform-content-sync.yml
deleted file mode 100644
index efce1cdb40d..00000000000
--- a/.github/workflows/platform-content-sync.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-name: Sync content with platform
-
-on:
- push:
- branches:
- - 'main'
- paths:
- - '**.mdx'
-
-jobs:
- create_issue:
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v3
- with:
- repository: carbon-design-system/carbon-platform
- ref: main
- - name: Generate token
- uses: tibdex/github-app-token@v1
- id: generate_token
- with:
- app_id: ${{ secrets.APP_ID }}
- private_key: ${{ secrets.APP_PRIVATE_KEY }}
- - name: Create issue on platform repo
- run: |
- gh issue create --title "[Content sync]: carbon-website" --label "role: dev π€" --label "service: web-app π" --body 'A pull request on carbon-website was just merged. It contains .mdx content changes that may need to be synced to platform:
- - ${{ github.event.compare }}'
- env:
- GITHUB_TOKEN: ${{ steps.generate_token.outputs.token }}
diff --git a/.github/workflows/update-carbon-gatsby-deps.yml b/.github/workflows/update-carbon-gatsby-deps.yml
new file mode 100644
index 00000000000..2f3c86a9204
--- /dev/null
+++ b/.github/workflows/update-carbon-gatsby-deps.yml
@@ -0,0 +1,53 @@
+name: Update Carbon and gatsby-theme-carbon deps
+
+concurrency:
+ group: ${{ github.workflow }}-${{ github.ref }}
+ cancel-in-progress: true
+
+on:
+ workflow_dispatch:
+
+jobs:
+ carbon-website:
+ runs-on: ubuntu-latest
+ timeout-minutes: 15
+ steps:
+ - uses: actions/checkout@v3
+ with:
+ repository: carbon-design-system/carbon-website
+ ref: main
+ - name: Use Node.js 18.x
+ uses: actions/setup-node@v3
+ with:
+ node-version: '18.x'
+ registry-url: 'https://registry.npmjs.org'
+ - name: Update dependencies
+ run: |
+ yarn upgrade \
+ @carbon/react@next \
+ @carbon/elements@next \
+ @carbon/pictograms@next \
+ @carbon/pictograms-react@next \
+ @carbon/icons@next \
+ @carbon/icons-react@next \
+ gatsby-theme-carbon@latest \
+ - name: Generate token
+ uses: tibdex/github-app-token@v1
+ id: generate_token
+ with:
+ app_id: ${{ secrets.APP_ID }}
+ private_key: ${{ secrets.APP_PRIVATE_KEY }}
+ - name: Create Pull Request
+ uses: peter-evans/create-pull-request@v5
+ with:
+ branch: 'release/update-carbon-deps'
+ commit-message: 'chore(release): update carbon and gatsby-theme-carbon deps'
+ delete-branch: true
+ title: 'chore(release): update carbon and gatsby-theme-carbon deps'
+ token: ${{ steps.generate_token.outputs.token }}
+ body: |
+ Automated pull request to update Carbon and gatsby-theme-carbon on the website
+ **Checklist**
+ - [ ] Verify package version bumps are accurate
+ - [ ] Verify CI passes as expected
+ - [ ] Verify no regressions on the website in the deploy preview
diff --git a/conf.d/rewrite.conf b/conf.d/rewrite.conf
index c17a5631163..431ca8c864b 100644
--- a/conf.d/rewrite.conf
+++ b/conf.d/rewrite.conf
@@ -25,6 +25,7 @@ rewrite /get-started/design/(.*) /designing/get-started/kits/\$1 permanent;
# Contributions rewrites
rewrite /how-to-contribute/(.*) /contributing/\$1 permanent;
+rewrite /contributing/overview /contributing/get-started permanent;
# What's happening
rewrite /updates/whats-new /whats-happening/releases permanent;
@@ -51,4 +52,7 @@ rewrite /whats-happening/v11-release /migrating/guide/\$1 permanent;
#Icon and pictogram contribution
rewrite /guidelines/icons/contribute/ /contributing/contribute-icons/ permanent;
-rewrite /guidelines/pictograms/contribute/ /contributing/contribute-pictograms/ permanent;
\ No newline at end of file
+rewrite /guidelines/pictograms/contribute/ /contributing/contribute-pictograms/ permanent;
+
+#Grid
+rewrite /guidelines/2x-grid/implementation/ /guidelines/2x-grid/usage/ permanent;
\ No newline at end of file
diff --git a/package.json b/package.json
index 1d4ee1e2c57..e572bd54047 100644
--- a/package.json
+++ b/package.json
@@ -11,7 +11,7 @@
"nohoist": []
},
"scripts": {
- "dev": "gatsby develop -H 0.0.0.0",
+ "dev": "NODE_OPTIONS='--max-old-space-size=8192' gatsby develop -H 0.0.0.0",
"dev:clean": "gatsby clean && yarn dev",
"clean": "gatsby clean",
"build": "node --max-old-space-size=8192 ./node_modules/.bin/gatsby build",
@@ -40,11 +40,12 @@
"dependencies": {
"@babel/core": "^7.15.8",
"@carbon/charts-react": "0.55.0",
- "@carbon/elements": "^11.27.0-rc.0",
- "@carbon/icons-react": "^11.24.0-rc.0",
- "@carbon/pictograms": "^12.21.0-rc.0",
- "@carbon/pictograms-react": "^11.47.0-rc.0",
- "@carbon/react": "^1.35.0-rc.0",
+ "@carbon/elements": "^11.32.2",
+ "@carbon/icons": "^11.29.2",
+ "@carbon/icons-react": "^11.29.2",
+ "@carbon/pictograms": "^12.25.2",
+ "@carbon/pictograms-react": "^11.51.2",
+ "@carbon/react": "^1.41.2",
"@loadable/component": "^5.15.2",
"@slack/web-api": "^5.11.0",
"babel-preset-env": "^1.7.0",
@@ -57,7 +58,7 @@
"gatsby": "^4.25.7",
"gatsby-image": "^3.7.1",
"gatsby-plugin-image": "^2.9.0",
- "gatsby-theme-carbon": "^3.1.4",
+ "gatsby-theme-carbon": "^3.1.27",
"lodash-es": "^4.17.15",
"markdown-it": "^12.3.2",
"nanoid": "^2.1.11",
@@ -115,7 +116,6 @@
]
},
"resolutions": {
- "webpack": "^5.59.0",
- "@carbon/react": "1.35.0-rc.0"
+ "webpack": "^5.59.0"
}
}
diff --git a/src/components/ColorPalette/ColorPalette.module.scss b/src/components/ColorPalette/ColorPalette.module.scss
index f4ff8b4c95b..c4c99342203 100644
--- a/src/components/ColorPalette/ColorPalette.module.scss
+++ b/src/components/ColorPalette/ColorPalette.module.scss
@@ -80,7 +80,9 @@
}
.palette-switcher
- :global(.cds--content-switcher-btn:not(.cds--content-switcher--selected):hover) {
+ :global(
+ .cds--content-switcher-btn:not(.cds--content-switcher--selected):hover
+ ) {
background-color: $hover-ui;
}
diff --git a/src/components/SVGLibraries/PictogramLibrary/PictogramCategory.js b/src/components/SVGLibraries/PictogramLibrary/PictogramCategory.js
index 928ef45136c..9085239788c 100644
--- a/src/components/SVGLibraries/PictogramLibrary/PictogramCategory.js
+++ b/src/components/SVGLibraries/PictogramLibrary/PictogramCategory.js
@@ -27,7 +27,10 @@ const IconCategory = ({ category, pictograms, columnCount }) => {
pictogram.name === 'ibm--z' ||
pictogram.name === 'ibm--z--partition' ||
pictogram.name === 'ibm--z-and-linuxone-multi-frame' ||
- pictogram.name === 'ibm--z-and-linuxone-single-frame'
+ pictogram.name === 'ibm--z-and-linuxone-single-frame' ||
+ pictogram.name === 'watsonx--ai' ||
+ pictogram.name === 'watsonx--data' ||
+ pictogram.name === 'watsonx--governance'
) {
return false;
}
diff --git a/src/components/StorybookDemo/StorybookDemo.js b/src/components/StorybookDemo/StorybookDemo.js
new file mode 100644
index 00000000000..9f7b5ee1372
--- /dev/null
+++ b/src/components/StorybookDemo/StorybookDemo.js
@@ -0,0 +1,174 @@
+/*
+ * Copyright IBM Corp. 2022, 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.
+ */
+
+import React from 'react';
+import { unstable__FluidDropdown as FluidDropdown, Link } from '@carbon/react';
+import { Caption, Row, Column } from 'gatsby-theme-carbon';
+import cx from 'classnames';
+import PropTypes from 'prop-types';
+import { useState } from 'react';
+
+import * as styles from './StorybookDemo.module.scss';
+
+const themeItems = [
+ {
+ id: 'white',
+ label: 'White',
+ src: 'white',
+ },
+ {
+ id: 'g10',
+ label: 'Gray 10',
+ src: 'g10',
+ },
+ {
+ id: 'g90',
+ label: 'Gray 90',
+ src: 'g90',
+ },
+ {
+ id: 'g100',
+ label: 'Gray 100',
+ src: 'g100',
+ },
+];
+
+/**
+ * The `` component displays an iframe embed for the storybook story
+ * for a component. It has the option to show different variants and themes. It also has a
+ * `wide` prop to span the full width, and `tall` for larger components. If you would like
+ * to use the theme selector, please use the Carbon React Storybook url,
+ * https://react.carbondesignsystem.com/?path=/story/components-button--default&globals=theme:g10
+ * as an example. The `themeSelctor` appends `&globals=theme:g10` to the url.
+ */
+const StorybookDemo = ({ tall, themeSelector, wide, url, variants }) => {
+ const columnWidth = wide ? 12 : 8;
+
+ const demoClassNames = cx(styles.demo, {
+ [styles.tall]: tall,
+ [styles.wide]: wide,
+ });
+
+ const [theme, setTheme] = useState(themeItems[0].src);
+ const onThemeChange = (item) => {
+ setTheme(item.selectedItem.src);
+ };
+
+ const multipleVariants = variants?.length > 1;
+
+ const variantsDefined =
+ typeof variants !== 'undefined' && variants.length > 0;
+
+ const initialSetVariant = variantsDefined && variants[0].variant;
+
+ const [variant, setVariant] = useState(initialSetVariant);
+
+ const onVariantChange = (item) => {
+ setVariant(item.selectedItem.variant);
+ };
+
+ const iframeUrl =
+ url + '/iframe.html?id=' + variant + '&globals=theme:' + theme;
+
+ // Only add border when theme and variant selectors are being displayed
+ const border = cx({
+ [styles.themeSelector]: multipleVariants,
+ });
+
+ return (
+ <>
+
+ {themeSelector && (
+
+
+
+ )}
+ {variantsDefined && multipleVariants && (
+
+
+
+ )}
+
+
+
+
+
+
+
+ This live demo contains only a preview of functionality and styles
+ available for this component. View the{' '}
+
+ full demo
+ {' '}
+ on Storybook for additional information such as its version, controls,
+ and API documentation.
+
;
+ }
+}
+
+ArticleCard.propTypes = {
+ /**
+ * Action icon, default is blank, options are Launch, ArrowRight, Download
+ */
+ actionIcon: PropTypes.string,
+
+ /**
+ * Author
+ */
+ author: PropTypes.string,
+
+ children: PropTypes.node,
+
+ /**
+ * Specify a custom class
+ */
+ className: PropTypes.string,
+
+ /**
+ * set to "dark" for dark background card
+ */
+ color: PropTypes.string,
+
+ /**
+ * date
+ */
+ date: PropTypes.string,
+
+ /**
+ * Use for disabled card
+ */
+ disabled: PropTypes.bool,
+
+ /**
+ * Set url for card
+ */
+ href: PropTypes.string,
+
+ /**
+ * Reat time of article
+ */
+ readTime: PropTypes.string,
+
+ /**
+ * sub title
+ */
+ subTitle: PropTypes.string,
+
+ /**
+ * Title
+ */
+ title: PropTypes.string,
+};
+
+ArticleCard.defaultProps = {
+ color: 'light',
+ disabled: false,
+ actionIcon: '',
+};
diff --git a/src/gatsby-theme-carbon/components/ArticleCard/article-card.scss b/src/gatsby-theme-carbon/components/ArticleCard/article-card.scss
new file mode 100644
index 00000000000..280a5d25c32
--- /dev/null
+++ b/src/gatsby-theme-carbon/components/ArticleCard/article-card.scss
@@ -0,0 +1,142 @@
+// $carbon--white-0
+@use '@carbon/react/scss/colors' as *;
+// $spacing-0X
+@use '@carbon/react/scss/spacing' as *;
+// carbon--type-style
+@use '@carbon/react/scss/type' as *;
+// color tokens
+@use '@carbon/react/scss/compat/theme' as *;
+// $standard-easing $transition-x
+@use '@carbon/react/scss/motion' as *;
+// carbon--breakpoint
+@use '@carbon/react/scss/breakpoint' as *;
+
+.cds--article-card .cds--tile {
+ height: 100%;
+ padding: 0;
+ position: relative;
+ transition: background $duration-fast-01;
+ text-decoration: none;
+ border: 1px solid $border-tile-01;
+
+ @include breakpoint('lg') {
+ margin-bottom: var(--space);
+ }
+}
+
+.cds--article-card__tile {
+ border-top: 1px solid $border-tile-01;
+ padding: $spacing-05 25% $spacing-05 $spacing-05;
+}
+
+// Dark
+.cds--article-card--dark .cds--article-card__tile {
+ background: $gray-90; //$ui-background for gray 90 theme
+}
+
+.cds--article-card:hover .cds--article-card__tile {
+ background: $hover-ui;
+}
+
+.cds--article-card__title {
+ @include type-style('body-short-02');
+ text-decoration: none;
+ color: $text-01;
+}
+
+.cds--article-card__subtitle {
+ @include type-style('heading-01');
+ font-weight: 400;
+ text-decoration: none;
+ color: $text-01;
+}
+
+.cds--article-card__info {
+ position: absolute;
+ bottom: 1rem;
+ left: 1rem;
+ padding: 0;
+ color: $text-02;
+}
+
+.cds--article-card__info p {
+ @include type-style('label-01');
+}
+
+// At the moment, we force 16:9 for medium posts, this
+// is how we would force 16:9 for all article cards
+// .cds--article-card__img {
+// aspect-ratio: 16 / 9;
+// }
+
+.cds--article-card__img .gatsby-resp-image-wrapper {
+ margin-bottom: 0;
+}
+
+.cds--article-card__icon--action {
+ position: absolute;
+ bottom: 1rem;
+ right: 1rem;
+ width: 20px;
+ height: 20px;
+}
+
+.cds--article-card__icon--action svg {
+ fill: $icon-01;
+}
+
+.cds--article-card--dark:hover .cds--article-card__tile {
+ background: $gray-80; //$hover-ui for gray 90 theme
+}
+
+.cds--article-card--dark .cds--article-card__title,
+.cds--article-card--dark .cds--article-card__subtitle {
+ color: $text-04;
+}
+
+.cds--article-card--dark .cds--article-card__info {
+ color: $gray-30; //$text-02 for gray 90 theme
+}
+
+.cds--article-card--dark .cds--article-card__icon--action svg {
+ fill: $gray-10; //$icon-01 for grsay 90 theme
+}
+
+// Disabled
+.cds--article-card--disabled {
+ cursor: not-allowed;
+}
+
+.cds--article-card--disabled .cds--article-card__tile:hover {
+ background: $ui-01;
+ cursor: not-allowed;
+}
+
+.cds--article-card--disabled .cds--article-card__title,
+.cds--article-card--disabled .cds--article-card__subtitle,
+.cds--article-card--disabled .cds--article-card__info {
+ color: $disabled-03;
+}
+
+.cds--article-card--disabled .cds--article-card__icon--action svg {
+ fill: $disabled-02;
+}
+
+// Disabled dark
+.cds--article-card--disabled.cds--article-card--dark
+ .cds--article-card__tile:hover {
+ background: $gray-90; //$ui-background for gray 90 theme
+}
+
+.cds--article-card--disabled.cds--article-card--dark .cds--article-card__title,
+.cds--article-card--disabled.cds--article-card--dark
+ .cds--article-card__subtitle,
+.cds--article-card--disabled.cds--article-card--dark .cds--article-card__info {
+ color: $gray-50; //$disabled-03 for gray 90
+}
+
+.cds--article-card--disabled.cds--article-card--dark
+ .cds--article-card__icon--action
+ svg {
+ fill: $gray-70; //$disabled-02 for gray 90
+}
diff --git a/src/gatsby-theme-carbon/components/ArticleCard/index.js b/src/gatsby-theme-carbon/components/ArticleCard/index.js
new file mode 100644
index 00000000000..d730790f128
--- /dev/null
+++ b/src/gatsby-theme-carbon/components/ArticleCard/index.js
@@ -0,0 +1,3 @@
+import ArticleCard from './ArticleCard';
+
+export default ArticleCard;
diff --git a/src/gatsby-theme-carbon/components/MDXProvider/defaultComponents.js b/src/gatsby-theme-carbon/components/MDXProvider/defaultComponents.js
index 887bbb2f612..c285adf226b 100644
--- a/src/gatsby-theme-carbon/components/MDXProvider/defaultComponents.js
+++ b/src/gatsby-theme-carbon/components/MDXProvider/defaultComponents.js
@@ -1,18 +1,16 @@
import defaultComponents from 'gatsby-theme-carbon/src/components/MDXProvider/defaultComponents';
import MdxIcon from '../../../components/MdxIcon';
-import ComponentDemo from '../../../components/ComponentDemo';
-import ComponentVariant from '../../../components/ComponentDemo/ComponentVariant';
import ColorPalette from '../../../components/ColorPalette';
import Profile from '../../../components/Profile';
import ListSection from '../../../components/ListSection';
+import StorybookDemo from '../../../components/StorybookDemo';
export default {
...defaultComponents,
- ComponentDemo,
- ComponentVariant,
MdxIcon,
ColorPalette,
Profile,
ListSection,
+ StorybookDemo,
};
diff --git a/src/gatsby-theme-carbon/templates/Homepage.js b/src/gatsby-theme-carbon/templates/Homepage.js
index 030113bfec8..e79c5ac26dc 100644
--- a/src/gatsby-theme-carbon/templates/Homepage.js
+++ b/src/gatsby-theme-carbon/templates/Homepage.js
@@ -30,7 +30,7 @@ const SecondRightText = () => (
We welcome all feedback, designs, or ideas in order to produce the best
possible experience for our users. If youβre interested in contributing,
check out our contributing guidelines to get started.
-
+
Start contributing β
diff --git a/src/pages/all-about-carbon/releases.mdx b/src/pages/all-about-carbon/releases.mdx
index d3dae487e03..275c54d46ec 100755
--- a/src/pages/all-about-carbon/releases.mdx
+++ b/src/pages/all-about-carbon/releases.mdx
@@ -67,12 +67,12 @@ experience standards. For more details about this release, see our
## Release history
-| Carbon Design System | IBM Design Language | Carbon Elements | Carbon Components | Carbon React |
-| -------------------- | ------------------- | --------------- | ----------------- | ------------ |
-| [Carbon v11](https://www.carbondesignsystem.com) β 31 Mar 2022 β Improves token and prop naming β Adds light/dark mode support β Uses CSS grid | [IDL v2](https://www.ibm.com/design/language) | v11.x | v11.x | v8.x |
-| [Carbon v10](https://v10.carbondesignsystem.com) β 29 Mar 2019 β Updates assets to IDL v2 β Updates grid to 16 columns β Adds Carbon Elements package | [IDL v2](https://www.ibm.com/design/language) | [v10.x](https://www.npmjs.com/package/@carbon/elements/v/latest) | [v10.x](https://www.npmjs.com/package/carbon-components/v/latest) | [v7.x](https://www.npmjs.com/package/carbon-components-react/v/latest) |
-| [Carbon v9](https://v9.carbondesignsystem.com) β 4 June 2018 | IDL v1 | β | [v9.x](https://www.npmjs.com/package/carbon-components/v/9.x) | [v6.x](https://www.npmjs.com/package/carbon-components-react/v/6.x) |
-| [Carbon v8](https://v8.carbondesignsystem.com) β 26 Oct 2017 | IDL v1 | β | [v8.23.1](https://www.npmjs.com/package/carbon-components/v/8.23.1) | [v5.x](https://www.npmjs.com/package/carbon-components-react/v/5.x) |
-| [Carbon v7](https://v7.carbondesignsystem.com) β 30 Mar 2017 | IDL v1 | β | [v7.26.10](https://www.npmjs.com/package/carbon-components/v/7.26.10) | [v4.2.2](https://www.npmjs.com/package/carbon-components-react/v/4.2.2) |
-| [Carbon v6](https://v6.carbondesignsystem.com) | IDL v1 | β | [v6.20.1](https://www.npmjs.com/package/carbon-components/v/6.20.1) | [v3.14.0](https://www.npmjs.com/package/carbon-components-react/v/3.14.0) |
+| Carbon Design System | IBM Design Language | @carbon/elements | carbon-components | carbon-components-react | @carbon/react |
+| -------------------- | ------------------- | --------------- | ----------------- | ------------ | ------------ |
+| [Carbon v11](https://www.carbondesignsystem.com) β 31 Mar 2022 β Improves token and prop naming β Adds light/dark mode support β Uses CSS grid | [IDL v2](https://www.ibm.com/design/language) | [v11.x](https://www.npmjs.com/package/@carbon/elements/v/latest) | v11.x | [v8.x](https://www.npmjs.com/package/carbon-components-react/v/latest) | [v1.x](https://www.npmjs.com/package/@carbon/react/v/latest) |
+| [Carbon v10](https://v10.carbondesignsystem.com) β 29 Mar 2019 β Updates assets to IDL v2 β Updates grid to 16 columns β Adds Carbon Elements package | [IDL v2](https://www.ibm.com/design/language) | v10.x | [v10.x](https://www.npmjs.com/package/carbon-components/v/latest) | v7.x | β |
+| [Carbon v9](https://v9.carbondesignsystem.com) β 4 June 2018 | IDL v1 | β | [v9.x](https://www.npmjs.com/package/carbon-components/v/9.x) | [v6.x](https://www.npmjs.com/package/carbon-components-react/v/6.x) | β |
+| [Carbon v8](https://v8.carbondesignsystem.com) β 26 Oct 2017 | IDL v1 | β | [v8.23.1](https://www.npmjs.com/package/carbon-components/v/8.23.1) | [v5.x](https://www.npmjs.com/package/carbon-components-react/v/5.x) | β |
+| [Carbon v7](https://v7.carbondesignsystem.com) β 30 Mar 2017 | IDL v1 | β | [v7.26.10](https://www.npmjs.com/package/carbon-components/v/7.26.10) | [v4.2.2](https://www.npmjs.com/package/carbon-components-react/v/4.2.2) | β |
+| [Carbon v6](https://v6.carbondesignsystem.com) | IDL v1 | β | [v6.20.1](https://www.npmjs.com/package/carbon-components/v/6.20.1) | [v3.14.0](https://www.npmjs.com/package/carbon-components-react/v/3.14.0) | β |
diff --git a/src/pages/all-about-carbon/who-uses-carbon.mdx b/src/pages/all-about-carbon/who-uses-carbon.mdx
index 8632f51fe01..f6a703acf1f 100755
--- a/src/pages/all-about-carbon/who-uses-carbon.mdx
+++ b/src/pages/all-about-carbon/who-uses-carbon.mdx
@@ -58,7 +58,7 @@ Here are some ways designers can begin engaging with Carbon.
- Familiarize yourself with usage and style guidance for all of Carbon's
[components](/components/overview/) and [patterns](/patterns/overview/).
-- Check out [design tutorials](/designing/tutorials/) to learn more about some
+- Check out [design tutorials](/designing/get-started/) to learn more about some
of the foundational pieces of the design system.
#### Get the tools
diff --git a/src/pages/components/UI-shell-header/code.mdx b/src/pages/components/UI-shell-header/code.mdx
index e361aa67519..c4459342aa4 100644
--- a/src/pages/components/UI-shell-header/code.mdx
+++ b/src/pages/components/UI-shell-header/code.mdx
@@ -58,109 +58,38 @@ the Storybooks for each framework below.
-## Demo
-
-## Header base
-
-
-
-
-
-
-
-## Header with nav
-
-
-
-
-
-
-
-## Header with actions
-
-
-
-
-
-
-
-## Header with actions and nav
-
-
-
-
-
-
-
-## Header with sidenav
-
-
-
-
-
-
+## Live demo
+
+
diff --git a/src/pages/components/UI-shell-header/usage.mdx b/src/pages/components/UI-shell-header/usage.mdx
index 72b0f33b153..adb2d39ee57 100644
--- a/src/pages/components/UI-shell-header/usage.mdx
+++ b/src/pages/components/UI-shell-header/usage.mdx
@@ -70,24 +70,39 @@ independently, but the components were designed to work together.
## Live demo
-
-
-
-
-
+
## Formatting
diff --git a/src/pages/components/UI-shell-left-panel/code.mdx b/src/pages/components/UI-shell-left-panel/code.mdx
index 25f1650c37e..1db2653ba38 100644
--- a/src/pages/components/UI-shell-left-panel/code.mdx
+++ b/src/pages/components/UI-shell-left-panel/code.mdx
@@ -29,7 +29,7 @@ see the Storybooks for each framework below.
@@ -58,46 +58,33 @@ see the Storybooks for each framework below.
-## Demo
-
-## Fixed side-nav
-
-
-
-
-
-
-
-## Fixed side-nav with icons
-
-
-
-
-
-
+## Live Demo
+
+
diff --git a/src/pages/components/UI-shell-right-panel/code.mdx b/src/pages/components/UI-shell-right-panel/code.mdx
index 4683aaedff6..321254e1d28 100644
--- a/src/pages/components/UI-shell-right-panel/code.mdx
+++ b/src/pages/components/UI-shell-right-panel/code.mdx
@@ -26,6 +26,16 @@ documentation, see the Storybooks for each framework below.
+
+
+
+
+
+
+
-## Demo
-
-## Right panel
-
-
-
-
-
-
-
-## Right panel with switcher
+## Live Demo
-
-
-
-
-
+
diff --git a/src/pages/components/accordion/code.mdx b/src/pages/components/accordion/code.mdx
index 03efde3227a..a7e171139f2 100755
--- a/src/pages/components/accordion/code.mdx
+++ b/src/pages/components/accordion/code.mdx
@@ -61,36 +61,13 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
The accordion component delivers large amounts of content in a small space through progressive disclosure. The user gets key details about the underlying content and can choose to expand that content within the constraints of the accordion. Accordions work especially well on mobile interfaces or whenever vertical space is at a premium.
-
The accordion component delivers large amounts of content in a small space through progressive disclosure. The user gets key details about the underlying content and can choose to expand that content within the constraints of the accordion. Accordions work especially well on mobile interfaces or whenever vertical space is at a premium.
-
The accordion component delivers large amounts of content in a small space through progressive disclosure. The user gets key details about the underlying content and can choose to expand that content within the constraints of the accordion. Accordions work especially well on mobile interfaces or whenever vertical space is at a premium.
-
- `}
-
-
+/>
diff --git a/src/pages/components/accordion/usage.mdx b/src/pages/components/accordion/usage.mdx
index e65e27c0602..55f95e4bd97 100755
--- a/src/pages/components/accordion/usage.mdx
+++ b/src/pages/components/accordion/usage.mdx
@@ -49,39 +49,16 @@ extra click; instead use a full scrolling page with normal headers.
## Live demo
-
-
- {`
-
-
The accordion component delivers large amounts of content in a small space through progressive disclosure. The user gets key details about the underlying content and can choose to expand that content within the constraints of the accordion. Accordions work especially well on mobile interfaces or whenever vertical space is at a premium.
-
The accordion component delivers large amounts of content in a small space through progressive disclosure. The user gets key details about the underlying content and can choose to expand that content within the constraints of the accordion. Accordions work especially well on mobile interfaces or whenever vertical space is at a premium.
-
The accordion component delivers large amounts of content in a small space through progressive disclosure. The user gets key details about the underlying content and can choose to expand that content within the constraints of the accordion. Accordions work especially well on mobile interfaces or whenever vertical space is at a premium.
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/breadcrumb/code.mdx b/src/pages/components/breadcrumb/code.mdx
index 1fcd4609c30..4fc494412ae 100755
--- a/src/pages/components/breadcrumb/code.mdx
+++ b/src/pages/components/breadcrumb/code.mdx
@@ -60,53 +60,17 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- Breadcrumb 1
- Breadcrumb 2
- Breadcrumb 3
-
-`}
-
-
- {`
-
- Breadcrumb 1
- Breadcrumb 2
- Breadcrumb 3
-
-`}
-
-
+/>
diff --git a/src/pages/components/breadcrumb/usage.mdx b/src/pages/components/breadcrumb/usage.mdx
index 7666b309d20..ad6e497cf67 100755
--- a/src/pages/components/breadcrumb/usage.mdx
+++ b/src/pages/components/breadcrumb/usage.mdx
@@ -61,56 +61,20 @@ type used should be consistent across a product.
## Live demo
-
-
- {`
-
- Breadcrumb 1
- Breadcrumb 2
- Breadcrumb 3
-
-`}
-
-
- {`
-
- Breadcrumb 1
- Breadcrumb 2
- Breadcrumb 3
-
-`}
-
-
+/>
## Formatting
diff --git a/src/pages/components/button/code.mdx b/src/pages/components/button/code.mdx
index 1f3336dbac1..7253c4a2a1b 100755
--- a/src/pages/components/button/code.mdx
+++ b/src/pages/components/button/code.mdx
@@ -60,80 +60,37 @@ documentation, see the Storybooks for each framework below.
## Live demo
-import { Add } from '@carbon/react/icons';
-
-
-
- {`
-
- `}
-
-
- {`
-
- `}
-
-
- {`
-
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/button/usage.mdx b/src/pages/components/button/usage.mdx
index 68993497c30..46566f8a787 100755
--- a/src/pages/components/button/usage.mdx
+++ b/src/pages/components/button/usage.mdx
@@ -80,83 +80,40 @@ actions.
## Live demo
-import { Add } from '@carbon/react/icons';
-
-
-
- {`
-
- `}
-
-
- {`
-
- `}
-
-
- {`
-
-
-
- `}
-
-
+/>
## Formatting
@@ -419,7 +376,7 @@ Button groups are a useful way of aligning buttons that have a relationship.
Group the buttons logically into sets based on usage and importance. Too many
calls to action will overwhelm and confuse users so they should be avoided.
-As mentioned in the [Emphasis section](#Emphasis), you donβt necessarily need to
+As mentioned in the [Emphasis section](#emphasis), you donβt necessarily need to
use the buttons in the order that their labels imply. Either a secondary or a
tertiary button can be used in conjunction with a primary button. In fact, due
to the visual weight of the secondary button, itβs recommended to use tertiary
@@ -451,9 +408,9 @@ or ghost buttons in layouts with more than three calls to action.
Ideally, when using groups of related buttons (not including ghost buttons),
they should all be the same width. This can be achieved in one of two ways, both
of which are acceptable. The first approach involves using the
-[narrow grid mode](/guidelines/2x-grid/implementation#grid-modes). In this
+[narrow gutter mode](/guidelines/2x-grid/implementation#gutter-modes). In this
situation each button would be set individually on the column grid. _Note:
-Carbon developers are working on the narrow grid mode, currently left-hanging
+Carbon developers are working on the narrow gutter mode, currently left-hanging
buttons can only be achieved with an override._
@@ -501,7 +458,7 @@ container with a programmatic 16px gutter between them.
#### Horizontally arranged groups
When using multiple buttons, the position of the primary button adheres to the
-[alignment guidance](#Alignment) above. To sum up, a primary button will be
+[alignment guidance](#alignment) above. To sum up, a primary button will be
left-aligned and positioned to the left of the secondary/tertiary button on
full-page designs. The primary button will be right-aligned and appear to the
right of the secondary/tertiary button within wizards and dialog windows.
diff --git a/src/pages/components/checkbox/code.mdx b/src/pages/components/checkbox/code.mdx
index eb380ca740c..5c6d51cb253 100755
--- a/src/pages/components/checkbox/code.mdx
+++ b/src/pages/components/checkbox/code.mdx
@@ -60,33 +60,13 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-`}
-
-
+/>
diff --git a/src/pages/components/checkbox/usage.mdx b/src/pages/components/checkbox/usage.mdx
index 00fa29284c5..f823b8b0921 100755
--- a/src/pages/components/checkbox/usage.mdx
+++ b/src/pages/components/checkbox/usage.mdx
@@ -89,36 +89,16 @@ set whereas radio buttons allow the user to select only one option.
## Live demo
-
-
- {`
-
-`}
-
-
+/>
## Formatting
diff --git a/src/pages/components/code-snippet/code.mdx b/src/pages/components/code-snippet/code.mdx
index 4e7a2101708..f4c4ccc31a6 100755
--- a/src/pages/components/code-snippet/code.mdx
+++ b/src/pages/components/code-snippet/code.mdx
@@ -29,7 +29,7 @@ usage documentation, see the Storybooks for each framework below.
@@ -60,84 +60,24 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-import {
- codeSnippet,
- codeSnippetSingle,
-} from '../../../data/components/code-snippet.js';
-
-
-
- {`
-
- ${codeSnippetSingle}
-
-`}
-
-
- {`
-
- {\`${codeSnippet}\`}
-
- `}
-
-
- {`
- ${codeSnippetSingle}
-`}
-
-
+/>
## Sample data
diff --git a/src/pages/components/code-snippet/usage.mdx b/src/pages/components/code-snippet/usage.mdx
index fadad44b770..f90b4e6ab2e 100644
--- a/src/pages/components/code-snippet/usage.mdx
+++ b/src/pages/components/code-snippet/usage.mdx
@@ -60,77 +60,24 @@ length use casesβinline, single line, and multi-line.
## Live demo
-
-
- {`
- ${codeSnippetSingle}
-`}
-
-
- {`
-
- {\`${codeSnippet}\`}
-
-`}
-
-
- {`
- ${codeSnippetSingle}
-`}
-
-
+/>
## Formatting
diff --git a/src/pages/components/contained-list/ComponentDemo.js b/src/pages/components/contained-list/ComponentDemo.js
deleted file mode 100644
index eaf85815fe6..00000000000
--- a/src/pages/components/contained-list/ComponentDemo.js
+++ /dev/null
@@ -1,41 +0,0 @@
-import React from 'react';
-import ComponentDemo from '../../../components/ComponentDemo';
-import ComponentVariant from '../../../components/ComponentDemo/ComponentVariant';
-
-const components = [
- {
- id: 'contained-list',
- label: 'ContainedList',
- },
-];
-
-
-const knobs = {
- ContainedList: ['kind', 'size', 'isInset'],
-};
-
-const links = {
- React:
- 'https://react.carbondesignsystem.com/?path=/story/components-containedlist--default',
-};
-
-function ContainedListComponentDemo() {
- return (
-
-
- {`
-
-
- List item
- List item
- List item
- List item
-
-
- `}
-
-
- );
-}
-
-export default ContainedListComponentDemo;
diff --git a/src/pages/components/contained-list/accessibility.mdx b/src/pages/components/contained-list/accessibility.mdx
index 7fc2e6635fd..4200cfd6d44 100644
--- a/src/pages/components/contained-list/accessibility.mdx
+++ b/src/pages/components/contained-list/accessibility.mdx
@@ -9,18 +9,101 @@ tabs: ['Usage', 'Style', 'Code', 'Accessibility']
Design annotations are needed for specific instances shown below, but for the
-standard accordion component, Carbon already incorporates accessibility.
+standard contained list component, Carbon already incorporates accessibility.
-
-
-This page is underdevelopment. Please check back later for updates.
-
-
-
What Carbon providesDesign recommendationsDevelopment considerations
+
+## What Carbon provides
+
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
+
+### Keyboard interactions
+
+The default contained list is not interactive, but several of its variants
+include keyboard operation. In all interactive variants, the `Tab` key is used
+for navigation and both `Space` and `Enter` are used to activate components.
+
+Users tab between any actionable items in the list, regardless of whether each
+item is clickable or contains an action button (such as βdeleteβ). It is
+possible for multiple tab stops to exist for each list item.
+
+
+
+
+![The user tabs to each row of a clickable contained list.](images/contained-list-accessibility-1.png)
+
+
+ In a clickable contained list, each list item is a tab stop, activated with
+ Enter or Space.
+
+
+
+
+
+
+
+
+![The user tabs to each row of a clickable contained list.](images/contained-list-accessibility-2.png)
+
+
+ Where a contained list has buttons on each row, the buttons are in the tab
+ order.
+
+
+
+
+
+
+
+
+![The user tabs to the first row of a clickable contained list, and then tabs to an actionable item at the end of the same row.](images/contained-list-accessibility-3.png)
+
+
+ If a contained list contains both clickable rows and action items, there are
+ multiple tab stops on each row.
+
+
+
+
+
+## Design recommendations
+
+### Indicate when the contained list is clickable
+
+There is no persistent visual indicator that the list items in a contained list
+are clickable. To help developers distinguish them from the default contained
+list in your designs, annotate if each row in a list is intended to be
+clickable. There is no need to annotate clickable buttons on each row since
+these are visually identifiable.
+
+
+
+
+![Two contained lists, the first with a pink annotation reading "clickable rows", the second showing a button on each row, with no annotation](images/contained-list-accessibility-5.png)
+
+
+ Annotate if the rows of a contained list are clickable. Do not annotate if it
+ is only buttons on each row that are actionable.
+
+
+
+
+
+## Development considerations
+
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component.
+
+- The contained list is implemented as a list (usually a `
`) with each item
+ an `
`, and the list title associated with the list through use of
+ `aria-labelledby`.
+- Any operable variant, whether a clickable list or a list with action items, is
+ a `
-#### Condensed grid mode
+#### Condensed gutter mode
The data table can be used on a condensed grid, but care should be taken to
avoid any unintentional relationships with other UI elements. Use a hybrid grid
diff --git a/src/pages/components/date-picker/code.mdx b/src/pages/components/date-picker/code.mdx
index e3ff8e36a3d..c3bc1d96e92 100755
--- a/src/pages/components/date-picker/code.mdx
+++ b/src/pages/components/date-picker/code.mdx
@@ -29,7 +29,7 @@ usage documentation, see the Storybooks for each framework below.
@@ -60,140 +60,34 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
-
- `}
-
-
- {`
-
-
-
- `}
-
-
- {`
-
-
-
-
- `}
-
-
- {`
-
-
-
-
-
-
-
-
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/date-picker/usage.mdx b/src/pages/components/date-picker/usage.mdx
index 31d2e1e4b8c..dbf7ddece51 100755
--- a/src/pages/components/date-picker/usage.mdx
+++ b/src/pages/components/date-picker/usage.mdx
@@ -46,147 +46,41 @@ You can customize the time picker's format depending on location or need.
| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Simple date input](/components/date-picker/usage#simple-date-input) | Use if the date can be remembered by the user easily, such as a date of birth, and they donβt need a calendar to anticipate the dates. It consists only of input fields. |
| [Calendar picker](/components/date-picker/usage#calendar-pickers) | Use a calendar picker (single or range) when the user needs to know a date's relationship to other days or when a date could be variable. The user can view and pick dates from a calendar widget or manually type them in the text field. |
-| [Time picker](/date-picker/usage#time-pickers) | Use when asking the user to input a specific time. |
+| [Time picker](/components/date-picker/usage/#time-pickers) | Use when asking the user to input a specific time. |
## Live demo
-
-
- {`
-
-
-
- `}
-
-
- {`
-
-
-
- `}
-
-
- {`
-
-
-
-
- `}
-
-
- {`
-
-
-
-
-
-
-
-
-
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/dropdown/code.mdx b/src/pages/components/dropdown/code.mdx
index cd4e41af589..288a40bfb04 100755
--- a/src/pages/components/dropdown/code.mdx
+++ b/src/pages/components/dropdown/code.mdx
@@ -62,154 +62,56 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/form/code.mdx b/src/pages/components/form/code.mdx
index d0af55aa876..3316043062a 100755
--- a/src/pages/components/form/code.mdx
+++ b/src/pages/components/form/code.mdx
@@ -29,7 +29,7 @@ documentation, see the Storybooks for each framework below.
@@ -60,79 +60,19 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- `}
-
-
+/>
diff --git a/src/pages/components/form/images/form-usage-1.png b/src/pages/components/form/images/form-usage-1.png
index 67c212074e7..6039a610f52 100644
Binary files a/src/pages/components/form/images/form-usage-1.png and b/src/pages/components/form/images/form-usage-1.png differ
diff --git a/src/pages/components/form/images/form-usage-2.png b/src/pages/components/form/images/form-usage-2.png
index e89004a749f..76e6b7c36f6 100644
Binary files a/src/pages/components/form/images/form-usage-2.png and b/src/pages/components/form/images/form-usage-2.png differ
diff --git a/src/pages/components/form/images/form-usage-3-do.png b/src/pages/components/form/images/form-usage-3-do.png
index 0329514c881..623886f0d45 100644
Binary files a/src/pages/components/form/images/form-usage-3-do.png and b/src/pages/components/form/images/form-usage-3-do.png differ
diff --git a/src/pages/components/form/images/form-usage-3-dont.png b/src/pages/components/form/images/form-usage-3-dont.png
index cc9b20fa2af..9cf0fe814ce 100644
Binary files a/src/pages/components/form/images/form-usage-3-dont.png and b/src/pages/components/form/images/form-usage-3-dont.png differ
diff --git a/src/pages/components/form/images/form-usage-5.png b/src/pages/components/form/images/form-usage-5.png
index 6a3ded05343..7dab2cdb639 100644
Binary files a/src/pages/components/form/images/form-usage-5.png and b/src/pages/components/form/images/form-usage-5.png differ
diff --git a/src/pages/components/form/images/form-usage-optional.png b/src/pages/components/form/images/form-usage-optional.png
index c7b435b6c6d..552066a96a5 100644
Binary files a/src/pages/components/form/images/form-usage-optional.png and b/src/pages/components/form/images/form-usage-optional.png differ
diff --git a/src/pages/components/form/images/form-usage-required.png b/src/pages/components/form/images/form-usage-required.png
index 5d5e4896d9a..43694c20e06 100644
Binary files a/src/pages/components/form/images/form-usage-required.png and b/src/pages/components/form/images/form-usage-required.png differ
diff --git a/src/pages/components/form/usage.mdx b/src/pages/components/form/usage.mdx
index 4fb7f56b791..d03026d566f 100755
--- a/src/pages/components/form/usage.mdx
+++ b/src/pages/components/form/usage.mdx
@@ -36,82 +36,22 @@ configure and extend a form, see the
## Live demo
-
-
- {`
-
- `}
-
-
+/>
## Formatting
@@ -170,15 +110,15 @@ functionality but look visually different and have different alignment rules.
In a form, input components should vertically align with all other form
components. Whether a form aligns flush to grid columns or hangs in the gutters
-depends on the style of form input you are using as well as the grid mode.
-Default forms typically use a wide grid mode and align flush to the grid columns
-prioritizing vertical label alignment. Fluid forms use the condensed grid and
-can hang into the gutter without causing label misalignment. Fluid forms are
-architectural and remain cohesive by never allowing vertical or horizontal space
-between inputs.
+depends on the style of form input you are using as well as the gutter mode.
+Default forms typically use a wide gutter mode and align flush to the grid
+columns prioritizing vertical label alignment. Fluid forms use the condensed
+grid and can hang into the gutter without causing label misalignment. Fluid
+forms are architectural and remain cohesive by never allowing vertical or
+horizontal space between inputs.
-
+
![An example showing a properly aligned default inputs](images/form-usage-3-do.png)
@@ -191,7 +131,7 @@ between inputs.
-
+
![An example showing a properly stacked fluid inputs](images/form-usage-4-do.png)
@@ -207,10 +147,10 @@ between inputs.
If a form has more than one column, then the columns should be proportional and
align to grid columns when possible. The space between form columns is
-determined by the grid mode you are using; default forms use the wide grid mode
-with 32px padding between form columns, versus fluid forms use the condensed
-grid mode with 1px padding. The narrow grid mode (16px) is typically not used in
-forms as it often places the text in the gutter.
+determined by the gutter mode you are using; default forms use the wide gutter
+mode with 32px padding between form columns, versus fluid forms use the
+condensed gutter mode with 1px padding. The narrow gutter mode (16px) is
+typically not used in forms as it often places the text in the gutter.
diff --git a/src/pages/components/inline-loading/code.mdx b/src/pages/components/inline-loading/code.mdx
index 62d9c3010c8..da9a42fa314 100755
--- a/src/pages/components/inline-loading/code.mdx
+++ b/src/pages/components/inline-loading/code.mdx
@@ -59,31 +59,17 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- `}
-
-
+/>
diff --git a/src/pages/components/inline-loading/usage.mdx b/src/pages/components/inline-loading/usage.mdx
index 5a379b0c1b1..86a39011749 100755
--- a/src/pages/components/inline-loading/usage.mdx
+++ b/src/pages/components/inline-loading/usage.mdx
@@ -50,35 +50,20 @@ table, after a primary or secondary button click, or even in a modal.
## Live demo
-
-
- {`
-
- `}
-
-
-
+/>
## Formatting
### Anatomy
diff --git a/src/pages/components/link/code.mdx b/src/pages/components/link/code.mdx
index 61991400eb3..b01dc12efcc 100755
--- a/src/pages/components/link/code.mdx
+++ b/src/pages/components/link/code.mdx
@@ -60,29 +60,17 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
- Link
- `}
-
-
+/>
diff --git a/src/pages/components/link/usage.mdx b/src/pages/components/link/usage.mdx
index 1ac9c3b0036..7b036cd5352 100755
--- a/src/pages/components/link/usage.mdx
+++ b/src/pages/components/link/usage.mdx
@@ -59,32 +59,20 @@ be used for navigational actions.
## Live demo
-
-
- {`
- Link
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/list/code.mdx b/src/pages/components/list/code.mdx
index 0c913668d9b..e2ec6888f9e 100755
--- a/src/pages/components/list/code.mdx
+++ b/src/pages/components/list/code.mdx
@@ -28,7 +28,7 @@ documentation, see the Storybooks for each framework below.
@@ -59,90 +59,29 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
- Ordered list level 1
-
-
- Ordered list level 1
-
-
- Ordered list level 2
-
-
- Ordered list level 2
-
-
- Ordered list level 2
-
-
-
-
- Ordered list level 1
-
-
- `}
-
-
- {`
-
-
- Unordered list level 1
-
-
- Unordered list level 1
-
-
- Unordered list level 2
-
-
- Unordered list level 2
-
-
- Unordered list level 2
-
-
-
-
- Unordered list level 1
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/list/usage.mdx b/src/pages/components/list/usage.mdx
index a51cee597e6..43542e1eca3 100755
--- a/src/pages/components/list/usage.mdx
+++ b/src/pages/components/list/usage.mdx
@@ -25,103 +25,39 @@ number or a bullet.
## Overview
-Lists consist of related content grouped together and organized vertically.
-
-Use bulleted lists when you don't need to convey a specific order for list
-items.
-
+Lists consist of related content grouped together and organized vertically. Use
+bulleted lists when you don't need to convey a specific order for list items.
Use numbered lists when you need to convey a priority, hierarchy, or sequence
between list items.
## Live demo
-
-
- {`
-
-
- Ordered list level 1
-
-
- Ordered list level 1
-
-
- Ordered list level 2
-
-
- Ordered list level 2
-
-
- Ordered list level 2
-
-
-
-
- Ordered list level 1
-
-
- `}
-
-
- {`
-
-
- Unordered list level 1
-
-
- Unordered list level 1
-
-
- Unordered list level 2
-
-
- Unordered list level 2
-
-
- Unordered list level 2
-
-
-
-
- Unordered list level 1
-
-
- `}
-
-
+/>
## Variants
diff --git a/src/pages/components/loading/code.mdx b/src/pages/components/loading/code.mdx
index d6634e8899e..e0470489aa0 100755
--- a/src/pages/components/loading/code.mdx
+++ b/src/pages/components/loading/code.mdx
@@ -60,31 +60,13 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- `}
-
-
+/>
diff --git a/src/pages/components/loading/usage.mdx b/src/pages/components/loading/usage.mdx
index b3a8be1e181..7103b202941 100755
--- a/src/pages/components/loading/usage.mdx
+++ b/src/pages/components/loading/usage.mdx
@@ -34,34 +34,16 @@ three seconds.
## Live demo
-
-
- {`
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/modal/code.mdx b/src/pages/components/modal/code.mdx
index e0f9bc58530..6df9df1b6aa 100755
--- a/src/pages/components/modal/code.mdx
+++ b/src/pages/components/modal/code.mdx
@@ -60,155 +60,30 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse cursus fermentum risus, sit amet fringilla nunc pellentesque quis. Duis quis odio ultrices, cursus lacus ac, posuere felis. Donec dignissim libero in augue mattis, a molestie metus vestibulum. Aliquam placerat felis ultrices lorem condimentum, nec ullamcorper felis porttitor.
-
-`}
-
-
- {`
-
- <>
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
- >
-
-`}
-
-
- {`
-
-
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse cursus fermentum risus, sit amet fringilla nunc pellentesque quis. Duis quis odio ultrices, cursus lacus ac, posuere felis. Donec dignissim libero in augue mattis, a molestie metus vestibulum. Aliquam placerat felis ultrices lorem condimentum, nec ullamcorper felis porttitor.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse cursus fermentum risus, sit amet fringilla nunc pellentesque quis. Duis quis odio ultrices, cursus lacus ac, posuere felis. Donec dignissim libero in augue mattis, a molestie metus vestibulum. Aliquam placerat felis ultrices lorem condimentum, nec ullamcorper felis porttitor.
-
-`}
-
-
+/>
diff --git a/src/pages/components/modal/usage.mdx b/src/pages/components/modal/usage.mdx
index e16fe5c6738..83b45d75c57 100755
--- a/src/pages/components/modal/usage.mdx
+++ b/src/pages/components/modal/usage.mdx
@@ -71,158 +71,33 @@ destructive or irreversible then use a transactional danger modal.
## Live demo
-
-
- {`
-
-
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse cursus fermentum risus, sit amet fringilla nunc pellentesque quis. Duis quis odio ultrices, cursus lacus ac, posuere felis. Donec dignissim libero in augue mattis, a molestie metus vestibulum. Aliquam placerat felis ultrices lorem condimentum, nec ullamcorper felis porttitor.
-
-`}
-
-
- {`
-
- <>
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id accumsan augue. Phasellus consequat augue vitae tellus tincidunt posuere. Curabitur justo urna, consectetur vel elit iaculis, ultrices condimentum risus. Nulla facilisi. Etiam venenatis molestie tellus. Quisque consectetur non risus eu rutrum.
-
- >
-
-`}
-
-
- {`
-
-
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse cursus fermentum risus, sit amet fringilla nunc pellentesque quis. Duis quis odio ultrices, cursus lacus ac, posuere felis. Donec dignissim libero in augue mattis, a molestie metus vestibulum. Aliquam placerat felis ultrices lorem condimentum, nec ullamcorper felis porttitor.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse cursus fermentum risus, sit amet fringilla nunc pellentesque quis. Duis quis odio ultrices, cursus lacus ac, posuere felis. Donec dignissim libero in augue mattis, a molestie metus vestibulum. Aliquam placerat felis ultrices lorem condimentum, nec ullamcorper felis porttitor.
-
-`}
-
-
+/>
## Formatting
diff --git a/src/pages/components/notification/code.mdx b/src/pages/components/notification/code.mdx
index d5a0683545a..9ec9869ff32 100755
--- a/src/pages/components/notification/code.mdx
+++ b/src/pages/components/notification/code.mdx
@@ -29,7 +29,7 @@ usage documentation, see the Storybooks for each framework below.
@@ -60,70 +60,21 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- Subtitle text goes here. Example link}
- timeout={0}
- title="Notification title"
- />
-
-`}
-
-
- {`
-
- Action}
- iconDescription="describes the close button"
- subtitle={Subtitle text goes here. Example link}
- title="Notification title"
- />
-
-`}
-
-
+/>
diff --git a/src/pages/components/notification/usage.mdx b/src/pages/components/notification/usage.mdx
index cf13f960319..1b51666a323 100755
--- a/src/pages/components/notification/usage.mdx
+++ b/src/pages/components/notification/usage.mdx
@@ -65,73 +65,24 @@ although some product teams also support banners and notification centers.
## Live demo
-
-
- {`
-
- Subtitle text goes here. Example link}
- timeout={0}
- title="Notification title"
- />
-
-`}
-
-
- {`
-
- Action}
- iconDescription="describes the close button"
- subtitle={Subtitle text goes here. Example link}
- title="Notification title"
- />
-
-`}
-
-
+/>
## Formatting
diff --git a/src/pages/components/number-input/code.mdx b/src/pages/components/number-input/code.mdx
index 2f8aa02aa85..922e49a65c1 100755
--- a/src/pages/components/number-input/code.mdx
+++ b/src/pages/components/number-input/code.mdx
@@ -60,67 +60,17 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- `}
-
-
- {`
-
- `}
-
-
+/>
diff --git a/src/pages/components/number-input/usage.mdx b/src/pages/components/number-input/usage.mdx
index 66849873308..ec334d429a3 100755
--- a/src/pages/components/number-input/usage.mdx
+++ b/src/pages/components/number-input/usage.mdx
@@ -64,70 +64,20 @@ values.
## Live demo
-
-
- {`
-
- `}
-
-
- {`
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/overflow-menu/code.mdx b/src/pages/components/overflow-menu/code.mdx
index df72913faf2..4e47d80dcd1 100755
--- a/src/pages/components/overflow-menu/code.mdx
+++ b/src/pages/components/overflow-menu/code.mdx
@@ -60,46 +60,17 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
-
-
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/overflow-menu/usage.mdx b/src/pages/components/overflow-menu/usage.mdx
index 53aafc4af88..b443f9551fe 100755
--- a/src/pages/components/overflow-menu/usage.mdx
+++ b/src/pages/components/overflow-menu/usage.mdx
@@ -29,49 +29,20 @@ there is a space constraint.
## Live demo
-
-
- {`
-
-
-
-
-
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/pagination/code.mdx b/src/pages/components/pagination/code.mdx
index c687a21c3ef..2a036eed35a 100755
--- a/src/pages/components/pagination/code.mdx
+++ b/src/pages/components/pagination/code.mdx
@@ -60,53 +60,26 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/pagination/usage.mdx b/src/pages/components/pagination/usage.mdx
index 5d9549b6607..80d588ea22e 100755
--- a/src/pages/components/pagination/usage.mdx
+++ b/src/pages/components/pagination/usage.mdx
@@ -31,56 +31,29 @@ The default number displayed will vary depending on the context.
## Live demo
-
-
- {`
-
-
-
- `}
-
-
+/>
## Best practices
diff --git a/src/pages/components/popover/ComponentDemo.js b/src/pages/components/popover/ComponentDemo.js
deleted file mode 100644
index 2dc4f58b3b3..00000000000
--- a/src/pages/components/popover/ComponentDemo.js
+++ /dev/null
@@ -1,55 +0,0 @@
-import './styles.scss';
-
-import { Checkbox } from '@carbon/icons-react';
-import React from 'react';
-import ComponentDemo from '../../../components/ComponentDemo';
-import ComponentVariant from '../../../components/ComponentDemo/ComponentVariant';
-
-const content = `
-
-
-
-
-
-
-
Available storage
-
- This server has 150 GB of block storage remaining.
-
-
-
-
-`;
-
-const components = [
- {
- id: 'popover',
- label: 'Popover',
- },
-];
-
-const knobs = {
- Popover: ['align', 'caret', 'dropShadow', 'highContrast'],
-};
-
-const links = {
- React:
- 'https://react.carbondesignsystem.com/?path=/story/components-popover--playground',
-};
-
-function PopoverComponentDemo() {
- return (
-
-
- {content}
-
-
- );
-}
-
-export default PopoverComponentDemo;
diff --git a/src/pages/components/popover/code.mdx b/src/pages/components/popover/code.mdx
index 99139ba48c4..085cd0afcdf 100644
--- a/src/pages/components/popover/code.mdx
+++ b/src/pages/components/popover/code.mdx
@@ -5,8 +5,6 @@ description:
tabs: ['Usage', 'Style', 'Code']
---
-import PopoverComponentDemo from './ComponentDemo';
-
Preview the popover component with the React live demo. For detailed code usage
@@ -27,8 +25,32 @@ documentation, see the Storybooks for each framework below.
+
+
+
+
+
+
+
## Live demo
-
+
diff --git a/src/pages/components/popover/usage.mdx b/src/pages/components/popover/usage.mdx
index 5a749a62274..6f64bbef4d1 100644
--- a/src/pages/components/popover/usage.mdx
+++ b/src/pages/components/popover/usage.mdx
@@ -5,8 +5,6 @@ description:
tabs: ['Usage', 'Style', 'Code']
---
-import PopoverComponentDemo from './ComponentDemo';
-
A popover is a layer that pops up over all other elements on a page.
@@ -54,7 +52,21 @@ tooltips, overflow menus, and dropdown menus.
## Live demo
-
+
## Variants
diff --git a/src/pages/components/progress-bar/ComponentDemo.js b/src/pages/components/progress-bar/ComponentDemo.js
deleted file mode 100644
index 74906951cee..00000000000
--- a/src/pages/components/progress-bar/ComponentDemo.js
+++ /dev/null
@@ -1,55 +0,0 @@
-import React from 'react';
-import ComponentDemo from '../../../components/ComponentDemo';
-import ComponentVariant from '../../../components/ComponentDemo/ComponentVariant';
-
-const components = [
- {
- id: 'determinate',
- label: 'Determinate',
- },
- {
- id: 'indeterminate',
- label: 'Indeterminate',
- },
-];
-
-const knobs = {
- ProgressBar: ['hideLabel', 'size', 'status', 'type'],
-};
-
-const links = {
- React:
- 'https://react.carbondesignsystem.com/?path=/story/components-progressbar--playground',
-};
-
-function PopoverComponentDemo() {
- return (
-
-
- {`
-
-
-
- `}
-
-
- {`
-
-
-
- `}
-
-
- );
-}
-
-export default PopoverComponentDemo;
diff --git a/src/pages/components/progress-bar/code.mdx b/src/pages/components/progress-bar/code.mdx
index ce42ae6a365..1605b667ded 100644
--- a/src/pages/components/progress-bar/code.mdx
+++ b/src/pages/components/progress-bar/code.mdx
@@ -6,8 +6,6 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import ProgressBarComponentDemo from './ComponentDemo';
-
Preview the progress bar component with the React live demo. For detailed code
@@ -23,6 +21,16 @@ usage documentation, see the Storybooks for each framework below.
subTitle="React"
href="https://react.carbondesignsystem.com/?path=/story/components-progressbar--example"
>
+
+
+
+
+
+
+
@@ -30,4 +38,21 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
+
diff --git a/src/pages/components/progress-bar/usage.mdx b/src/pages/components/progress-bar/usage.mdx
index 38ed7cc1898..85774b12221 100644
--- a/src/pages/components/progress-bar/usage.mdx
+++ b/src/pages/components/progress-bar/usage.mdx
@@ -6,8 +6,6 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
-import ProgressBarComponentDemo from './ComponentDemo';
-
import localVideo from './videos/progress-bar-usage-4.mp4';
import localPoster from './images/progress-bar-usage-4.png';
@@ -67,7 +65,24 @@ how long a process will take, or if a request is being executed.
## Live demo
-
+
#### When to use
diff --git a/src/pages/components/progress-indicator/code.mdx b/src/pages/components/progress-indicator/code.mdx
index 60ac72b0034..315a647cc2f 100755
--- a/src/pages/components/progress-indicator/code.mdx
+++ b/src/pages/components/progress-indicator/code.mdx
@@ -61,60 +61,17 @@ code usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
-
-
-
-
-
-
-
-`}
-
-
+/>
diff --git a/src/pages/components/progress-indicator/usage.mdx b/src/pages/components/progress-indicator/usage.mdx
index 4722f2427f4..6bb3f3d8848 100755
--- a/src/pages/components/progress-indicator/usage.mdx
+++ b/src/pages/components/progress-indicator/usage.mdx
@@ -30,63 +30,20 @@ percentage of completeness as each task is completed.
## Live demo
-
-
- {`
-
-
-
-
-
-
-
-
-
-`}
-
-
+/>
## Best practices
diff --git a/src/pages/components/radio-button/code.mdx b/src/pages/components/radio-button/code.mdx
index ece181bf4e9..1c19100cb83 100755
--- a/src/pages/components/radio-button/code.mdx
+++ b/src/pages/components/radio-button/code.mdx
@@ -60,52 +60,13 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
-
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/radio-button/usage.mdx b/src/pages/components/radio-button/usage.mdx
index a46c06b836e..6133acf598a 100755
--- a/src/pages/components/radio-button/usage.mdx
+++ b/src/pages/components/radio-button/usage.mdx
@@ -73,55 +73,16 @@ checkboxes allow the user to select multiple items.
## Live demo
-
-
- {`
-
-
-
-
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/search/code.mdx b/src/pages/components/search/code.mdx
index 933b8cd178c..9b9c6e11554 100755
--- a/src/pages/components/search/code.mdx
+++ b/src/pages/components/search/code.mdx
@@ -60,32 +60,25 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- `}
-
-
diff --git a/src/pages/components/search/usage.mdx b/src/pages/components/search/usage.mdx
index 383e0549a2b..092ec38e98a 100755
--- a/src/pages/components/search/usage.mdx
+++ b/src/pages/components/search/usage.mdx
@@ -47,35 +47,28 @@ aid the user in finding content.
## Live demo
-
-
- {`
-
- `}
-
-
## Formatting
diff --git a/src/pages/components/select/code.mdx b/src/pages/components/select/code.mdx
index 069c33044c8..6ec834a2dfa 100755
--- a/src/pages/components/select/code.mdx
+++ b/src/pages/components/select/code.mdx
@@ -60,68 +60,21 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
- `}
-
-
+/>
diff --git a/src/pages/components/select/usage.mdx b/src/pages/components/select/usage.mdx
index 4c31f01ef95..fa50c016b07 100755
--- a/src/pages/components/select/usage.mdx
+++ b/src/pages/components/select/usage.mdx
@@ -85,71 +85,24 @@ the dropdown list can be styled as needed.
## Live demo
-
-
- {`
-
- `}
-
-
+/>
## Variants
diff --git a/src/pages/components/slider/code.mdx b/src/pages/components/slider/code.mdx
index 294c5d17b26..2c1749dae7a 100755
--- a/src/pages/components/slider/code.mdx
+++ b/src/pages/components/slider/code.mdx
@@ -60,40 +60,17 @@ documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
-
- `}
-
-
diff --git a/src/pages/components/slider/usage.mdx b/src/pages/components/slider/usage.mdx
index 811d95c9a7e..912a9272312 100755
--- a/src/pages/components/slider/usage.mdx
+++ b/src/pages/components/slider/usage.mdx
@@ -48,43 +48,20 @@ value range.
## Live demo
-
-
- {`
-
-
-
- `}
-
-
## Behaviors
diff --git a/src/pages/components/structured-list/code.mdx b/src/pages/components/structured-list/code.mdx
index 9ec9eb090c9..42970697537 100755
--- a/src/pages/components/structured-list/code.mdx
+++ b/src/pages/components/structured-list/code.mdx
@@ -62,169 +62,22 @@ code usage documentation, see the Storybooks for each framework below.
## Live demo
-
-
- {`
-
-
-
-
- ColumnA
-
-
- ColumnB
-
-
- ColumnC
-
-
-
-
-
-
- Row 1
-
-
- Row 1
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque vulputate nisl a porttitor interdum.
-
-
-
-
- Row 2
-
-
- Row 2
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque vulputate nisl a porttitor interdum.
-
-
-
-
- `}
-
-
- {`
-
-
-
- ColumnA
- ColumnB
- ColumnC
-
-
-
-
- Row 1
- Row 1
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui
- magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere
- sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque
- vulputate nisl a porttitor interdum.
-
- {}}
- />
-
-
- select an option
-
-
-
-
- Row 2
- Row 2
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui
- magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere
- sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque
- vulputate nisl a porttitor interdum.
-
- {}}
- />
-
-
- select an option
-
-
-
-
- Row 3
- Row 3
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui
- magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere
- sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque
- vulputate nisl a porttitor interdum.
-
- {}}
- />
-
-
- select an option
-
-
-
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/structured-list/usage.mdx b/src/pages/components/structured-list/usage.mdx
index 55a55111bd1..d781ba14484 100755
--- a/src/pages/components/structured-list/usage.mdx
+++ b/src/pages/components/structured-list/usage.mdx
@@ -57,172 +57,25 @@ which supports nesting items and presents a larger set of content.
import { CheckmarkFilled } from '@carbon/icons-react';
-
-
- {`
-
-
-
-
- ColumnA
-
-
- ColumnB
-
-
- ColumnC
-
-
-
-
-
-
- Row 1
-
-
- Row 1
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque vulputate nisl a porttitor interdum.
-
-
-
-
- Row 2
-
-
- Row 2
-
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque vulputate nisl a porttitor interdum.
-
-
-
-
- `}
-
-
- {`
-
-
-
- ColumnA
- ColumnB
- ColumnC
-
-
-
-
- Row 1
- Row 1
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui
- magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere
- sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque
- vulputate nisl a porttitor interdum.
-
- {}}
- />
-
-
- select an option
-
-
-
-
- Row 2
- Row 2
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui
- magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere
- sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque
- vulputate nisl a porttitor interdum.
-
- {}}
- />
-
-
- select an option
-
-
-
-
- Row 3
- Row 3
-
- Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc dui
- magna, finibus id tortor sed, aliquet bibendum augue. Aenean posuere
- sem vel euismod dignissim. Nulla ut cursus dolor. Pellentesque
- vulputate nisl a porttitor interdum.
-
- {}}
- />
-
-
- select an option
-
-
-
-
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/components/tabs/accessibility.mdx b/src/pages/components/tabs/accessibility.mdx
index 1a2737b8cdb..cde453a8caf 100644
--- a/src/pages/components/tabs/accessibility.mdx
+++ b/src/pages/components/tabs/accessibility.mdx
@@ -18,79 +18,136 @@ import {
-The tabs React Carbon component has been tested against the latest
-[W3C Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA success criteria](https://www.w3.org/TR/WCAG21/).
+Design annotations are needed for specific instances shown below, but for the
+standard tabs component, also called a tablist, Carbon already incorporates
+accessibility.
- Accessibility considerations
- Resources
- Accessibility testing
+ What Carbon provides
+ Design recommendations
+ Development considerations
-## Accessibility considerations
+## What Carbon provides
-1. Each tab must have a unique title that clearly describes tab panel content.
- This is particularly helpful for users of assistive technologies so they have
- the necessary information to efficiently navigate the content.
-2. Carbon components should be used to create the content that displays within
- each tab panel.
-3. Content authors need to ensure the content that is added to the tab panel is
- accessible. For example, if you add an image to the panel you need to include
- alternative text to pass accessibility testing.
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
-## Resources
+### Keyboard interactions
-- [W3C WAI-ARIA Tab Design Pattern](https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel)
- covers the usage of ARIA names, state and roles, as well as the expected
- keyboard interactions.
-- [IBM Accessibility Requirements](https://www.ibm.com/able/requirements/requirements/):
- - [1.3.1 Info and Relationships](https://www.ibm.com/able/requirements/requirements/#1_3_1)
- (WCAG Success Criteria
- [1.3.1](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships))
- - [1.3.2 Meaningful Sequence](https://www.ibm.com/able/requirements/requirements/#1_3_2)
- (WCAG Success Criteria
- [1.3.2](https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence))
+Tabs take at least two tabstops, one for the tablist and one for the tabpanel.
+When tabbing away from the tablist, focus will either go to the first operable
+element in the tabpanel or, where there are no operable elements, the entire
+tabpanel will take focus to support scrolling of its content.
-## Accessibility testing
+
+
-Automated, manual and screen reader accessibility verification test has been
-performed on the structure list React Carbon Component.
-[WCAG 2.1 Level A and AA success criteria](https://www.w3.org/TR/WCAG21/) issues
-have been identified and the list of open accessibility violations is available
-in the Carbon Component GitHub repository.
+![A user reaches the tablist with the Tab key. Pressing the Tab key again moves focus to a link inside the tabpanel's content](images/tab-accessibility-1a-do.png)
-### Automated test
+
+
+
+![A user tabs through a tablist. The focus goes from the tablist to the whole tabpanel, which contains only text.](images/tab-accessibility-1b-do.png)
+
+
+
+
+Arrow keys are used to navigate between individual tab items in the tablist.
+When the end of the tablist is reached, the focus wraps to the opposite end of
+the list. For scrollable tablists, where the number of tabs exceeds the
+horizontal space, the keyboard navigation does not change. The user presses the
+`Left` or `Right` arrow key, which moves the focus to the next tab item and,
+where necessary, scrolls the tablist to keep the selected item visible. For
+mouse users, clickable arrows appear at the end of the tablist to provide the
+same scrolling, but these are not needed for keyboard users and they are not in
+the focus order.
+
+
+
+
+
+![An image pair showing two views of the same tablist of 6 items. The user navigates between tab with left and right arrow keys. If the user presses the left arrow on the first item, the focus wraps around to item 6. Likewise arrowing right from tab item 6 moves to the first tab](images/tab-accessibility-4.png)
+
+
+ Arrow keys move between tabs in the tablist (wrapping from last back to first)
+ and scroll automatically to keep the focused tab visible.
+
+
+
+
+
+Automatic and manual tablists differ in how the tab items are activated. The
+following illustration shows what will happen for each variant when a right
+arrow key is pressed with the Overview tab selected and focused.
+
+For automatic tablists, focus and selection are synchronized. When the user
+arrows to a tab, it is selected, and the tabpanel under the tab is updated in
+real time.
+
+Manual tablists allow the user to arrow between the tab items without updating
+the tabpanel underneath. When the user right arrows, the Overview tab remains
+selected while focus moves to the Details tab. In order to select the Details
+tab (and update the tabpanel under the tab), the user would press `Enter` or
+`Space`.
+
+
+
+
+![Automatic and manual versions of a tablist with tabs called Overview, Details, and Support. In the first, the Details tab is selected and focused. In the second the Overview tab is still selected and the Details tab has a focus indicator](images/tab-accessibility-2.png)
+
+
+ After pressing the `Right Arrow` key, the second tab is selected in an
+ automatic tablist. For the manual tablist, Details has focus but Overview is
+ still selected. Pressing the Space or Enter key will select Details.
+
+
+
+
+
+## Design recommendations
+
+### Indicate which variant to implement
+
+The automatic and manual tablists are visually indistinguishable in a wireframe,
+so designers should annotate which variant the team has decided to implement.
+Since the choice primarily concerns technical considerations about potential
+latency when updating the tabpanelβs information, architects or developers
+should be involved in the discussion.
-
-
-
-
-
- Automated test environment
-
- Results
-
-
-
-
-
- - macOS Mojave version 10.14.6 with VoiceOver
-
- - Chrome version 77.0.3865.90
-
- - Dynamic Assessment Plugin (DAP) version 1.8.0.0 - IBM
- Accessibility WCAG 2.1 Sept. 2019 Ruleset
- - Carbon React version 7.7.1
-
-
- DAP test:
- - No violations
-
-
-
-
-
+
+
+![Two tabs, one with a pink annotation reading "auto", the other with an annotation "manual"](images/tab-accessibility-3.png)
+
+
+ Annotate whether the tabs should be implemented as automatic or manual.
+
+
+
+
+## Development considerations
+
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component.
+
+- Tabs are implemented as a `tablist`, with each tab item implemented as a
+ `` with a role of `tab`.
+- The selected tab has attributes `aria-selected="true"` and `tabindex="0"`. All
+ other tabs have these attribute values set to `"false"` and `"-1"`.
+- Each tab is associated with its tabpanel through `aria-controls`.
+- See the
+ [ARIA authoring practices guidance for tabs](https://w3c.github.io/aria-practices/#tabpanel)
+ for more considerations.
+- For accessibility considerations for manual tabs, see
+ [Deciding when to make selection automatically follow focus](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#kbd_selection_follows_focus).
diff --git a/src/pages/components/tabs/code.mdx b/src/pages/components/tabs/code.mdx
index 423160471a4..e07036f5eac 100755
--- a/src/pages/components/tabs/code.mdx
+++ b/src/pages/components/tabs/code.mdx
@@ -61,171 +61,41 @@ documentation, see the Storybooks for each framework below.
## Live demo
-import { Bat, Bee, Corn, Home, Monster } from '@carbon/react/icons';
-
-
-
- {`
-
-
-
- Tab Label 1
- Tab Label 2
- Tab Label 3
-
- Tab Label 4 with a very long long title
-
- Tab Label 5
-
-
- Tab Panel 1
-
- Tab Panel 2 Example button
-
- Tab Panel 3
- Tab Panel 4
- Tab Panel 5
-
-
-
-
-
- `}
-
-
+/>
diff --git a/src/pages/components/tile/usage.mdx b/src/pages/components/tile/usage.mdx
index 7b81f1bcb2c..5f67551f244 100755
--- a/src/pages/components/tile/usage.mdx
+++ b/src/pages/components/tile/usage.mdx
@@ -15,7 +15,7 @@ including information, getting started, how-to, next steps, and more.
-[Experimental tiles](https://react.carbondesignsystem.com/?path=/story/experimental-improved-contrast-tile--clickable)
+[Experimental tiles](https://react.carbondesignsystem.com/?path=/docs/experimental-feature-flags-tile--overview)
are now available. This addition enhances accessibility and only applies to the
visual appearance, not the function of tiles. Though we are not deprecating the
current tiles, we encourage all design teams to use the new experimental tiles
@@ -64,7 +64,7 @@ asset library (PAL) ecosystem below:
(Carbon for Cloud & Cognitive)
- [Dashboard cards](https://pages.github.ibm.com/ai-applications/design/patterns/dashboards-v2/overview/#dashboard-cards)
(AI Applications Design)
-- [Card](https://www.ibm.com/standards/carbon/components/card) (Carbon for
+- [Card](https://www.ibm.com/standards/carbon/components/cards) (Carbon for
IBM.com)
### When to use
@@ -92,209 +92,60 @@ elevation and are appropriate for this function instead.
## Live demo
-
-
- {`
-
- Default tile
-
- `}
-
-
- {`
-
- Clickable tile
-
- `}
-
-
- {`
-
-
- Radio tile
-
-
- Radio tile
-
-
- Radio tile
-
-
- `}
-
-
- {`
-
-
-
- `}
-
-
-
+/>
### Anatomy
diff --git a/src/pages/components/tooltip/code.mdx b/src/pages/components/tooltip/code.mdx
index ba3fd1af3a7..d5a9457ecea 100755
--- a/src/pages/components/tooltip/code.mdx
+++ b/src/pages/components/tooltip/code.mdx
@@ -60,67 +60,21 @@ documentation, see the Storybooks for each framework below.
## Live demo
-import { Information } from '@carbon/react/icons';
-
-
-
- {`
-
-
-
-
-
- `}
-
-
- {`
-
- Definition Tooltip
-
- `}
-
-
+/>
diff --git a/src/pages/components/tooltip/images/definition_tooltip_image.png b/src/pages/components/tooltip/images/definition_tooltip_image.png
deleted file mode 100644
index 0fa5c27f251..00000000000
Binary files a/src/pages/components/tooltip/images/definition_tooltip_image.png and /dev/null differ
diff --git a/src/pages/components/tooltip/images/interactive_tooltip.png b/src/pages/components/tooltip/images/interactive_tooltip.png
deleted file mode 100644
index d8d7394497e..00000000000
Binary files a/src/pages/components/tooltip/images/interactive_tooltip.png and /dev/null differ
diff --git a/src/pages/components/tooltip/images/tooltip-style-1.png b/src/pages/components/tooltip/images/tooltip-style-1.png
index 6bad4f729d5..2a2d74e9b2f 100644
Binary files a/src/pages/components/tooltip/images/tooltip-style-1.png and b/src/pages/components/tooltip/images/tooltip-style-1.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-style-2.png b/src/pages/components/tooltip/images/tooltip-style-2.png
index ceeb1c7c015..aaf77d9442f 100644
Binary files a/src/pages/components/tooltip/images/tooltip-style-2.png and b/src/pages/components/tooltip/images/tooltip-style-2.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-style-3.png b/src/pages/components/tooltip/images/tooltip-style-3.png
index 15b1fd5892b..d88b5b05714 100644
Binary files a/src/pages/components/tooltip/images/tooltip-style-3.png and b/src/pages/components/tooltip/images/tooltip-style-3.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-style-4.png b/src/pages/components/tooltip/images/tooltip-style-4.png
index 158cf629d04..f2474bd57af 100644
Binary files a/src/pages/components/tooltip/images/tooltip-style-4.png and b/src/pages/components/tooltip/images/tooltip-style-4.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-style-5.png b/src/pages/components/tooltip/images/tooltip-style-5.png
index dba34106add..a097f84ea8e 100644
Binary files a/src/pages/components/tooltip/images/tooltip-style-5.png and b/src/pages/components/tooltip/images/tooltip-style-5.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-style-6.png b/src/pages/components/tooltip/images/tooltip-style-6.png
index 46a9cbbfa1d..9814b3e3c0d 100644
Binary files a/src/pages/components/tooltip/images/tooltip-style-6.png and b/src/pages/components/tooltip/images/tooltip-style-6.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-style-7.png b/src/pages/components/tooltip/images/tooltip-style-7.png
index 5ab1e4aefab..0c83f4fbda5 100644
Binary files a/src/pages/components/tooltip/images/tooltip-style-7.png and b/src/pages/components/tooltip/images/tooltip-style-7.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-toggletip.png b/src/pages/components/tooltip/images/tooltip-toggletip.png
new file mode 100644
index 00000000000..2bc17986051
Binary files /dev/null and b/src/pages/components/tooltip/images/tooltip-toggletip.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-1.png b/src/pages/components/tooltip/images/tooltip-usage-1.png
deleted file mode 100644
index e495e2216ac..00000000000
Binary files a/src/pages/components/tooltip/images/tooltip-usage-1.png and /dev/null differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-10.png b/src/pages/components/tooltip/images/tooltip-usage-10.png
index ece5bf16a73..ab71ea12d40 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-10.png and b/src/pages/components/tooltip/images/tooltip-usage-10.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-12.png b/src/pages/components/tooltip/images/tooltip-usage-12.png
index 6f7d6bb70b3..d143ae818d2 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-12.png and b/src/pages/components/tooltip/images/tooltip-usage-12.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-13.png b/src/pages/components/tooltip/images/tooltip-usage-13.png
index b8c6dba1fa5..79dff64ee54 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-13.png and b/src/pages/components/tooltip/images/tooltip-usage-13.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-14.png b/src/pages/components/tooltip/images/tooltip-usage-14.png
index 2fce0a5e8a8..a6d4f98ddff 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-14.png and b/src/pages/components/tooltip/images/tooltip-usage-14.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-15.png b/src/pages/components/tooltip/images/tooltip-usage-15.png
index 6c41053f012..ec18ec8cbcd 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-15.png and b/src/pages/components/tooltip/images/tooltip-usage-15.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-2.png b/src/pages/components/tooltip/images/tooltip-usage-2.png
index 18bde41d3b0..5c28fc6e82f 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-2.png and b/src/pages/components/tooltip/images/tooltip-usage-2.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-3-do.png b/src/pages/components/tooltip/images/tooltip-usage-3-do.png
index 505558e8651..7d91154840d 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-3-do.png and b/src/pages/components/tooltip/images/tooltip-usage-3-do.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-3-dont.png b/src/pages/components/tooltip/images/tooltip-usage-3-dont.png
index e6fa7b4ad70..30501ff58bf 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-3-dont.png and b/src/pages/components/tooltip/images/tooltip-usage-3-dont.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-4-do.png b/src/pages/components/tooltip/images/tooltip-usage-4-do.png
index 86adb81a7f6..da1b55a66c5 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-4-do.png and b/src/pages/components/tooltip/images/tooltip-usage-4-do.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-4-dont.png b/src/pages/components/tooltip/images/tooltip-usage-4-dont.png
index d9df3b8ae99..63bd425d785 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-4-dont.png and b/src/pages/components/tooltip/images/tooltip-usage-4-dont.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-6.png b/src/pages/components/tooltip/images/tooltip-usage-6.png
index 83c833abe16..f4aa962d117 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-6.png and b/src/pages/components/tooltip/images/tooltip-usage-6.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-7.png b/src/pages/components/tooltip/images/tooltip-usage-7.png
index b330ef8c5b5..55de3ad3c9a 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-7.png and b/src/pages/components/tooltip/images/tooltip-usage-7.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-8.png b/src/pages/components/tooltip/images/tooltip-usage-8.png
index df59237553b..b88b2d28317 100644
Binary files a/src/pages/components/tooltip/images/tooltip-usage-8.png and b/src/pages/components/tooltip/images/tooltip-usage-8.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-standard-tooltip.png b/src/pages/components/tooltip/images/tooltip-usage-standard-tooltip.png
new file mode 100644
index 00000000000..86723802baa
Binary files /dev/null and b/src/pages/components/tooltip/images/tooltip-usage-standard-tooltip.png differ
diff --git a/src/pages/components/tooltip/images/tooltip-usage-standard.png b/src/pages/components/tooltip/images/tooltip-usage-standard.png
new file mode 100644
index 00000000000..54231f40546
Binary files /dev/null and b/src/pages/components/tooltip/images/tooltip-usage-standard.png differ
diff --git a/src/pages/components/tooltip/images/tooltip_placement.png b/src/pages/components/tooltip/images/tooltip_placement.png
deleted file mode 100644
index 0f4b794fca6..00000000000
Binary files a/src/pages/components/tooltip/images/tooltip_placement.png and /dev/null differ
diff --git a/src/pages/components/tooltip/style.mdx b/src/pages/components/tooltip/style.mdx
index 17ad30280f6..0ae3aab0f29 100755
--- a/src/pages/components/tooltip/style.mdx
+++ b/src/pages/components/tooltip/style.mdx
@@ -7,18 +7,34 @@ description:
tabs: ['Usage', 'Style', 'Code', 'Accessibility']
---
+
+
+The following page documents visual specifications such as color, typography,
+structure, and size.
+
+
+
+
+
+Color
+Typography
+Structure
+Feedback
+
+
+
## Color
-### Standard tooltip
+### Standard tooltip color
| Element | Property | Color token |
| -------------- | ---------------- | --------------------- |
-| Label | text color | `$text-secondary` |
+| Label | text-color | `$text-secondary` |
| Trigger button | svg | `$icon-secondary` |
| Container | background-color | `$background-inverse` |
-| Text | color | `$text-inverse` |
+| Text | text-color | `$text-inverse` |
-#### Interactive states
+#### Standard tooltip interactive states
@@ -31,7 +47,7 @@ tabs: ['Usage', 'Style', 'Code', 'Accessibility']
-![Closed and open states for a standard tooltip](images/tooltip-style-1.png)
+![Closed and open states for an icon button tooltip](images/tooltip-style-1.png)
@@ -41,17 +57,18 @@ tabs: ['Usage', 'Style', 'Code', 'Accessibility']
standard tooltip
-### Icon button tooltip
+### Icon button tooltip color
| Element | Property | Color token |
| --------- | ---------------- | --------------------- |
| Container | background-color | `$background-inverse` |
-| Text | color | `$text-inverse` |
+| Text | text-color | `$text-inverse` |
-#### Interactive states
+#### Icon button tooltip interactive states
Icon button tooltip states rely on what kind of button is being used. Refer to
-button styles for specific hover and focus states.
+[button styles](https://carbondesignsystem.com/components/button/style) for
+specific hover and focus states.
@@ -66,16 +83,16 @@ button styles for specific hover and focus states.
button tooltip
-### Definition tooltip
+### Definition tooltip color
| Element | Property | Color token |
| --------- | ---------------- | --------------------- |
-| Label | text color | `$text-secondary` |
+| Label | text-color | `$text-secondary` |
| Trigger | border | `$border-strong` |
| Container | background-color | `$background-inverse` |
-| Text | color | `$text-inverse` |
+| Text | text-color | `$text-inverse` |
-#### Interactive states
+#### Definition tooltip interactive states
@@ -95,14 +112,14 @@ button styles for specific hover and focus states.
Example of closed (top-left), hover (top-right), active (bottom-left) and
- focus (bottom-right) states for definition button tooltip
+ focus (bottom-right) states for definition tooltip
## Typography
Tooltip labels and text should be set in sentence case.
-| Element | Font-size (px/rem) | Font-weight | Type token |
+| Element | Font size (px/rem) | Font weight | Type token |
| --------- | ------------------ | ------------- | ----------- |
| Label | 12 / 0.75 | Regular / 400 | `$label-01` |
| Body text | 14 / 0.875 | Regular / 400 | `$body-01` |
@@ -112,9 +129,9 @@ Tooltip labels and text should be set in sentence case.
All tooltip types have a varying height based on the amount of content they
contain.
-### Standard tooltip
+### Standard tooltip structure
-| Element | Property | px / rem | Spacing token |
+| Class | Property | px / rem | Spacing token |
| ------------ | ------------- | -------- | ------------- |
| Container | max-width | 288 / 18 | β |
| | padding | 16 / 1 | `$spacing-05` |
@@ -132,7 +149,7 @@ contain.
Structure and spacing measurements for a standard tooltip | px / rem
-### Icon button tooltip
+### Icon button tooltip structure
| Class | Property | px / rem | Spacing token |
| --------- | --------------------------- | --------- | ------------- |
@@ -151,7 +168,7 @@ contain.
Structure and spacing measurements for an icon button tooltip | px / rem
-### Definition tooltip
+### Definition tooltip structure
| Element | Property | px / rem | Spacing token |
| --------- | --------------------------- | -------- | ------------- |
@@ -163,20 +180,20 @@ contain.
-![Structure and spacing measurements for definition tooltip](images/tooltip-style-6.png)
+![Structure and spacing measurements for a definition tooltip](images/tooltip-style-6.png)
- Structure and spacing measurements for definition tooltip | px / rem
+ Structure and spacing measurements for a definition tooltip | px / rem
-### Placement
+### Default placement
-Tooltip directions by default are set to auto. Upon opening, tooltips can detect
-the edges of the browser to properly be placed in view so the container does not
+Tooltip directions, by default, are set to auto. Upon opening, tooltips can
+detect the edges of the browser to be placed in view so the container does not
get cutoff. Tooltips can instead use specific directions and may be
-positionedΒ **top**,Β **right**, **bottom**,Β or **left**Β to the trigger item.
+positionedΒ **top**,Β **right**, **bottom**,Β or **left** of the trigger item.
Tooltips should be placed at least 16px / 1rem off of the bottom of the page and
not bleed off page or behind other content. On mobile, tooltips can only appear
below the tooltip icon.
@@ -188,3 +205,9 @@ below the tooltip icon.
Placement examples for a tooltip
+
+## Feedback
+
+Help us improve this component by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
diff --git a/src/pages/components/tooltip/usage.mdx b/src/pages/components/tooltip/usage.mdx
index 0c675369f38..23b5f54a547 100755
--- a/src/pages/components/tooltip/usage.mdx
+++ b/src/pages/components/tooltip/usage.mdx
@@ -8,9 +8,9 @@ tabs: ['Usage', 'Style', 'Code', 'Accessibility']
-Tooltips display additional information upon hover or focus. The information
-included should be contextual, helpful, and nonessential while providing that
-extra ability to communicate and give clarity to a user.
+Tooltips display additional information upon hover or focus that is contextual,
+helpful, and nonessential while providing the ability to communicate and give
+clarity to a user.
@@ -18,10 +18,10 @@ extra ability to communicate and give clarity to a user.
**v11 update:** The tooltip component has been refactored to use the
[popover](/components/popover/usage/) component under the hood to improve
-accessibility. Definition and interactive tootips now use the
+accessibility. Interactive tooltips now use the
[toggletip](/components/toggletip/usage/) component to achieve accessibility
-standards. For v10 implementation guidance, go to
-[v10 Tooltip](https://v10.carbondesignsystem.com/components/tooltip/usage/).
+standards. For v10 implementation guidance, see the
+[v10 tooltip](https://v10.carbondesignsystem.com/components/tooltip/usage/).
@@ -43,45 +43,35 @@ standards. For v10 implementation guidance, go to
## Overview
-A tooltip is a message box that is displayed when a user hovers over or gives
-focus to a UI element. The tool tip should be paired with an interactive UI
-element like a button. Tooltips should be used sparingly and contain succinct,
-supplementary information. Although Carbon tooltips used to allow for
-interactive elements such as buttons and links, do not include these elements in
-tooltips and use toggle tip instead.
+A tooltip is a message box displayed when a user hovers over or focuses on a UI
+element. A tooltip is used to provide more information and should be paired with
+an interactive UI element like a button. Tooltips should be used sparingly and
+contain succinct supplementary information. Do not include interactive elements
+in tooltips; use the toggletip component instead.
-![Example of tooltip being used with an information icon](images/tooltip-usage-1.png)
+![Image of a tooltip](images/tooltip-usage-2.png)
-
Example of standard tooltip
+
Image of a tooltip
### When to use
-- Describe icon buttons
-- When more information is useful in helping a user make decisions
+- To expose names of controls, like icon buttons, that lack visual labels
+- When an element can take focus and supplying additional information is useful
+ in helping a user make decisions
- When an element needs more context or explanation
- Use when defining a term or inline item
-
-
-
-![Example of tooltip being used to desribe an icon button](images/tooltip-usage-2.png)
-
-
-
-
-
Example of when to use tooltip to describe an icon button
-
### When not to use
- Since a tooltip disappears when a user hovers away, do not include information
- that is pertinent for the user to complete their task. Use helper text that is
- always visible and accessible for vital information such as required fields.
+ for the user to complete their task. Use helper text that is always visible
+ and accessible for vital information such as required fields.
- Do not include interactive elements within a tooltip. Interactive elements in
tooltips are inaccessible for some users and are hard to use for all users
since tooltips do not receive focus. If images, buttons, or links need to be
@@ -95,7 +85,7 @@ type="do"
colMd={6} colLg={6}
caption="Do use helper text for pertinent information.">
-![Example of using helper test rather than tooltip for pertinent information](images/tooltip-usage-3-do.png)
+![Example of using helper text rather than tooltip for pertinent information](images/tooltip-usage-3-do.png)
-![Example of buttons and links in a tooltip](images/tooltip-usage-4-dont.png)
+![Example of links in a tooltip](images/tooltip-usage-4-dont.png)
-#### Toggletips vs Tooltips
+#### Tooltips versus Toggletips
-Toggletips and tooltips are similar visually and both contain a popover and
-interactive trigger element. The two components differ in the way they are
-invoked and dismissed and if the user must interact with the contents. A tooltip
-is exposed on hover or focus when you need to expose brief, supplemental
-information that is not interactive. A toggletip is used on click or enter when
-you need to expose interactive elements, such as button, that a user needs to
-interact with.
+Tooltips and toggletips look visually similar, and both have an interactive
+trigger. The two components differ of how they are invoked and dismissed and if
+the user is required to interact with the contents. A tooltip is exposed on
+hover or focus when you need to disclose brief, supplemental information that is
+not interactive. A toggletip is used on click or enter when you must expose
+interactive elements, such as a button, that a user needs to interact with.
+
+
+
+
+![Example of a tooltip versus a toggletip](images/tooltip-toggletip.png)
+
+
+
+
+
Example of a tooltip versus a toggletip
### Variants
-| Variant | Purpose |
-| ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
-| [Standard tooltip](#standard-tooltip) | Provides nonessential, supplemental information to help a user make a decision |
-| [Icon button tooltip](#icon-button-tooltip) | Describes a button's function or action |
-| [Definition tooltip](#definition-tooltip) | Provides additional help or defines an item or term. It may be used on the label of a UI element, or on a word embedded in a paragraph. |
+| Variant | Purpose |
+| ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [Standard tooltip](#standard-tooltip) | Provides nonessential, supplemental information to help a user make a decision but is optional to interpret and will not prevent a user from completing a task or workflow. |
+| [Icon button tooltip](#icon-button-tooltip) | Describes a button's function or action. |
+| [Definition tooltip](#definition-tooltip) | Provides additional help or defines an item or term. It may be used on the label of a UI element, or on a word embedded in a paragraph. |
-
+
![Tooltip variants](images/tooltip-usage-12.png)
-## Live demo
+
+ Image of a standard tooltip, icon button tooltip, and definition tooltip
+
-import { Information } from '@carbon/react/icons';
+## Live demo
-
-
- {`
-
-
-
-
-
- `}
-
-
- {`
-
- Definition Tooltip
-
- `}
-
-
+/>
## Formatting
@@ -227,14 +184,15 @@ import { Information } from '@carbon/react/icons';
-![Standard tooltip anatomy](images/tooltip-usage-5.png)
+![Standard tooltip anatomy](images/tooltip-usage-standard.png)
-1. **UI trigger button:** Element that triggers a tooltip on hover or focus
-2. **Caret tip:** Closely associates container to specific trigger element
-3. **Container:** Contains helper text
+1. **UI trigger button:** Button that triggers a tooltip on hover or focus.
+2. **Caret tip:** Closely associates the container with the related trigger
+ element.
+3. **Container:** Contains helper text.
### Icon button tooltip anatomy
@@ -246,9 +204,10 @@ import { Information } from '@carbon/react/icons';
-1. **Icon button:** Button that triggers a tooltip on hover or focus
-2. **Caret tip:** Closely associates container to specific trigger element
-3. **Container:** Contains helper text
+1. **Icon button:** Button that triggers a tooltip on hover or focus.
+2. **Caret tip:** Closely associates the container with the related trigger
+ element.
+3. **Container:** Contains helper text.
### Definition tooltip anatomy
@@ -260,34 +219,38 @@ import { Information } from '@carbon/react/icons';
-1. **UI trigger:** Definition indicator: Underline below text that cues
-2. **Caret tip:** Closely associates container to term to be defined
-3. **Container:** Contains helper text
+1. **UI trigger button:** The definition indicator and underline that is dotted
+ and can be activated on hover or focus.
+2. **Caret tip:** Closely associates the container to term to be defined.
+3. **Container:** Contains helper text.
### Alignment
The container of the tooltip may be aligned toΒ **start**,Β **center**Β orΒ **end**
to keep the container from bleeding off the page or covering important
-information. The UI trigger button and caret tip should be vertically center
-with each other to clearly associate the tooltip and the trigger. This is
-especially helpful when multiple elements are close to each other.
+information. The UI trigger button and caret tip should be vertically centered
+with each other to associate the tooltip and the trigger. This is especially
+helpful when multiple elements are close to each other.
-![Image of tooltips aligned to start, center, and end](images/tooltip-usage-7.png)
+![Image of tooltips aligned to the start, center, or end](images/tooltip-usage-7.png)
-
Tooltip containers may be aligned toΒ start,Β centerΒ orΒ end
+
+ Tooltip containers can be automatically or manually positioned to the start,
+ center, or end
+
### Placement
-Tooltip directions by default are set to auto. Upon opening, tooltips can detect
-the edges of the browser to properly be placed in view so the container does not
+Tooltip directions, by default, are set to auto. Upon opening, tooltips can
+detect the edges of the browser to be placed in view so the container does not
get cutoff. Tooltips can instead use specific directions and may be
-positionedΒ **right**,Β **left**, **bottom**,Β or **top**Β to the trigger item. Do
+positionedΒ **right**,Β **left**, **bottom**,Β or **top**Β of the trigger item. Do
not cover related content that is essential to the user's tasks. Tooltips should
not bleed off page or behind other content.
@@ -300,22 +263,25 @@ not bleed off page or behind other content.
- Tooltip containers can be positioned to the right, left, bottom, or top.
+ Tooltip containers can be automatically or manually positioned to the right,
+ left, bottom, or top
-For toggletips that are inline with other text, like a definition toggletip, do
-not obstruct words to the left and right of the trigger word. When the toggletip
-is active, ensure popover overlays other content and is not cut off by other
-surrounding components or bleeds off the page where some content is not visible.
+For tooltips that are inline with other text, like a definition tooltip, do not
+obstruct words to the left and right of the trigger word. When the tooltip is
+active, ensure it overlays other content and is not cut off by other surrounding
+components or bleeds off the page where some content is not visible.
-![Image of definition tooltip positioned to the top](images/tooltip-usage-14.png)
+![Example of a definition tooltip positioned to the top](images/tooltip-usage-14.png)
+
Example of a definition tooltip positioned to the top
+
## Content
### Main elements
@@ -323,13 +289,13 @@ surrounding components or bleeds off the page where some content is not visible.
#### Text
- Should contain relevant, specific content.
-- Keep tooltips short and concise, no longer than a sentence or two.
-- Should not contain required information essential for a user to complete their
- task since a tooltip is not persistent.
-- Use sentence-style capitalization and write the text as full sentences with
- punctuation, unless space is limited.
-- Icon button tooltips that describe a button's function should only contain one
- or two words.
+- Should not contain essential task instructions since a tooltip is not
+ persistent.
+- Icon button tooltips should only contain one or two-word descriptions of a
+ button's function.
+- For definitions and instructive tooltips, use sentence-style capitalization
+ and write the text as complete sentences with punctuation unless space is
+ limited.
### Further guidance
@@ -350,49 +316,42 @@ and `enter`.
#### Mouse
Tooltips are triggered when the mouse hovers over or focuses on the UI trigger.
-The tooltip persists as long as the mouse remains over the active container or
-the UI trigger. The tooltip is dismissed by hovering away or moving focus to
-another element. Definition tooltip can additionally be activated on click or
-enter and dismissed by clicking outside of active container or UI element.
+The tooltip persists if the mouse remains over the active container or the UI
+trigger. The tooltip is dismissed by hovering away or moving focus to another
+element. The definition tooltip can be activated on click or and dismissed by
+clicking outside the active container or UI element.
#### Keyboard
-Users can trigger a tooltip by focusing on element. Addtionally, a definition
-tooltip can be triggered by using the `enter` key. A tooltip dismissible by use
-of the `escape` key.
-
-#### Screen readers
-
-VoiceOver: Users can trigger a button to open a popover by pressing `enter` or
-`space` while the button has focus.
-
-JAWS: Users can trigger a button to open a popover by pressing `enter` or
-`space` while the button has focus.
-
-NVDA: Users can trigger a button to open a popover by pressing `enter` or
-`space` while the button has focus.
+Users can trigger a tooltip by focusing on the element. Addtionally, a
+definition tooltip can be triggered by using the `enter` key. A tooltip is
+dismissible by the use of the `escape` key. For tooltips that reveal containers
+on focus, the container dissapears when focus moves away.
## Standard tooltip
-A standard tooltip is used to provide more information to help a user complete a
-task and is always paired with an interactive UI element such as a button or
-link.
+A standard tooltip provides additional information to further assist a user in
+completing a task and is paired with an interactive UI element such as a button
+or link.
### Best practices
-- Do not include interactive elements within a tooltip. If interactive elements
- are needed use a toggle tip instead.
-- Default tooltip content, such as when using an information icon, should be
- precise and related.
+- The content within a standard tooltip should be purely additional information
+ that is not critical for a user to read to complete a task. If the content is
+ essential for the user to interpret concerning their workflow, use a
+ [toggletip](https://carbondesignsystem.com/components/toggletip/usage/) for
+ this information instead.
-![Image of information icon tooltip](images/tooltip-usage-9.png)
+![Image of a standard tooltip](images/tooltip-usage-standard-tooltip.png)
+
Image of a standard tooltip
+
## Icon button tooltip
An icon button tooltip is used to describe the function or action of an icon
@@ -400,9 +359,10 @@ button that has no label to provide clarity on what the button will do.
### Best practices
-- Should only contain one or two words.
-- Should use icon button tooltip instead of the title attribute. Do not use
- both.
+- Tooltip content should only contain one or two words.
+- Use the icon button tooltip instead of the title attribute. Do not use both.
+- It is required to not include interactive elements within a tooltip. If
+ interactive elements are needed use a toggletip instead.
@@ -412,6 +372,8 @@ button that has no label to provide clarity on what the button will do.
+
Image of an icon button tooltip
+
## Definition tooltip
The definition tooltip provides inline additional help or defines a term. It may
@@ -419,18 +381,17 @@ be used on the label of a UI element, on a word embedded in a paragraph, or in
compact spaces such as data tables where icons clutter the UI. You can use
definition tooltips on headers, body copy, or labels.
-Definition tooltip is unique in that if offers both a hover or click interaction
-depending on specific use cases. If a user needs only a few seconds to gather
-their information and go, use a hover interaction. If a user needs time to think
-about the content or the tooltip is placed in a way that a user can
-unintentionally tigger the tooltip, then a click interaction would be more
+The definition tooltip is unique in that if offers both a hover or click
+interaction depending on specific use cases. If a user needs only a few seconds
+to gather their information and go, use a hover interaction. If a user needs
+time to think about the content or the tooltip is placed so that a user can
+unintentionally trigger the tooltip, then a click interaction would be more
appropriate.
### Best practices
-- Should contain brief, read-only text
-- Use on proper nouns, technical terms, or acronyms with two letters or more
-- Do not use a definition tooltip on words with fewer than two letters
+- Tooltip content should contain brief, read-only text.
+- Use on proper nouns, technical terms, or acronyms with two letters or more.
@@ -440,25 +401,31 @@ appropriate.
+
Image of a definition tooltip
+
## Related
#### Popover
Popovers are used as a base layer in some of our components like tooltips,
-overflow menus, and dropdown menus. For further guidance, see Carbon's popover
-component.
+overflow menus, and dropdown menus. For further guidance, see Carbon's
+[popover](https://carbondesignsystem.com/components/popover/usage/) component.
#### Disclosure
-Disclosures use popovers as a base layer. Disclosures are comprised of a popover
+Disclosures use popovers as a base layer. Disclosures are comprised of a
container, text, and interactive elements. Interactive elements are kept in the
-tab order of the page. For further guidance, see Carbon's disclosure pattern.
+tab order of the page. For further guidance, see Carbon's
+[disclosures](https://carbondesignsystem.com/patterns/disclosures-pattern/)
+pattern.
#### Toggletip
-Toggletip uses the disclosure pattern to toggle the visibility of a popover.
-This popover may contain a variety of information, from descriptive text to
-interactive elements. For further guidance, see Carbon's toggletip component.
+Toggletip uses the disclosure pattern to toggle the visibility of a popover and
+can contain a variety of information, from descriptive text to interactive
+elements. For further guidance, see Carbon's
+[toggletip](https://carbondesignsystem.com/components/toggletip/usage/)
+component.
#### Chart tooltip
@@ -476,12 +443,18 @@ more about using tooltips in charts.
+
Image of chart tooltips on a line graph
+
## References
Alita Joyce,
[Tooltip Guidelines](https://www.nngroup.com/articles/tooltip-guidelines/)
(Nielsen Norman Group, 2019)
+MDN Web Docs,
+[ARIA: tooltip role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/tooltip_role)
+(Mozilla: Developer contributors, 2023)
+
## Feedback
Help us improve this component by providing feedback, asking questions, and
diff --git a/src/pages/components/tree-view/code.mdx b/src/pages/components/tree-view/code.mdx
index 42cd79a7028..d579bc3fb14 100755
--- a/src/pages/components/tree-view/code.mdx
+++ b/src/pages/components/tree-view/code.mdx
@@ -30,265 +30,22 @@ usage documentation, see the Storybooks for each framework below.
## Live demo
-import { Document, Folder } from '@carbon/icons-react';
-
-
-
- {`
-
- `}
-
-
+/>
## Formatting
diff --git a/src/pages/contributing/add-ons.mdx b/src/pages/contributing/add-ons.mdx
deleted file mode 100644
index 47485d99144..00000000000
--- a/src/pages/contributing/add-ons.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Add-ons
-description:
- Carbon add-ons contain components, tools, and guidance that extend Carbon for
- a specific product or experience.
----
-
-import { CheckmarkFilled } from '@carbon/icons-react';
-
-
-
-Carbon add-ons
-Contributing to add-ons
-Ownership and maintenance
-
-
-
-## Carbon add-ons
-
-Carbon add-ons contain components, tools, and guidance that extend Carbon for a
-specific product or experience. Add-ons enable teams to create their own custom
-patterns and components that follow Carbon's visual style and guidelines.
-
-If your team is using Carbon and needs components specific to your product or
-industry, you should create a Carbon add-on.
-
-If you feel that your components and/or patterns could be used in other
-products, we encourage you to [contribute](/contributing/overview) your work
-back to Carbon.
-
-### Private vs public
-
-The Carbon Design System is an open-source project and we encourage teams using
-Carbon Design System to stay open-source as well. If your product has privacy
-constraints, there are options for creating an add-on repo under our GitHub
-Enterprise account.
-
-## Contributing to add-ons
-
-Add-ons are generally easier to contribute to because they are not fully managed
-by the Carbon team. For your add-on to be accepted, your components must meet
-WCAG AA standards and include interaction states (hover, active, focus, and
-disabled).
-
-## Ownership and maintenance
-
-If you build an add-on repo, it's your responsibility to maintain it. This
-involves carrying over changes from the core Carbon repo, as well as making sure
-it is using the latest major version of Carbon.
diff --git a/src/pages/contributing/bugs-and-requests.mdx b/src/pages/contributing/bugs-and-requests.mdx
deleted file mode 100644
index 81bcc4752e6..00000000000
--- a/src/pages/contributing/bugs-and-requests.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Bugs and requests
-description:
- Carbon tracks bugs and issues with GitHub. If you have a bug to report or wish
- to request a new feature, please check our existing issues before opening a
- new one.
----
-
-
-
-Checking for known issues
-Creating an issue
-Requests for comment
-Need more help?
-
-
-
-## Checking for known issues
-
-### GitHub
-
-We use GitHub to track our bugs. If you have a bug to report or wish to request
-a new feature, please check the
-[existing issues](https://github.com/carbon-design-system/carbon/issues) before
-opening a new one. There may already be something similar in the works.
-
-### Carbon website
-
-Please take some time to explore the content on this website before opening an
-issue. The site is comprehensive and most guidelines and components are well
-documented.
-
-## Creating an issue
-
-### GitHub issues
-
-Report bugs, request features, and leave feedback with a GitHub issue. If you're
-unsure which repo to use, please open an issue in the
-[Carbon monorepo](https://github.com/carbon-design-system/carbon).
-
-#### Carbon repos
-
-- [Carbon website](https://github.com/carbon-design-system/carbon-website/issues/new/choose)
-- [Carbon monorepo](https://github.com/carbon-design-system/carbon)
-- [Carbon Angular](https://github.com/IBM/carbon-components-angular/issues/new)
-- [Carbon Vue](https://github.com/carbon-design-system/carbon-components-vue/issues/new)
-- [Carbon charts (beta)](https://github.com/carbon-design-system/carbon-charts/issues/new)
-- [Carbon design kit](https://github.com/carbon-design-system/carbon-design-kit/issues/new)
-- [Carbon icons](https://github.com/carbon-design-system/carbon-icons/issues/new)
-
-### GitHub pull requests
-
-If you have a specific fix or contribution, start by generating a pull request
-in the appropriate [Carbon repo](/developing/dev-resources#github-repos). Here
-are detailed
-[instructions](https://github.com/carbon-design-system/carbon-website/wiki/Creating-a-PR-through-github.com-UI)
-for forking the repo and opening a pull request.
-
-## Requests for comment
-
-For changes that are larger in scale, an RFC (request for comment) may be
-appropriate. Read more about our
-[RFC process](https://github.com/carbon-design-system/rfcs).
-
-## Need more help?
-
-If you have more questions about issues or requesting features, there are
-multiple ways to reach us at [Contact us](/help/contact-us).
diff --git a/src/pages/contributing/code.mdx b/src/pages/contributing/code.mdx
new file mode 100644
index 00000000000..ac2adb7622b
--- /dev/null
+++ b/src/pages/contributing/code.mdx
@@ -0,0 +1,110 @@
+---
+title: Code
+description:
+ Code contributions can include anything from squashing bugs to adding feature
+ requests. Check out the instructions below to contribute code effectively.
+---
+
+export const Title = () => Contribute code;
+
+
+
+Code contributions can include anything from squashing bugs to adding feature
+requests. Check out the instructions below to contribute code effectively.
+
+
+
+
+
+Step 1: Find a project
+Step 2: Set up your environment
+Step 3: Refine the issue
+Step 4: Get feedback
+
+
+
+## Step 1: Find a project
+
+New issues submitted by the community are initially triaged by Carbon team
+members. Any issue that the Carbon team accepts, but can not fit in their
+roadmap, is open for community contribution.
+
+#### Volunteer for existing work
+
+The best way to volunteer is to look through
+[existing GitHub issues](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs%3A+community+contribution%22+)
+labeled with `needs: community contribution`. Any issue labeled with
+`needs: code contribution` is fair game! Put a comment in the issue saying you'd
+like to help.
+
+
+
+If you want to join an issue that is already assigned to someone or has a
+specific milestone, please discuss with the assignee of the issue or with the
+Carbon team to coordinate.
+
+Issues labeled `good first issue` are great candidates to pick up if you are in
+the code for the first time. The Carbon team is also happy to help you. Just
+stop by our [Carbon Developer office hours](/whats-happening/meetups/) or
+[contact us](/help/contact-us/) directly.
+
+#### Submit an idea or bug report
+
+Have a new idea that you think would benefit Carbon? Or do you need to report a
+bug? First, be sure to look through the
+[issue backlog](https://github.com/carbon-design-system/carbon/issues) to make
+sure it is a novel idea or bug. Then, file your proposal on GitHub using the
+[issue templates](https://github.com/carbon-design-system/carbon/issues/new/choose).
+If you're willing to work on this idea yourself, be sure to let us know in your
+issue! Your idea will then go through a triage process by the Carbon team.
+
+## Step 2: Set up your environment
+
+[Follow these steps](https://github.com/carbon-design-system/carbon/blob/main/.github/CONTRIBUTING.md)
+to install the tools, set up your environment, and learn how to make a pull
+request. You can explore all the repositories in the Carbon Design system
+[here](https://github.com/carbon-design-system), but you will likely be working
+in one of the following:
+
+- [Carbon website](https://github.com/carbon-design-system/carbon-website/)
+- [Carbon monorepo](https://github.com/carbon-design-system/carbon)
+- [Carbon Angular](https://github.com/IBM/carbon-components-angular/)
+- [Carbon Vue](https://github.com/carbon-design-system/carbon-components-vue/)
+- [Carbon charts](https://github.com/carbon-design-system/carbon-charts/)
+
+If you need help troubleshooting, [reach out](/help/contact-us/) to the Carbon
+team.
+
+## Step 3: Refine the issue
+
+Your dev environment is set up and you might be tempted to jump into coding.
+Before you get started, we recommend you refine the issue by creating a rough
+task list and posting it in the issue comments.
+
+If you have trouble answering any of these questions, reach out to the Carbon
+team and we will help you refine your issue:
+
+- Am I clear on the scope of this work?
+- Is this task list feasible for me to do?
+- Should a designer get involved to do initial research or create a design spec?
+- Do I need to collaborate with anyone else?
+
+## Step 4: Get feedback
+
+Most contributors work in groups of 2-3 and either set up weekly sessions or
+join [meetups](/whats-happening/meetups/#carbon-office-hours) such as the Data
+Viz Guild or Carbon Developer office hours. In these sessions, it is common to
+share work in progress and ask lots of questions. As you make progress, update
+your GitHub issue.
+
+Work that results in code will be reviewed directly in a pull request.
+Maintainers will be reviewing your work and making comments, asking questions
+and suggesting changes to be made before they merge your code. When you need to
+make a change, commit and push to your branch normally. Once all revisions to
+your pull request are complete, a maintainer will squash and merge your commits
+for you.
diff --git a/src/pages/contributing/component/images/content-switcher-style-1.png b/src/pages/contributing/component/images/content-switcher-style-1.png
deleted file mode 100644
index d79f8c22582..00000000000
Binary files a/src/pages/contributing/component/images/content-switcher-style-1.png and /dev/null differ
diff --git a/src/pages/contributing/component/images/contribution-iconography-pictogram.png b/src/pages/contributing/component/images/contribution-iconography-pictogram.png
deleted file mode 100644
index 4e4002a9a7e..00000000000
Binary files a/src/pages/contributing/component/images/contribution-iconography-pictogram.png and /dev/null differ
diff --git a/src/pages/contributing/component/images/spec.png b/src/pages/contributing/component/images/spec.png
deleted file mode 100644
index 5e08409d603..00000000000
Binary files a/src/pages/contributing/component/images/spec.png and /dev/null differ
diff --git a/src/pages/contributing/component/index.mdx b/src/pages/contributing/component/index.mdx
deleted file mode 100644
index 231a32dda8c..00000000000
--- a/src/pages/contributing/component/index.mdx
+++ /dev/null
@@ -1,1094 +0,0 @@
----
-title: Components
-description:
- Component contributions can take several forms. Most are either component
- enhancements or brand new assets.
----
-
-
-
-Component contributions can take several forms. Most are either component
-enhancements or brand new assets.
-
-
-
-
- How to write component guidance
- Parts of a component contribution
- First steps to contributing
-
-
-
-## How to write component guidance
-
-Our component usage documentation typically contains three parts: usage
-guidance, style guidance, and code guidance. Some components are more complex
-than others but you should cover each topic included in these templates.
-
-### Usage template: for components with one variant
-
-The usage template helps describe when to use a component and how it works. You
-can see this template in use for components with only one variant:
-[Accordion](/components/accordion/usage) and
-[Checkbox](/components/checkbox/usage).
-
-```markdown
----
-title: Component name
-description: Explains what the component is in one or two sentences.
-tabs: ['Usage', 'Style', 'Code', 'Accessibility']
----
-
-
-
-
-
-
-
-
-
-OverviewLive demo
-FormattingContent
-BehaviorsModifiers
-RelatedReferences
-Feedback
-
-
-
-## Overview
-
-
-
-### When to use
-
-
-
-### When not to use (optional)
-
-
-
-## Live demo
-
-
-
-## Formatting
-
-### Anatomy
-
-
-
-### Sizing (optional)
-
-
-
-### Alignment (optional)
-
-
-
-### Placement
-
-
-
-## Content
-
-### Main elements
-
-
-
-### Overflow content
-
-
-
-### Further guidance
-
-
-
-## Behaviors
-
-
-
-### States
-
-
-
-### Interactions
-
-
-
-### Validation
-
-
-
-### Responsive behavior
-
-
-
-### Default selection
-
-
-
-### Clickable areas
-
-
-
-### Loading
-
-
-
-## Modifiers
-
-
-
-## Related
-
-
-
-## References
-
-
-
-## Feedback
-
-
-
-Help us improve this component by providing feedback, asking questions, and
-leaving any other comments on
-[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
-```
-
-### Usage template: for components with multiple variants
-
-Use this template for documenting components that have multiple types or
-variants. You can see this template in use for
-[Dropdown](/components/dropdown/usage), [Modal](/components/modal/usage), and
-[Notification](/components/notification/usage).
-
-```markdown
----
-title: Component name
-description: Explains what the component is in one or two sentences.
-tabs: ['Usage', 'Style', 'Code', 'Accessibility']
----
-
-
-
-
-
-
-
-
-
-OverviewLive demo
-FormattingContent
-Universal behaviorsComponent type
-nameModifiers
-RelatedReferences
-Feedback
-
-
-
-## Overview
-
-
-
-### When to use
-
-
-
-### When not to use (optional)
-
-
-
-### Types
-
-
-
-## Live demo
-
-
-
-## Formatting
-
-
-
-### Sizing (optional)
-
-
-
-### Alignment (optional)
-
-
-
-### Placement
-
-
-
-## Content
-
-### Main elements
-
-
-
-### Overflow content (optional)
-
-
-
-### Further guidance
-
-For further content guidance, see Carbon's
-[content guidelines](<[https://www.carbondesignsystem.com/guidelines/content/general](https://www.carbondesignsystem.com/guidelines/content/general)>).
-
-## Universal behaviors
-
-
-
-### States
-
-
-
-### Interactions
-
-
-
-### Validation
-
-
-
-### Responsive behavior
-
-
-
-### Default selection
-
-
-
-### Clickable areas
-
-
-
-### Loading
-
-
-
-## Component type name
-
-
-
-## Modifiers
-
-
-
-## Related
-
-
-
-## References
-
-
-
-## Feedback
-
-Help us improve this component by providing feedback, asking questions, and
-leaving any other comments on
-[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
-```
-
-### Style template
-
-The style template helps describe how a component looks, including visual
-specifications such as color, typography, structure, and size.
-
-```markdown
----
-title: [Component name]
-description: [Explains what the component is in one or two sentences.]
-tabs: ['Usage', 'Style', 'Code', 'Accessibility']
----
-
-
-
-The following page documents visual specifications such as color, typography,
-structure, and size.
-
-
-
-
-
-ColorTypography
-StructureSize
-Feedback
-
-
-
-## Color
-
-
-
-| Element | Property | Color token |
-| ------- | ------------- | ------------------ |
-| Title | color | `$text-primary` |
-| Content | color | `$text-primary` |
-| Icon | fill | `$icon-primary` |
-| Header | border-top | `$border-subtle`\* |
-| | background | Transparent |
-| Panel | border-bottom | `$border-subtle`\* |
-| | background | Transparent |
-
-
- * Denotes a contextual color token that will change values based on the layer
- it is placed on.
-
-
-![Structure measurements for default accordion alignment](images/accordion-style-4.png)
-
-
-
-
- Structure measurements for default accordion alignment. | px / rem
-
-
-
-
-
-
-![Spacing measurements for default accordion alignment](images/accordion-style-5.png)
-
-
-
-
- Spacing measurements for default accordion alignment. | px / rem
-
-
-## Size
-
-
-
-There are six button sizes: small, medium, large productive, large expressive,
-extra large, and 2XL. The large expressive button is used in editorial and
-digital marketing experiences. See
-[Button sizes](/components/button/usage#button-sizes) on the Usage tab for more
-information about specific use cases for each button size.
-
-| Variant | Size | Height (px / rem) |
-| ----------------- | ---------------- | ----------------- |
-| Button | Small | 32 / 2 |
-| | Medium | 40 / 2.5 |
-| | Large productive | 48 / 3 |
-| | Large expressive | 48 / 3 |
-| Full bleed button | Extra large | 64 / 4 |
-| | 2xl | 80 / 5 |
-
-
-
-
-![Button sizes](images/button_usage_3.png)
-
-
-
-
-## Feedback
-
-
-
-Help us improve this component by providing feedback, asking questions, and
-leaving any other comments on
-[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
-```
-
-### Code template
-
-The code template helps developers implement your component. Be specific,
-include code snippets, and be sure to update as dependencies and versions
-change.
-
-```markdown
----
-title: Component name (you won't need to write this)
-description: Component description (you won't need to write this)
-tabs: ['Usage', 'Style', 'Code', 'Accessibility']
----
-
-
-
-
-
-
-
-
-
-Overview[Component use-case]
-Component APIReferences
-Feedback
-
-
-
-## Overview
-
-
-
-### Skeleton
-
-
-
-## [Use case, for example, Skeleton state or Sorting]
-
-
-
-## Component API
-
-### [Component name] props
-
-| Prop | Type | Required | Default | Description |
-| ----------- | -------- | -------- | ------- | ----------- |
-| `className` | `string` | β | β | β |
-
-
-
-#### [Component name][prop name]
-
-
-
-## References
-
-
-
-## Feedback
-
-Help us improve this component by providing feedback, asking questions, and
-leaving any other comments on
-[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
-```
-
-### Accessibility template
-
-The accessibility template helps designers and developers ensure components are
-accessible. The published information helps users understand all the
-accessibility considerations that are baked into Carbon. Refer to our guidance
-on creating the
-[keyboard interaction visuals](https://github.com/hiraaeth/component-contribution-accessibility/wiki/High-fidelity-keyboard-interaction-visuals).
-
-```markdown
----
-title: Component name (you won't need to write this)
-description: Component description (you won't need to write this)
-tabs: ['Usage', 'Style', 'Code', 'Accessibility']
----
-
-
-
-
-
-
-
-
- What Carbon provides
-
- Design recommendations
- Development considerations
-
-
-## What Carbon provides
-
-Carbon bakes keyboard operation into its components, improving the experience of
-blind users and others who operate via the keyboard. Carbon incorporates many
-other accessibility considerations, some of which are described below.
-
-### Keyboard interaction
-
-
-
-Each accordion is a tab stop. `Space` or `Enter` keys expand or collapse
-accordions, which are collapsed by default. Interactive elements within expanded
-accordions integrate into the tab order automatically.
-
-
-
-
-
-
-
-![example of (componet_name) keyboard interaction](images/component_name-accessibility-1.png)
-
-
- The (component_name) is reached by Tab and activated by Enter.
-
-
-
-
-
-
-
-## Design recommendations
-
-Design annotations are needed for the following instances.
-
-
-
-## Development considerations
-
-Keep these considerations in mind if you are modifying Carbon or creating a
-custom component.
-
-
-```
-
-## Parts of a component contribution
-
-Component contributions ideally include all of the following parts.
-
-#### 1. A rationale
-
-Explain how your component will add value to the system. Carbon serves the
-widest possible range of products, and contributions that increase the scope of
-the system are more likely to be accepted. Be sure to include any user
-experience and interaction descriptions.
-
-#### 2. A design spec
-
-Create sizing and styling annotations for all aspects of the component. This
-spec should provide a developer with everything they need to create the design
-in code. Check out our
-[production guidelines](https://github.com/carbon-design-system/carbon-website/wiki/Production-guidelines#spec-guidelines)
-to get started.
-
-You should include color tokens and type tokens used.
-
-
-
-
-![Example of a design spec](images/content-switcher-style-1.png)
-
-
Example of a design spec
-
-
-
-
-#### 3. A Sketch symbol
-
-Any new components or changes to existing components will also live in the
-[Carbon Sketch kit](/designing/kits/sketch) and so we'll need a Sketch symbol.
-Check out
-[Sketch's guide](https://www.sketch.com/docs/symbols/creating-symbols/) for
-creating a symbol.
-
-This symbol can be contributed with the asset or enhancement, but must be added
-to the kit by one of its maintainers. To contribute a symbol, simply open an
-issue in the
-[kit repo](https://github.com/carbon-design-system/carbon-design-kit/issues).
-
-#### 4. Usage documentation
-
-For guidance, see our
-[production guidelines](https://github.com/carbon-design-system/carbon-website/wiki/Production-guidelines#spec-guidelines)
-and [documentation templates](#documentation-templates) above. Reading through
-existing component documentation on the site will help also. Color and type
-tokens will live in the style tab.
-
-#### 5. Working code
-
-The component or enhancement must be built in one of our supported frameworks
-(Vanilla, React, Vue, or Angular). See the contribution guidelines for the
-specific repo you intend to contribute to.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-#### 6. Accessibility documentation
-
-Use this
-[component accessibility documentation](https://github.com/hiraaeth/component-contribution-accessibility/wiki/component-accessibility-documentation)
-to document the accessibility considerations to ensure the implemented component
-is usable by assistive technologies.
-
-#### 7. Code documentation
-
-Start with our [Code guidance](#code-guidance) template. We recommend reading
-through existing code documentation on this site for inspiration.
-
-## First steps to contributing
-
-To contribute a component to Carbon, start by
-[opening a Github issue](https://github.com/carbon-design-system/carbon/issues/new?assignees=&labels=type%3A+enhancement+%F0%9F%92%A1&template=feature-request-or-enhancement.md&title=).
-Include a detailed description in which you:
-
-- Explain the rationale
-- Detail the intended behavior
-- Clarify whether it's a variation of an existing component, or a new asset
-- Include mockups of any fidelity (optional)
-- Include any inspirations from other products (optional)
-
-This issue will be the staging ground for the contribution and an opportunity
-for the community to weigh in with any suggestions. We encourage you to surface
-work in progress. Someone in the community may be working on the same component
-and interested in collaborating with you.
diff --git a/src/pages/contributing/contribute-icons.mdx b/src/pages/contributing/contribute-icons.mdx
deleted file mode 100644
index e1ea11968ad..00000000000
--- a/src/pages/contributing/contribute-icons.mdx
+++ /dev/null
@@ -1,134 +0,0 @@
----
-title: Icons
-label:
- Icons are visual symbols used to represent ideas, objects, or actions. They
- communicate messages at a glance, afford interactivity, and draw attention to
- important information.
-description:
- Icons are visual symbols used to represent ideas, objects, or actions. They
- communicate messages at a glance, afford interactivity, and draw attention to
- important information.
----
-
-
-
-Design and production and guidelines
-Making an icon
-Exporting SVGs
-Contribution process
-
-
-
-## Design and production guidelines
-
-Don't see the icon you need in the library? Make your own! Follow these
-guidelines to ensure visual consistency and proper formatting.
-
-- All icons should be unique and not redundant with any existing icons in the
- system. Search the [library](/guidelines/icons/library) for the keyword(s)
- associated with your proposed new icon to ensure that it is not already
- represented.
-- All icons should adhere to the
- [IBM Design Language visual style](https://www.ibm.com/design/language/iconography/ui-icons/library).
-- All icons should comply with IBM
- [accessibility standards](/guidelines/accessibility/overview).
-- All icons should be usable across all supported platforms and devices.
-- All icons should be understandable by a global audience of users, regardless
- of nationality or language.
-
-## Making an icon
-
-- Create a 16 x 16 or 32 x 32 px artboard for each icon.
-- 16 px icons should have 1 px padding. 32 px icons should have 2 px padding.
-- Set your workspace up from the start to snap to pixels and round values to
- whole pixels to avoid correcting shapes later.
-- Never use center borders. Centering can cause half pixels.
-- Avoid using the line tool; use the rectangle tool instead. The line tool will
- place the vector on half pixels.
-- Be aware of automatic alignments which can place vectors on uneven or half
- pixels.
-- Ungroup icon layers completely. The icon should be on the top-most layer in
- your artboard.
-- Make sure to properly name layers and artboards _(these names will also be
- exported into the code)_.
-- Review the
- [icon master file](https://github.com/carbon-design-system/carbon/tree/v10/packages/icons/master)
- to see these guidelines in practice.
-
-### Production-ready
-
-To be considered production-ready, all icon submissions must be delivered in SVG
-format at 16 x 16 px (for integration with Carbon components) or 32 x 32 (for
-service icons).
-
-- Icons should be at whole pixels. No decimals are allowed in x and y
- coordinates or width and height fields.
-- Each artboard and the artwork within it must be aligned to the pixel grid.
-- All strokes must be expanded and at full pixel values.
-- All possible shapes and paths should be combined.
-
-## Exporting SVGs
-
-### Export SVGs from Adobe Illustrator.
-
-1. Draw a 16 x 16 or 32 x 32 px artboard. 16 px icons should have 1 px padding.
- 32 px icons should have 2 px padding.
-2. Place the icon squarely on the artboard, making sure it's aligned to the
- pixel grid.
-3. Expand all strokes `Object` β `Expand`.
-4. Select all overlapping shapes and click the "Unite" icon in the Pathfinder
- panel to merge all of the shapes together.
-5. Make sure the icon is at `#000000` and has no additional styling.
-6. Select `File` β `Save a Copy...` from the top navigation.
-7. On the `Format` dropdown select "SVG".
-8. Below `Format` select `Use Artboard`, then select either all or a range of
- artboards, depending on your need.
-9. Click `Save`.
-10. The `SVG Options` dialog will then open.
-11. Make sure the preferences are the same as in the image below.
-
-
-
-
-![export an icon from Illustrator](component/images/contribution-iconography-pictogram.png)
-
-
-
-
-## Contribution process
-
-Does your icon have potential for other products at IBM? If so, please consider
-contributing to the design system. IBM welcomes icon contributions to our
-iconography library. Youβre welcome to submit a single icon or a batch of icons
-for approval.
-
-### Getting started
-
-Before submitting artwork, first review our
-[icons library](https://www.carbondesignsystem.com/guidelines/icons/library/) or
-download the
-[Carbon icon master .ai file](https://github.com/carbon-design-system/carbon/tree/v10/packages/icons/master)
-to check your design for duplication against existing icons.
-
-### Approval process
-
-Icons for use within IBM must go through a design review process to ensure
-consistency and proper representation of the IBM brand across all environments.
-The process begins when you create a GitHub issue. Design review and approval
-typically take 14β21 days from issue creation, depending on the number of icons
-contributed.
-
-If your submission is accepted, the team will assign someone to your issue. If
-changes are needed, the team will note them in the issue and may return your
-submission with recommendations or suggest reworking the icon based on feedback
-from the Design System and Brand teams.
-
-Once the submission is approved it will then go through our process to be
-included into the Adobe Illustrator IBM Icon master file and be made available
-in the IBM Design Language and Carbon libraries.
-
-Submit icons for approval by creating a
-[single](https://github.ibm.com/brand/ui-icons/issues/new?assignees=&labels=&template=single-ui-icon-approval.md&title=%5Bui-icon%5D)
-or
-[batch](https://github.ibm.com/brand/ui-icons/issues/new?assignees=&labels=&template=batch-ui-icon-approval-request.md&title=%5Bui-icon-batch%5D)
-GitHub issue for your contribution.
diff --git a/src/pages/contributing/contribute-pictograms.mdx b/src/pages/contributing/contribute-pictograms.mdx
deleted file mode 100644
index 8b7c3a65684..00000000000
--- a/src/pages/contributing/contribute-pictograms.mdx
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: Pictograms
-description:
- Pictograms are visual symbols used to represent ideas, objects, or narratives
- at a glance. They work well in presentations and marketing communications.
----
-
-
-
-IBM's pictograms are visual symbols used to represent ideas, objects, or
-narratives. They can communicate messages at a glance, afford interactivity, and
-simplify complex ideas. They draw from details found in the Plex typeface and
-work well in presentations and marketing communications.
-
-
-
-
- Producing a pictogram
- Producing an icon
- Export SVGs from Adobe Illustrator
- Contribution process
-
-
-## Producing a pictogram
-
-Don't see the pictogram you need in the library? Make your own! Follow these
-guidelines to ensure visual consistency and proper formatting.
-
-- All pictograms should be unique and not redundant with any existing pictograms
- in the system. Look through the pictograms in the
- [Pictogram library](/guidelines/pictograms/library/) to ensure that your
- proposed new pictogram is not already represented.
-- All pictograms should adhere to the
- [IBM Design Language visual style](https://www.ibm.com/design/language/elements/pictograms/design).
-- All pictograms should comply with IBM
- [accessibility standards](/guidelines/accessibility/overview).
-- All pictograms should be usable across all supported platforms and devices.
-- All pictograms should be understandable by a global audience of users,
- regardless of nationality or language.
-
-## Producing an icon
-
-- Create a 32 x 32 px artboard for each pictogram.
-- 32 px pictograms should have 1 px padding.
-- Set your workspace up from the start to snap to grid.
-- Be aware of automatic alignments which can place vectors on uneven or half
- pixels.
-- The pictogram should be on the top-most layer in your artboard. Strokes should
- be grouped appropriately.
-- Make sure to properly name layers and artboards (these names will also be
- exported into the code).
-
-### Production-ready
-
-- To be considered production-ready, all pictogram submissions must be delivered
- in Adobe Illustrator format at 32 x 32 px with strokes kept intact.
-- Each artboard and the artwork within it must be aligned to the pixel grid
- wherever possible.
-- All strokes should be kept as is and not converted to shapes.
-- Group strokes logically whenever possible.
-
-## Export SVGs from Adobe Illustrator
-
-1. Draw a 32 x 32 px artboard. 32 px pictograms should have 1 px padding.
-1. Place the icon squarely on the artboard, making sure it's aligned to the
- pixel grid.
-1. Expand all strokes `Object > Expand`.
-1. Select all overlapping shapes and click the `Unite` icon in the `Pathfinder`
- panel to merge all of the shapes together.
-1. Make sure the icon is at `#000000` and has no additional styling.
-1. Select `File > Save a Copyβ¦` from the top navigation.
-1. On the `Format` dropdown select `SVG`.
-1. Below `Format` select `Use Artboard`, then select either all or a range of
- artboards, depending on your need.
-1. Click `Save`.
-1. The `SVG Options` dialog will then open.
-1. Make sure the preferences are the same as in the image below.
-
-
-
-
-![SVG export options image](component/images/contribution-iconography-pictogram.png)
-
-
-
-
-## Contribution process
-
-Does your pictogram have potential for other materials at IBM? If so, please
-consider contributing to the design system. IBM welcomes pictogram contributions
-in the form of a pull request to our pictogram repository. For now, to make a
-pull request,
-**[please submit an issue in the repo](https://github.ibm.com/brand/Pictograms/issues/new/choose)**
-with the pictogram attached.
-
-Please note that Carbon contribution is not required in order to introduce a new
-pictogram into your materials. If your pictogram is determined to be broadly
-useful in Carbon and passes IBM Brand design reviews, then it may also be
-integrated into the design system.
-
-If your submission is accepted, the team will notify you. If changes are needed,
-you'll need to create a new contribution issue after reworking it based on
-feedback from the Design System and Brand teams.
diff --git a/src/pages/contributing/design.mdx b/src/pages/contributing/design.mdx
new file mode 100644
index 00000000000..c5c975a10a4
--- /dev/null
+++ b/src/pages/contributing/design.mdx
@@ -0,0 +1,96 @@
+---
+title: Design
+description:
+ Design contributions can involve anything from creating design specs for
+ feature requests to maintaining Figma libraries. Below you'll find tips and
+ best practices to get started.
+---
+
+export const Title = () => Contribute design;
+
+
+
+Design contributions can involve anything from creating design specs for feature
+requests to maintaining Figma libraries. Below you'll find tips and best
+practices to get started.
+
+
+
+
+
+Step 1: Find a project
+Step 2: Refine the issue
+Step 3: Get feedback
+
+
+
+## Step 1: Find a project
+
+New issues submitted by the community are initially triaged by Carbon team
+members. Any issue that the Carbon team accepts, but can not fit in their
+roadmap, is open for community contribution.
+
+#### Volunteer for existing work
+
+The best way to volunteer is to look through
+[existing GitHub issues](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs%3A+community+contribution%22+)
+labeled with `needs: community contribution`. Any issue labeled with
+`needs: design contribution` is fair game! Put a comment in the issue saying
+you'd like to help.
+
+
+
+The most common design requests are related to feature enhancements: researching
+UX, creating visual solutions, and crafting a design spec are often required
+before a feature enhancement can be put into code.
+
+If you want to join an issue that is already assigned to someone or has a
+specific milestone, please discuss with the assignee of the issue or with the
+Carbon team to coordinate. Often contributors work in groups of 2-3.
+
+We also have many ongoing projects to create and update reusable components in
+Figma. This work is not currently tracked in GitHub, so check out the
+[status of design kits](https://www.figma.com/file/CFMtqV5Nztdbm0mi2UiDLg/Library-%2B-Template-Planning?type=design&node-id=3713-26762&mode=design&t=HqvAYXUeccKNMstT-0)
+and get involved by reaching out to the contacts listed.
+
+The Carbon team is also happy to help you. Just stop by our
+[Carbon Design office hours](/whats-happening/meetups/) or
+[contact us](/help/contact-us/) directly.
+
+#### Submit an idea
+
+Have a new idea that you think would benefit Carbon? Or do you need to report a
+bug? First, be sure to look through the
+[issue backlog](https://github.com/carbon-design-system/carbon/issues) to make
+sure it is a novel idea or bug. Then, file your proposal on GitHub using the
+[issue templates](https://github.com/carbon-design-system/carbon/issues/new/choose).
+If you're willing to work on this idea yourself, be sure to let us know in your
+issue! Your idea will then go through a triage process by the Carbon team.
+
+## Step 2: Refine the issue
+
+Whereas code contributions tend to be well defined, design contributions can be
+a little more ambiguous. We recommend you try writing a rough task list of what
+you believe your contribution will entail, and post it in the GitHub issue
+comments. In most cases, we recommend you then reach out to the Carbon team or
+come to Carbon Design office hours. We'll help you further refine your issue,
+clarify the scope of work, and connect you to other collaborators. Some good
+questions to ask yourself are:
+
+- Am I clear on the scope of this work?
+- Is this task list feasible for me to do?
+- Do I need to collaborate with anyone else?
+- Do I have a clear definition of done or a plan to pass this to a developer?
+
+## Step 3: Get feedback
+
+Most contributors work in groups of 2-3 and either set up weekly sessions or
+join [meetups](/whats-happening/meetups/#carbon-office-hours) such as the Data
+Viz Guild or Carbon Design office hours. In these sessions, it is common to
+share work in progress and ask lots of questions. In return, you'll get candid
+feedback and help. As you make progress, update your GitHub issue.
diff --git a/src/pages/contributing/documentation.mdx b/src/pages/contributing/documentation.mdx
index a03f7ef2cf9..519559768b9 100644
--- a/src/pages/contributing/documentation.mdx
+++ b/src/pages/contributing/documentation.mdx
@@ -1,71 +1,1380 @@
---
title: Documentation
description:
- You can contribute to the content on the Carbon site in a few different ways.
- Choose the way that works best, depending on how extensive your contribution
- is.
+ All components and patterns require usage, style, code, and accessibility
+ guidance on the Carbon website. Check out the markdown templates and
+ instructions below to contribute documentation smoothly.
---
+export const Title = () => Contribute docs;
+
-You can contribute to the content on the Carbon site in a few different ways.
-Choose the way that works best, depending on how extensive your contribution is.
-And be sure to read our content writing guidelines before you begin!
+All components and patterns require usage, style, code, and accessibility
+guidance on the Carbon website. Check out the markdown templates and
+instructions below to contribute documentation smoothly.
+Documenting components
+Documenting patterns
+Writing better content
+Publishing updates
+
+
+
+## Documenting components
+
+The website is written in markdown, which makes it easy for anyone to contribute
+content in a systematic way. Some components require more complex documentation
+than others, but you should cover each topic included in the following markdown
+templates: usage, style, code, and accessibility.
+
+Check out Carbon's handy markdown
+[styling cheatsheet](https://github.com/carbon-design-system/carbon-website/wiki/Markdown-cheatsheet)
+for how to style content.
+
+### Usage template: for components with one variant
+
+The usage template helps describe when to use a component and how it works. You
+can see this template in use for components with only one variant:
+[Accordion](/components/accordion/usage) and
+[Checkbox](/components/checkbox/usage).
+
+```markdown
+---
+title: Component name
+description: Explains what the component is in one or two sentences.
+tabs: ['Usage', 'Style', 'Code', 'Accessibility']
+---
+
+
-Editing pages
-Making regular content updates
-Content and style guidelines
+
+
+
+
+
+
+OverviewLive demo
+FormattingContent
+BehaviorsModifiers
+RelatedReferences
+Feedback
-## Editing pages
+## Overview
-The easiest way to edit a page is with the `Edit this page on Github` link that
-appears at the bottom of every page on the site. The link opens the specific
-Github page where you can edit the content and then propose the change with a
-pull request.
+
-If you are planning regular or more comprehensive content updates, you'll want
-to fork the repo and install some of the tools we use to build the website. This
-will create an easier workflow for you long term.
+### When to use
-Instructions for how to
-[install tools](https://github.com/carbon-design-system/carbon-website/wiki/Updating-content-on-carbondesignsystem.com)
-and fork the repo.
+
-Before you get started, take a moment to review our content guidelines.
-Following these will help us ensure consistency of experience across the site.
+### When not to use (optional)
-### Use Markdown
+
+
+## Live demo
+
+
+
+## Formatting
+
+### Anatomy
+
+
+
+### Sizing (optional)
+
+
+
+### Alignment (optional)
+
+
+
+### Placement
+
+
+
+## Content
+
+### Main elements
+
+
+
+### Overflow content
+
+
+
+### Further guidance
+
+
+
+## Behaviors
+
+
+
+### States
+
+
+
+### Interactions
+
+
+
+### Validation
+
+
+
+### Responsive behavior
+
+
+
+### Default selection
+
+
+
+### Clickable areas
+
+
+
+### Loading
+
+
+
+## Modifiers
+
+
+
+## Related
+
+
+
+## References
+
+
+
+## Feedback
+
+
+
+Help us improve this component by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
+```
+
+### Usage template: for components with multiple variants
+
+Use this template for documenting components that have multiple types or
+variants. You can see this template in use for
+[Dropdown](/components/dropdown/usage), [Modal](/components/modal/usage), and
+[Notification](/components/notification/usage).
+
+```markdown
+---
+title: Component name
+description: Explains what the component is in one or two sentences.
+tabs: ['Usage', 'Style', 'Code', 'Accessibility']
+---
+
+
+
+
+
+
+
+
+
+OverviewLive demo
+FormattingContent
+Universal behaviorsComponent type
+nameModifiers
+RelatedReferences
+Feedback
+
+
+
+## Overview
+
+
+
+### When to use
+
+
+
+### When not to use (optional)
+
+
+
+### Types
+
+
+
+## Live demo
+
+
+
+## Formatting
+
+
+
+### Sizing (optional)
+
+
+
+### Alignment (optional)
+
+
+
+### Placement
+
+
+
+## Content
+
+### Main elements
+
+
+
+### Overflow content (optional)
+
+
+
+### Further guidance
+
+For further content guidance, see Carbon's
+[content guidelines](<[https://www.carbondesignsystem.com/guidelines/content/general](https://www.carbondesignsystem.com/guidelines/content/general)>).
+
+## Universal behaviors
+
+
+
+### States
+
+
+
+### Interactions
+
+
+
+### Validation
+
+
+
+### Responsive behavior
+
+
+
+### Default selection
+
+
+
+### Clickable areas
+
+
+
+### Loading
+
+
+
+## Component type name
+
+
+
+## Modifiers
+
+
+
+## Related
+
+
+
+## References
+
+
+
+## Feedback
+
+Help us improve this component by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
+```
+
+### Style template
+
+The style template helps describe how a component looks, including visual
+specifications such as color, typography, structure, and size.
+
+```markdown
+---
+title: [Component name]
+description: [Explains what the component is in one or two sentences.]
+tabs: ['Usage', 'Style', 'Code', 'Accessibility']
+---
+
+
+
+The following page documents visual specifications such as color, typography,
+structure, and size.
+
+
+
+
+
+ColorTypography
+StructureSize
+Feedback
+
+
+
+## Color
+
+
+
+| Element | Property | Color token |
+| ------- | ------------- | ------------------ |
+| Title | color | `$text-primary` |
+| Content | color | `$text-primary` |
+| Icon | fill | `$icon-primary` |
+| Header | border-top | `$border-subtle`\* |
+| | background | Transparent |
+| Panel | border-bottom | `$border-subtle`\* |
+| | background | Transparent |
+
+
+ * Denotes a contextual color token that will change values based on the layer
+ it is placed on.
+
-### Guidelines for writing content
+![Structure measurements for default accordion alignment](images/accordion-style-4.png)
-Please keep these things in mind when writing content for Carbon.
+
+
+
+ Structure measurements for default accordion alignment. | px / rem
+
+
+
+
+
+
+![Spacing measurements for default accordion alignment](images/accordion-style-5.png)
+
+
+
+
+ Spacing measurements for default accordion alignment. | px / rem
+
+
+## Size
+
+
+
+There are six button sizes: small, medium, large productive, large expressive,
+extra large, and 2XL. The large expressive button is used in editorial and
+digital marketing experiences. See
+[Button sizes](/components/button/usage#button-sizes) on the Usage tab for more
+information about specific use cases for each button size.
+
+| Variant | Size | Height (px / rem) |
+| ----------------- | ---------------- | ----------------- |
+| Button | Small | 32 / 2 |
+| | Medium | 40 / 2.5 |
+| | Large productive | 48 / 3 |
+| | Large expressive | 48 / 3 |
+| Full bleed button | Extra large | 64 / 4 |
+| | 2xl | 80 / 5 |
+
+
+
+
+![Button sizes](images/button_usage_3.png)
+
+
+
+
+## Feedback
+
+
+
+Help us improve this component by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
+```
+
+### Code template
+
+The code template helps developers implement your component. Be specific,
+include code snippets, and be sure to update as dependencies and versions
+change.
+
+```markdown
+---
+title: Component name (you won't need to write this)
+description: Component description (you won't need to write this)
+tabs: ['Usage', 'Style', 'Code', 'Accessibility']
+---
+
+
+
+
+
+
+
+
+
+Overview[Component use-case]
+Component APIReferences
+Feedback
+
+
+
+## Overview
+
+
+
+### Skeleton
+
+
+
+## [Use case, for example, Skeleton state or Sorting]
+
+
+
+## Component API
+
+### [Component name] props
+
+| Prop | Type | Required | Default | Description |
+| ----------- | -------- | -------- | ------- | ----------- |
+| `className` | `string` | β | β | β |
+
+
+
+#### [Component name][prop name]
+
+
+
+## References
+
+
+
+## Feedback
+
+Help us improve this component by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
+```
+
+### Accessibility template
+
+The accessibility template helps designers and developers ensure components are
+accessible. The published information helps users understand all the
+accessibility considerations that are baked into Carbon. Refer to our guidance
+on creating the
+[keyboard interaction visuals](https://github.com/hiraaeth/component-contribution-accessibility/wiki/High-fidelity-keyboard-interaction-visuals).
+
+```markdown
+---
+title: Component name (you won't need to write this)
+description: Component description (you won't need to write this)
+tabs: ['Usage', 'Style', 'Code', 'Accessibility']
+---
+
+
+
+
+
+
+
+
+ What Carbon provides
+
+ Design recommendations
+ Development considerations
+
+
+## What Carbon provides
+
+Carbon bakes keyboard operation into its components, improving the experience of
+blind users and others who operate via the keyboard. Carbon incorporates many
+other accessibility considerations, some of which are described below.
+
+### Keyboard interaction
+
+
+
+Each accordion is a tab stop. `Space` or `Enter` keys expand or collapse
+accordions, which are collapsed by default. Interactive elements within expanded
+accordions integrate into the tab order automatically.
+
+
+
+
+
+
+
+![example of (componet_name) keyboard interaction](images/component_name-accessibility-1.png)
+
+
+ The (component_name) is reached by Tab and activated by Enter.
+
+
+
+
+
+
+
+## Design recommendations
+
+Design annotations are needed for the following instances.
+
+
+
+## Development considerations
+
+Keep these considerations in mind if you are modifying Carbon or creating a
+custom component.
+
+
+```
+
+## Documenting patterns
+
+Patterns show reusable combinations of components and templates that address
+common user objectives with sequences and flows. Because they are more
+complicated than components, you may need to adjust the topic order to best tell
+the story β but your pattern should cover all of the topics outlined in the
+following templates.
+
+### Pattern template: for one variant
+
+Use this template for documenting patterns that have a single variant. You can
+see this template in use for [Toolbar](/patterns/text-toolbar-pattern/).
+
+```markdown
+---
+title: Pattern name
+description: Explain the pattern in one or two sentences.
+---
+
+
+
+Explain the pattern in one or two sentences.
+
+
+
+
+
+Overview
+Designing with [pattern]
+Accessibility
+Related
+References
+Feedback
+
+
+
+## Overview
+
+This section answers the question: βWhat problem does this pattern solve?β
+
+- Define the use of your pattern and what it does.
+- Explain a userβs needs and how the pattern meets those needs.
+
+### Anatomy
+
+Include an image with callouts explaining each part of the pattern. See the
+[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#anatomy-of-a-form)
+for an example.
+
+### When to use
+
+Include a short list describing situations where this pattern could be applied.
+
+For example, use this pattern when:
+
+- Situation 1
+- Situation 2
+
+### When not to use (optional)
+
+If required, include a short explanation about when not to use this pattern.
+
+## Designing with [pattern]
+
+This section explains the pattern in detail. Use a combination of written
+explanations and visuals to tell the story.
+
+Describe the elements, components, and content that make up the pattern.
+
+Show the pattern in context. Use visuals throughout your written commentary to
+illustrate your guidance.
+
+Different patterns require different visuals to best explain the behaviors and
+hierarchy. Choose the options that make the most sense for the story you are
+telling.
+
+- Use annotated wireframes or sketches to explain the visual hierarchy of
+ components.
+- Create high-level user flows to explain the big picture.
+- Create a functional prototype if that is the best way to illustrate the
+ pattern's behavior.
+
+Provide a Sketch file with any symbols you've created in the development of this
+pattern.
+
+Use the following headings as guidelines for the kind of information to include.
+Depending on the requirements of your pattern, you may choose to present these
+headings as H2 headings or as H3 headings underneath a more general "Designing
+with [pattern]" heading. See the
+[Dialogs pattern](https://www.carbondesignsystem.com/patterns/dialog-pattern/#designing-with-dialogs)
+as an example.
+
+### Types of [pattern]
+
+If the pattern has different types or visual treatments that serve different use
+cases, cover them here and be sure to explain when to use each type.
+
+See the
+[Empty states](https://www.carbondesignsystem.com/patterns/empty-states-pattern#when-to-use)
+pattern and the
+[Notification](https://www.carbondesignsystem.com/patterns/notification-pattern#notification-types)
+pattern for examples.
+
+### Behaviors
+
+Describe behaviors, including guidance on interactions, and changes in states
+and content.
+
+### Best practices
+
+Are there any do's and don'ts specific to this variant? Include them here.
+
+For examples of how to lay out this kind of information, see
+[Dropdown](https://www.carbondesignsystem.com/components/dropdown/usage) and
+[Modal](https://www.carbondesignsystem.com/components/modal/usage#variations).
+
+### Visual guidance
+
+Cover any important topics such as alignment, image choice considerations, or
+special treatments in situations with no data or multiple instances of elements.
+See the
+[Empty states pattern](https://www.carbondesignsystem.com/patterns/empty-states-pattern#visual-guidelines-for-smaller-empty-spaces)
+and the
+[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#designing-a-form)
+for examples.
+
+### Other use cases
+
+If there are use cases that require a different solution, include those here
+with corresponding explanations and visuals. Be sure to explain the reasons for
+using one solution over another.
+
+## Accessibility
+
+Evaluate your pattern to ensure it meets
+[accessibility standards](notion://www.notion.so/guidelines/accessibility/overview)
+and guidelines, and provide details of compliance.
+
+For example, βUsers should be able to TAB into the input field of the search box
+to begin typing and press ENTER to run the search query.β
+
+For examples, see the
+[Text toolbar pattern](https://www.carbondesignsystem.com/patterns/text-toolbar-pattern#accessibility)
+and the
+[Search pattern](https://www.carbondesignsystem.com/patterns/search-pattern#accessibility).
+
+## Related
+
+Which components are used when building this pattern? Did you reference other
+patterns? List them here.
+
+If necessary, clarify any differences between this pattern and related patterns.
+
+## References
+
+Help designers understand your process by explaining your rationale for the way
+you implemented the pattern. Include any research, citations, books or articles
+that you found helpful.
+
+## Feedback
+
+Help us improve this pattern by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
+```
+
+### Pattern template: for multiple variants
+
+Use this template for documenting patterns that have multiple types or variants.
+You can see this template in use for [Dialog](/patterns/dialog-pattern/) and
+[Loading](/patterns/loading-pattern/).
+
+```markdown
+---
+title: Pattern name (multiple variants)
+description: Explain the pattern in one or two sentences.
+---
+
+
+
+Explain the pattern in one or two sentences.
+
+
+
+
+
+Overview
+Designing with [pattern]
+[Pattern] variant
+Accessibility
+Related
+References
+Feedback
+
+
+
+## Overview
+
+Include a paragraph or two that describes the primary use cases for the pattern
+and details about how it helps the user achieve any tasks.
+
+The purpose of this overview section is to set context for your readers.
+
+### Anatomy
+
+It can be helpful to show images of all of the variants in small form together.
+See the
+[Dialogs pattern](https://www.carbondesignsystem.com/patterns/dialog-pattern#modal-variants)
+and the
+[Notifications pattern](https://www.carbondesignsystem.com/patterns/notification-pattern#notification-types)
+for examples of this visual treatment.
+
+Alternatively, if there is one variant that includes common aspects of the
+pattern that are seen across all or most variants, include an image with
+callouts explaining each part of the pattern. See the
+[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#anatomy-of-a-form)
+for an example.
+
+### [Pattern] variants
+
+Include a table with the variants discussed in this pattern. Include a short
+description about the usage of each pattern variant. The table in
+[Modal component](https://www.carbondesignsystem.com/components/modal/usage/#variants)
+is a good example of the level of detail required.
+
+The variant names should link to the H2 headings for the variants below.
+
+Add more columns, if needed. For example, you could add a column that includes
+short explanations about when not to use the variant and guide the user to an
+alternative that may be more appropriate.
+
+## Designing with [pattern]
+
+This section covers _universal_ content related to all variants, and depending
+on the requirements of your pattern, may include the following H3s.
+
+### When to use
+
+If you need to elaborate on the content included in the pattern variants table
+in the Overview, include that detail here. The
+[Notifications pattern](https://www.carbondesignsystem.com/patterns/notification-pattern#when-to-use)
+is a good example of the kind of content to include.
+
+### When not to use (optional)
+
+If required, include a short explanation about when not to use this pattern and
+provide alternatives.
+
+### Universal behaviors
+
+Describe any behaviors that are universal to all pattern variants, and include
+guidance on interactions, and changes in states and content.
+
+### Best practices
+
+List out best practices and include any design considerations that help with
+making choices.
+
+- Do's
+- Dont's
+
+### Visual guidance
+
+Cover any important topics such as alignment, image choice considerations, or
+special treatments in situations with no data or multiple instances of elements.
+See
+[Empty states](https://www.carbondesignsystem.com/patterns/empty-states-pattern#visual-guidelines-for-smaller-empty-spaces)
+for an example.
+
+### Other considerations
+
+If there are any other considerations particular to your pattern that are
+applicable to all variants, include them here.
+
+## [Pattern] variant
+
+Rename this H2 heading with the first pattern variant name, and repeat for all
+variants within this pattern. These sections should map directly to the variant
+table in the Overview.
+
+This section describes the pattern variant in detail, and highlights content
+that is _unique_ to the pattern variant. Use a combination of written
+explanations and visuals to tell the story.
+
+The H3s headings below are suggested that be included and adapted to suit the
+requirements and complexity of the variant.
+
+Include an introductory paragraph about the pattern variant to set context.
+
+### [Pattern variant] anatomy
+
+Include an image with callouts explaining each part of the pattern variant. See
+the
+[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#anatomy-of-a-form)
+for an example.
+
+### When to use
+
+Provide use cases and situations for when this pattern should be used.
+
+### When not to use
+
+If required, also include a "When not to use" section with details about when
+not to use and suggest alternatives.
+
+### Designing with [pattern variant]
+
+Describe the elements, components, and content that make up the pattern.
+
+Show the variant in context. Use visuals throughout your written commentary to
+illustrate your guidance.
+
+Different patterns require different visuals to best explain the behaviors and
+hierarchy. Choose the options that make the most sense for the story you are
+telling.
+
+- Use annotated wireframes or sketches to explain the visual hierarchy of
+ components.
+- Create high-level user flows to explain the big picture.
+- Create a functional prototype if that is the best way to illustrate the
+ pattern's behavior.
+
+Provide a Sketch file with any symbols you've created in the development of this
+pattern.
+
+### [Pattern variant] behaviors
+
+Describe behaviors specific to the pattern variant, including guidance on
+interactions, and changes in states and content.
+
+### Best practices
+
+List out best practices and include any design considerations that help with
+making choices.
+
+- Do's
+- Dont's
+
+For examples of how to lay out this kind of information, see the
+[Dropdown component](https://www.carbondesignsystem.com/components/dropdown/usage)
+and the
+[Modal component](https://www.carbondesignsystem.com/components/modal/usage#variations).
+
+### Visual guidance
+
+Cover any important topics such as alignment, image choice considerations, or
+special treatments in situations with no data or multiple instances of elements.
+See the
+[Empty states pattern](https://www.carbondesignsystem.com/patterns/empty-states-pattern#visual-guidelines-for-smaller-empty-spaces)
+and the
+[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#designing-a-form)
+for examples.
+
+### Other use cases
+
+If there are similar use cases that may require a different solution, include
+details here and explain the reasons for using one solution over another.
+
+Repeat the H2 heading `Pattern variant` with the necessary H3 headings for each
+variant within the pattern.
+
+## Accessibility
+
+Evaluate your pattern to ensure it meets
+[accessibility standards](/guidelines/accessibility/overview) and guidelines,
+and provide details of compliance.
+
+For example, βUsers should be able to TAB into the input field of the search box
+to begin typing and press ENTER to run the search query.β
+
+## Related
+
+Which components did you use when building this pattern? Did you reference other
+patterns? List them here.
+
+If necessary, clarify any differences between this pattern and related patterns.
+
+## References
+
+Help designers understand your process by explaining your rationale for the way
+you implemented the pattern. Include any research, citations, books or articles
+that you found helpful.
+
+## Feedback
+
+Help us improve this pattern by providing feedback, asking questions, and
+leaving any other comments on
+[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
+```
+
+## Writing better content
+
+As you fill out the templates above, please keep these things in mind when
+writing content for Carbon.
- Aim for a friendly and encouraging tone.
- Speak directly to the user. You can use the second person pronoun ("you").
@@ -75,5 +1384,76 @@ Please keep these things in mind when writing content for Carbon.
- Use sentence case for everything, including component names, e.g. Content
switcher and Data table.
-To learn about writing content for component pages, see our
-[production guidelines](https://github.com/carbon-design-system/carbon-website/wiki/Production-guidelines#creating-content-for-component-pages).
+## Publishing updates
+
+Ready to get your work reviewed and published? There are two ways to do this,
+depending on your experience with GitHub. You may also draft your content and
+bring it to
+[office hours](https://ec.yourlearning.ibm.com/w3/series/10289694?layout=grid&_ga=2.129990351.257088430.1694013487-309583455.1691093939&_gl=1*16l2j5q*_ga*MzA5NTgzNDU1LjE2OTEwOTM5Mzk.*_ga_FYECCCS21D*MTY5NDAzMjgwMi4xMS4xLjE2OTQwMzQ0OTEuMC4wLjA.)
+to get further guidance.
+
+### Editing in browser
+
+#### How to edit an existing page
+
+If you are editing an existing docs page, the easiest option is to click on the
+`Edit this page on GitHub` link that appears at the bottom of every page on the
+site. The link opens the specific GitHub page where you can edit the content and
+then propose the change with a pull request. Your changes will be reviewed by
+the Carbon team. This is the easiest and most commonly used approach by
+contributors.
+
+
+
+#### How to add a new page or image
+
+To start, go to the Carbon website repository
+[here](https://github.com/carbon-design-system/carbon-website). Navigate to the
+left hand corner above the files and click `main`. From here, type in a new
+branch name that reflects your work. For
+example,`add-accordion-accessibility-guidance`. Once that new branch is created,
+navigate to where the new file will be stored for a
+[component](https://github.com/carbon-design-system/carbon-website/tree/main/src/pages/components)
+or
+[pattern](https://github.com/carbon-design-system/carbon-website/tree/main/src/pages/patterns).
+
+Ensure you are in the branch you created, then navigate to `Add file` in the
+upper right-hand corner. To add a new guidance page, click `create new file`
+button. Title the file one of the following: `usage.mdx`, `style.mdx`,
+`code.mdx`, or `accessibility.mdx`. To add an image, make sure you are in the
+image folder and click `Upload files`.
+
+After filling out the markdown template or adding an image, click
+`Commit changes`. Describe your work and double check that you are on the branch
+you created. If you are in the wrong branch, you will have to copy your content
+into the correct branch.
+
+
+
+Once you have committed your changes, go to the
+[Pull requests](https://github.com/carbon-design-system/carbon-website/pulls)
+page. Compare `base: main` to your branch and click `Create new pull request`.
+Your contribution will be reviewed by the Carbon team!
+
+### Editing in a local environment
+
+Alternatively, if you are planning regular or more comprehensive content updates
+and are up for a more advanced option, you'll want to fork the repo and install
+some of the tools we use to build the website. This will create an easier
+workflow for you long term, but takes some time to set up.
+
+If you are familiar with this process, you can
+[fork the repo](https://github.com/carbon-design-system/carbon-website/blob/main/.github/CONTRIBUTING.md#submission-guidelines)
+and get started. Otherwise, reach out to the Carbon team on slack or
+[office hours](https://ec.yourlearning.ibm.com/w3/series/10289694?layout=grid&_ga=2.129990351.257088430.1694013487-309583455.1691093939&_gl=1*16l2j5q*_ga*MzA5NTgzNDU1LjE2OTEwOTM5Mzk.*_ga_FYECCCS21D*MTY5NDAzMjgwMi4xMS4xLjE2OTQwMzQ0OTEuMC4wLjA.)
+and we'll help you find the best way to contribute.
diff --git a/src/pages/contributing/get-started.mdx b/src/pages/contributing/get-started.mdx
new file mode 100644
index 00000000000..620bea7d121
--- /dev/null
+++ b/src/pages/contributing/get-started.mdx
@@ -0,0 +1,281 @@
+---
+title: Get started
+description:
+ The Carbon Design System is made possible through a vibrant community of
+ designers and developers. Anyone can contribute code, design, documentation,
+ and ideas. Here's how you can contribute, too!
+---
+
+
+
+The Carbon Design System is made possible through a vibrant community of
+designers and developers. Anyone can contribute code, design, and documentation.
+
+
+
+
+
+Get started
+Carbon champions
+Types of contribution
+The process
+
+
+
+## Get started
+
+If you're interested in getting involved but don't know where to start, welcome!
+Designers and developers like you help to make Carbon great, and we're so glad
+you're here.
+
+To get started, subscribe to our [office hours](/whats-happening/meetups/) and
+stop on by. We'll help you find an appropriate first contribution depending on
+your skills and interests. Read on to learn about common types of contributions
+and the process.
+
+## Contribution gallery
+
+In the past year, Carbon contributors have added features to components,
+improved the React testing suite, created image production guidelines in Figma,
+and so much more! Explore the gallery below to see a small sample of finished
+projects.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Carbon champions
+
+Many thanks to our 2023 Carbon champions for making significant contributions to
+the design system.
+
+
+
+
+**Kylee Barnard** Community support
**Amaya Mali** Gantt chart
+
+
+
+
+
+**Tom Roach** Community support
**Eugene To **
+Figma
**Shankar Venkatachalam** Create React App
+**Colleen Yates** lllustration Guild
+
+
+
+
+## Types of contribution
+
+There are several ways you can contribute, depending on your interest and
+bandwidth.
+
+### Component enhancements
+
+This work involves enhancing our components in code, like adding new features or
+variants. Designers are often responsible for researching UX and visual
+solutions and then creating a design spec for developers.
+[Here are issues](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs%3A+community+contribution%22+)
+in our enhancement backlog that need design or development work.
+
+### Design kits
+
+This work is all about creating and updating reusable components in Figma.
+You'll get valuable Figma experience and will collaborate with the Figma Guild.
+Check out the
+[status of design kits](https://www.figma.com/file/CFMtqV5Nztdbm0mi2UiDLg/Library-%2B-Template-Planning?type=design&node-id=3713-26762&mode=design&t=HqvAYXUeccKNMstT-0)
+and get involved by reaching out to the contacts listed.
+
+### Website documentation
+
+All components and patterns require usage, style, code, and accessibility
+guidance on the Carbon website. You can learn how to contribute documentation
+smoothly and utilize our markdown templates on the
+[documentation](/contributing/documentation/) page. A list of components that
+still need documentation help can be found
+[here](https://github.com/carbon-design-system/carbon-website/issues/2085).
+
+### Fixing issues and bugs
+
+If you find a bug in the source code, you can help us by
+[filling out a bug report](https://github.com/carbon-design-system/carbon/issues/new/choose)
+and, ideally, submitting a pull request with a fix.
+
+### Icons and pictograms
+
+You can find instructions on how to create and contribute
+[UI icons](https://www.ibm.com/design/language/iconography/ui-icons/contribute),
+[app icons](https://www.ibm.com/design/language/iconography/app-icons/production),
+and
+[pictograms](https://www.ibm.com/design/language/iconography/pictograms/contribute)
+on the IBM Design Language site.
+
+## The process
+
+Whether you're contributing code, designs, or documentation, there's a process
+to follow. Here's what it looks like:
+
+### 1. Find a project to work on
+
+#### Volunteer for existing work
+
+The best way to volunteer is to look through
+[existing GitHub issues](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs%3A+community+contribution%22+)
+labeled with `needs: community contribution`. You can also filter by
+[code](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs%3A+community+contribution%22+label%3A%22needs%3A+code+contribution%22+)
+or
+[design](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs%3A+community+contribution%22+label%3A%22needs%3A+design+contribution%22+)
+work. Put a comment in the issue saying you'd like to help.
+
+The Carbon team is also happy to help you find a good first issue. Just stop by
+our [office hours](/whats-happening/meetups/) or send us a slack message.
+
+#### Submit an idea
+
+Have a new idea that you think would benefit Carbon? Or do you need to report a
+bug? First, be sure to look through the
+[issue backlog](https://github.com/carbon-design-system/carbon/issues) to make
+sure it is a novel idea or bug. Then, file your proposal on GitHub using the
+[issue templates](https://github.com/carbon-design-system/carbon/issues/new/choose).
+If you're willing to work on this idea yourself, be sure to let is know in your
+issue! Your idea will then go through a triage process by the Carbon team.
+
+### 2. Iterate and get feedback
+
+Most contributors work in groups of 2-3 and either set up weekly sessions or
+join [meetups](/whats-happening/meetups/#carbon-office-hours) such as the Figma
+Guild, Data Viz Guild, or office hours. In these sessions, it is common to share
+work in progress and ask lots of questions. As you make progress, update your
+GitHub issue.
+
+### 3. Review and publish
+
+#### Code deliverables
+
+Work that results in code will be reviewed directly in a pull request.
+Maintainers will be reviewing your work and making comments, asking questions
+and suggesting changes before they merge your code. When you need to make a
+change, commit and push to your branch normally. Once all revisions to your pull
+request are complete, a maintainer will squash and merge your commits for you.
+
+#### Contributor License Agreement
+
+The Carbon core team is part of IBM. To accept contributions, we need a signed
+Contributor License Agreement (CLA) from you before code contributions can be
+reviewed and merged. You will be prompted to do this in your PR, but if you have
+questions, please don't hesitate
+toΒ [reach out](/help/contact-us/#slack-channels).
+
+#### Design deliverables
+
+For work that does not have a code deliverable, such as revisions to Figma
+libraries, ask the Carbon team how to finish your contribution.
diff --git a/src/pages/contributing/images/combo-button.gif b/src/pages/contributing/images/combo-button.gif
new file mode 100644
index 00000000000..1b9b492bddc
Binary files /dev/null and b/src/pages/contributing/images/combo-button.gif differ
diff --git a/src/pages/contributing/images/icon-only-switcher.gif b/src/pages/contributing/images/icon-only-switcher.gif
new file mode 100644
index 00000000000..3314b54c20f
Binary files /dev/null and b/src/pages/contributing/images/icon-only-switcher.gif differ
diff --git a/src/pages/contributing/images/left-hand-nav-delay.gif b/src/pages/contributing/images/left-hand-nav-delay.gif
new file mode 100644
index 00000000000..17411ff9ae3
Binary files /dev/null and b/src/pages/contributing/images/left-hand-nav-delay.gif differ
diff --git a/src/pages/contributing/images/read-only-form-inputs.gif b/src/pages/contributing/images/read-only-form-inputs.gif
new file mode 100644
index 00000000000..eaec5b40a01
Binary files /dev/null and b/src/pages/contributing/images/read-only-form-inputs.gif differ
diff --git a/src/pages/contributing/images/rtl2.gif b/src/pages/contributing/images/rtl2.gif
new file mode 100644
index 00000000000..24ccf31be55
Binary files /dev/null and b/src/pages/contributing/images/rtl2.gif differ
diff --git a/src/pages/contributing/images/two-handle-slider.gif b/src/pages/contributing/images/two-handle-slider.gif
new file mode 100644
index 00000000000..d84dfec7916
Binary files /dev/null and b/src/pages/contributing/images/two-handle-slider.gif differ
diff --git a/src/pages/contributing/overview.mdx b/src/pages/contributing/overview.mdx
deleted file mode 100644
index 79852db8be7..00000000000
--- a/src/pages/contributing/overview.mdx
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Overview
-description:
- Interested in contributing to Carbon? This design system is the result of
- community contributions, large and small--of code, design, ideas, and
- guidance. Here's how you can contribute too.
----
-
-
-
-Interested in contributing to Carbon? This design system is the result of
-community contributions, large and small--of code, design, ideas, and guidance.
-Here's how you can contribute too.
-
-
-
-
-
-Introduction
-Working in the open
-The Carbon community
-Project workflow
-Contributor License Agreement
-
-
-
-## Introduction
-
-Carbon is free to use for anybody building a product or website, and the Carbon
-community is always working to make it better. Contributors like you help to
-make Carbon great, and so we're glad you're here.
-
-Contributions are not limited to code. We also encourage feedback,
-documentation, new designs, and tools.
-
-All you need is a [public GitHub account](https://github.com/join) to get
-started. Most contributions begin with a GitHub issue using one of these
-templates:
-
-- [Ask a question](https://github.com/carbon-design-system/carbon/issues/new?assignees=&labels=type%3A+question+%3Aquestion%3A&template=question.md&title=)
-- [Report a bug](https://github.com/carbon-design-system/carbon/issues/new?assignees=&labels=type%3A+bug+%F0%9F%90%9B&template=bug-report.md&title=)
-- [Request a feature](https://github.com/carbon-design-system/carbon/issues/new?assignees=&labels=type%3A+enhancement+%F0%9F%92%A1&template=feature-request-or-enhancement.md&title=)
-
-## Working in the open
-
-Carbon lives on GitHub. All work, discussion, issues, bugs, features,
-improvements, and comments happen right out in the open where everyone can see.
-As we mentioned, you'll need a [public GitHub account](https://github.com/join)
-to contribute.
-
-If you're looking for something that we don't have, or you notice something
-could be improved, you have two options:
-
-1. **Open an issue for the request.** We'll review the issue and get back to you
- with next steps. If we decide the request should be part of our pipeline,
- we'll add it to our roadmap. There are never timeline guarantees for
- requests, but we'll do our best to give you an estimate.
-
-2. **Begin the work yourself and contribute it back to Carbon.** We appreciate
- complete contributions but also works in progress. You're welcome to open an
- issue to surface your work and we'll weigh in and help where we can.
-
-Regardless of how you choose to contribute, we encourage you to open an issue as
-early as possible in the process.
-
-If working with GitHub sounds like a lot, check out
-[this free video series](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
-It's one of our favorite resources.
-
-## The Carbon community
-
-### Users
-
-Users are members of the community who use Carbon guidelines, assets, and
-tooling. Anyone can be a user, and we encourage users to participate in the
-community as much as possible.
-
-### Contributors
-
-Contributors are members of the community who contribute to Carbon in a material
-way. Anyone can be a contributor. In addition to participating as a user, you
-can also contribute by:
-
-- Reporting bugs or missing features through GitHub issues
-- Fixing bugs, adding features, and improving documentation
-
-### Maintainers
-
-Maintainers are members of the community who are committed to the success of
-individual Carbon projects. In addition to their participation as a contributor,
-maintainers:
-
-- Label, close, and manage GitHub issues
-- Close and merge GitHub pull requests
-
-## Project workflow
-
-Carbon Design System projects typically use a
-[fork and pull request workflow](https://guides.github.com/activities/forking/)
-for contributions. Specific instructions can be found in each projectβs GitHub
-`CONTRIBUTING.md` file.
-
-## Contributor License Agreement
-
-The Carbon core team works for IBM. To accept contributions, we need a signed
-Contributor License Agreement (CLA) from you before code contributions can be
-reviewed and merged. If you have questions, please don't hesitate
-toΒ [reach out](/help/contact-us).
diff --git a/src/pages/contributing/pattern.mdx b/src/pages/contributing/pattern.mdx
deleted file mode 100644
index 9b88b85b2eb..00000000000
--- a/src/pages/contributing/pattern.mdx
+++ /dev/null
@@ -1,430 +0,0 @@
----
-title: Patterns
-description:
- Patterns are best practice solutions for how a user achieves a goal. They show
- reusable combinations of components and templates that address common user
- objectives with sequences and flows.
----
-
-
-
-Patterns are best practice solutions for how a user achieves a goal. They show
-reusable combinations of components and templates that address common user
-objectives with sequences and flows.
-
-
-
-## How to write a pattern
-
-Weβve created guidelines to help you prepare a complete and comprehensive
-pattern. There are two Markdown templates to choose from:
-
-- **Pattern with a single variant**: Use this template if your pattern has one
- primary solution. This is the most common.
-- **Pattern with multiple variants**: Use this template if your content covers
- multiple variants of the pattern.
-
-You may need to adjust the topic order to best tell the story but your pattern
-should cover all of the topics outlined in each of these templates.
-
-If you would like some assistance with the best approach for your pattern,
-please [reach out](https://www.carbondesignsystem.com/help/contact-us). We'd be
-happy to work through the options with you.
-
-```markdown
----
-title: Pattern name
-description: Explain the pattern in one or two sentences.
----
-
-
-
-Explain the pattern in one or two sentences.
-
-
-
-
-
-Overview
-Designing with [pattern]
-Accessibility
-Related
-References
-Feedback
-
-
-
-## Overview
-
-This section answers the question: βWhat problem does this pattern solve?β
-
-- Define the use of your pattern and what it does.
-- Explain a userβs needs and how the pattern meets those needs.
-
-### Anatomy
-
-Include an image with callouts explaining each part of the pattern. See the
-[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#anatomy-of-a-form)
-for an example.
-
-### When to use
-
-Include a short list describing situations where this pattern could be applied.
-
-For example, use this pattern when:
-
-- Situation 1
-- Situation 2
-
-### When not to use (optional)
-
-If required, include a short explanation about when not to use this pattern.
-
-## Designing with [pattern]
-
-This section explains the pattern in detail. Use a combination of written
-explanations and visuals to tell the story.
-
-Describe the elements, components, and content that make up the pattern.
-
-Show the pattern in context. Use visuals throughout your written commentary to
-illustrate your guidance.
-
-Different patterns require different visuals to best explain the behaviors and
-hierarchy. Choose the options that make the most sense for the story you are
-telling.
-
-- Use annotated wireframes or sketches to explain the visual hierarchy of
- components.
-- Create high-level user flows to explain the big picture.
-- Create a functional prototype if that is the best way to illustrate the
- pattern's behavior.
-
-Provide a Sketch file with any symbols you've created in the development of this
-pattern.
-
-Use the following headings as guidelines for the kind of information to include.
-Depending on the requirements of your pattern, you may choose to present these
-headings as H2 headings or as H3 headings underneath a more general "Designing
-with [pattern]" heading. See the
-[Dialogs pattern](https://www.carbondesignsystem.com/patterns/dialog-pattern/#designing-with-dialogs)
-as an example.
-
-### Types of [pattern]
-
-If the pattern has different types or visual treatments that serve different use
-cases, cover them here and be sure to explain when to use each type.
-
-See the
-[Empty states](https://www.carbondesignsystem.com/patterns/empty-states-pattern#when-to-use)
-pattern and the
-[Notification](https://www.carbondesignsystem.com/patterns/notification-pattern#notification-types)
-pattern for examples.
-
-### Behaviors
-
-Describe behaviors, including guidance on interactions, and changes in states
-and content.
-
-### Best practices
-
-Are there any do's and don'ts specific to this variant? Include them here.
-
-For examples of how to lay out this kind of information, see
-[Dropdown](https://www.carbondesignsystem.com/components/dropdown/usage) and
-[Modal](https://www.carbondesignsystem.com/components/modal/usage#variations).
-
-### Visual guidance
-
-Cover any important topics such as alignment, image choice considerations, or
-special treatments in situations with no data or multiple instances of elements.
-See the
-[Empty states pattern](https://www.carbondesignsystem.com/patterns/empty-states-pattern#visual-guidelines-for-smaller-empty-spaces)
-and the
-[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#designing-a-form)
-for examples.
-
-### Other use cases
-
-If there are use cases that require a different solution, include those here
-with corresponding explanations and visuals. Be sure to explain the reasons for
-using one solution over another.
-
-## Accessibility
-
-Evaluate your pattern to ensure it meets
-[accessibility standards](notion://www.notion.so/guidelines/accessibility/overview)
-and guidelines, and provide details of compliance.
-
-For example, βUsers should be able to TAB into the input field of the search box
-to begin typing and press ENTER to run the search query.β
-
-For examples, see the
-[Text toolbar pattern](https://www.carbondesignsystem.com/patterns/text-toolbar-pattern#accessibility)
-and the
-[Search pattern](https://www.carbondesignsystem.com/patterns/search-pattern#accessibility).
-
-## Related
-
-Which components are used when building this pattern? Did you reference other
-patterns? List them here.
-
-If necessary, clarify any differences between this pattern and related patterns.
-
-## References
-
-Help designers understand your process by explaining your rationale for the way
-you implemented the pattern. Include any research, citations, books or articles
-that you found helpful.
-
-## Feedback
-
-Help us improve this pattern by providing feedback, asking questions, and
-leaving any other comments on
-[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
-```
-
-
Template for patterns with one primary solution
-
-```markdown
----
-title: Pattern name (multiple variants)
-description: Explain the pattern in one or two sentences.
----
-
-
-
-Explain the pattern in one or two sentences.
-
-
-
-
-
-Overview
-Designing with [pattern]
-[Pattern] variant
-Accessibility
-Related
-References
-Feedback
-
-
-
-## Overview
-
-Include a paragraph or two that describes the primary use cases for the pattern
-and details about how it helps the user achieve any tasks.
-
-The purpose of this overview section is to set context for your readers.
-
-### Anatomy
-
-It can be helpful to show images of all of the variants in small form together.
-See the
-[Dialogs pattern](https://www.carbondesignsystem.com/patterns/dialog-pattern#modal-variants)
-and the
-[Notifications pattern](https://www.carbondesignsystem.com/patterns/notification-pattern#notification-types)
-for examples of this visual treatment.
-
-Alternatively, if there is one variant that includes common aspects of the
-pattern that are seen across all or most variants, include an image with
-callouts explaining each part of the pattern. See the
-[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#anatomy-of-a-form)
-for an example.
-
-### [Pattern] variants
-
-Include a table with the variants discussed in this pattern. Include a short
-description about the usage of each pattern variant. The table in
-[Modal component](https://www.carbondesignsystem.com/components/modal/usage/#variants)
-is a good example of the level of detail required.
-
-The variant names should link to the H2 headings for the variants below.
-
-Add more columns, if needed. For example, you could add a column that includes
-short explanations about when not to use the variant and guide the user to an
-alternative that may be more appropriate.
-
-## Designing with [pattern]
-
-This section covers _universal_ content related to all variants, and depending
-on the requirements of your pattern, may include the following H3s.
-
-### When to use
-
-If you need to elaborate on the content included in the pattern variants table
-in the Overview, include that detail here. The
-[Notifications pattern](https://www.carbondesignsystem.com/patterns/notification-pattern#when-to-use)
-is a good example of the kind of content to include.
-
-### When not to use (optional)
-
-If required, include a short explanation about when not to use this pattern and
-provide alternatives.
-
-### Universal behaviors
-
-Describe any behaviors that are universal to all pattern variants, and include
-guidance on interactions, and changes in states and content.
-
-### Best practices
-
-List out best practices and include any design considerations that help with
-making choices.
-
-- Do's
-- Dont's
-
-### Visual guidance
-
-Cover any important topics such as alignment, image choice considerations, or
-special treatments in situations with no data or multiple instances of elements.
-See
-[Empty states](https://www.carbondesignsystem.com/patterns/empty-states-pattern#visual-guidelines-for-smaller-empty-spaces)
-for an example.
-
-### Other considerations
-
-If there are any other considerations particular to your pattern that are
-applicable to all variants, include them here.
-
-## [Pattern] variant
-
-Rename this H2 heading with the first pattern variant name, and repeat for all
-variants within this pattern. These sections should map directly to the variant
-table in the Overview.
-
-This section describes the pattern variant in detail, and highlights content
-that is _unique_ to the pattern variant. Use a combination of written
-explanations and visuals to tell the story.
-
-The H3s headings below are suggested that be included and adapted to suit the
-requirements and complexity of the variant.
-
-Include an introductory paragraph about the pattern variant to set context.
-
-### [Pattern variant] anatomy
-
-Include an image with callouts explaining each part of the pattern variant. See
-the
-[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#anatomy-of-a-form)
-for an example.
-
-### When to use
-
-Provide use cases and situations for when this pattern should be used.
-
-### When not to use
-
-If required, also include a "When not to use" section with details about when
-not to use and suggest alternatives.
-
-### Designing with [pattern variant]
-
-Describe the elements, components, and content that make up the pattern.
-
-Show the variant in context. Use visuals throughout your written commentary to
-illustrate your guidance.
-
-Different patterns require different visuals to best explain the behaviors and
-hierarchy. Choose the options that make the most sense for the story you are
-telling.
-
-- Use annotated wireframes or sketches to explain the visual hierarchy of
- components.
-- Create high-level user flows to explain the big picture.
-- Create a functional prototype if that is the best way to illustrate the
- pattern's behavior.
-
-Provide a Sketch file with any symbols you've created in the development of this
-pattern.
-
-### [Pattern variant] behaviors
-
-Describe behaviors specific to the pattern variant, including guidance on
-interactions, and changes in states and content.
-
-### Best practices
-
-List out best practices and include any design considerations that help with
-making choices.
-
-- Do's
-- Dont's
-
-For examples of how to lay out this kind of information, see the
-[Dropdown component](https://www.carbondesignsystem.com/components/dropdown/usage)
-and the
-[Modal component](https://www.carbondesignsystem.com/components/modal/usage#variations).
-
-### Visual guidance
-
-Cover any important topics such as alignment, image choice considerations, or
-special treatments in situations with no data or multiple instances of elements.
-See the
-[Empty states pattern](https://www.carbondesignsystem.com/patterns/empty-states-pattern#visual-guidelines-for-smaller-empty-spaces)
-and the
-[Forms pattern](https://www.carbondesignsystem.com/patterns/forms-pattern#designing-a-form)
-for examples.
-
-### Other use cases
-
-If there are similar use cases that may require a different solution, include
-details here and explain the reasons for using one solution over another.
-
-Repeat the H2 heading `Pattern variant` with the necessary H3 headings for each
-variant within the pattern.
-
-## Accessibility
-
-Evaluate your pattern to ensure it meets
-[accessibility standards](/guidelines/accessibility/overview) and guidelines,
-and provide details of compliance.
-
-For example, βUsers should be able to TAB into the input field of the search box
-to begin typing and press ENTER to run the search query.β
-
-## Related
-
-Which components did you use when building this pattern? Did you reference other
-patterns? List them here.
-
-If necessary, clarify any differences between this pattern and related patterns.
-
-## References
-
-Help designers understand your process by explaining your rationale for the way
-you implemented the pattern. Include any research, citations, books or articles
-that you found helpful.
-
-## Feedback
-
-Help us improve this pattern by providing feedback, asking questions, and
-leaving any other comments on
-[GitHub](https://github.com/carbon-design-system/carbon-website/issues/new?assignees=&labels=feedback&template=feedback.md).
-```
-
-
Template for patterns with multiple variants
-
-## First steps to contributing
-
-If youβve designed a pattern that is not currently in Carbon, contributing it
-back allows others in the community to refine and use your pattern in their
-projects.
-
-Start by opening a
-[Github issue](https://github.com/carbon-design-system/carbon-website/issues/new).
-Include a detailed description in which you:
-
-- Define your pattern and explain the rationale
-- Include mockups and/or prototypes of any fidelity
-- Clarify whether it uses existing components, new components, or both
-- Include competitive and comparative analysis, and any inspirations from other
- products
-
-This issue will be the staging ground for the pattern contribution, and you
-should expect the Carbon core team and the community to weigh in with
-suggestions.
-
-We encourage you to surface work in progress. If youβre not able to complete all
-of the parts yourself, someone in the community may be able to help.
diff --git a/src/pages/designing/design-resources/index.mdx b/src/pages/designing/design-resources/index.mdx
index eb7a3e7998d..a45d6f72710 100755
--- a/src/pages/designing/design-resources/index.mdx
+++ b/src/pages/designing/design-resources/index.mdx
@@ -103,16 +103,15 @@ reflect IBM's spirit, beliefs, and design principles.
## Data visualization
-The Data visualization kit includes basic and complex chart assets, along with
+The Carbon Charts library includes basic and complex chart assets, along with
usage guidance, theming guidance, palettes, and sample layouts.
@@ -239,7 +238,7 @@ assets to make sure your designs are accessible for implementation.
## Prototyping tools
-### Carbon Mid-Fi kit
+### Carbon Mid-Fidelity kit
This kit provides designers with a way to visualize concepts and test them out
before committing to high-fidelity designs.
@@ -248,13 +247,13 @@ before committing to high-fidelity designs.
+
### Invision Freehand kit
diff --git a/src/pages/designing/get-started.mdx b/src/pages/designing/get-started.mdx
index ae5f4e0f205..6b73c5d8c8f 100644
--- a/src/pages/designing/get-started.mdx
+++ b/src/pages/designing/get-started.mdx
@@ -78,17 +78,17 @@ starting point for building user interfaces. This brings consistency and speed,
allowing teams to focus on solving more specific user tasks. Core design kits
include elements, core components, wireframes, and guidelines.
-| Maintainer | Design kit | Type |
-| ------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------ |
-| IBM Brand | [IBM Pictograms](https://www.figma.com/community/file/1089047716352012639/Pictograms---IBM-Design-Language) | `Elements` |
-| | [IBM Icons](https://www.figma.com/community/file/1089055340263947620/Icons---IBM-Design-Language) | `Elements` |
-| | [v11 Text styles]() | `Elements` |
-| | [IBM Color palette](https://www.figma.com/community/file/1089055766693968230/Color-Styles---IBM-Design-Language) | `Elements` |
-| Carbon Core | [v11 White theme]() | `UI` |
-| | [v11 Gray 10 theme]() | `UI` |
-| | [v11 Gray 90 theme]() | `UI` |
-| | [v11 Gray 100 theme]() | `UI` |
-| Accessibility | [Accessibility toolkit](https://www.figma.com/community/file/1118184491812988116/IBM-Accessibility-Design-Kit) | `Guidelines` |
+| Maintainer | Design kit | Type |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ------------ |
+| IBM Brand | [IBM Pictograms](https://www.figma.com/community/file/1089047716352012639/Pictograms---IBM-Design-Language) | `Elements` |
+| | [IBM Icons](https://www.figma.com/community/file/1089055340263947620/Icons---IBM-Design-Language) | `Elements` |
+| | [v11 Text styles]() | `Elements` |
+| | [IBM Color palette](https://www.figma.com/community/file/1089055766693968230/Color-Styles---IBM-Design-Language) | `Elements` |
+| Carbon Core | [v11 All themes]() | `UI` |
+| | [v11 Gray 10 theme [Deprecated]]() | `UI` |
+| | [v11 Gray 90 theme [Deprecated]]() | `UI` |
+| | [v11 Gray 100 theme [Deprecated]]() | `UI` |
+| Accessibility | [Accessibility toolkit](https://www.figma.com/community/file/1118184491812988116/IBM-Accessibility-Design-Kit) | `Guidelines` |
The links in the table for Figma Libraries are preview only. Some of the Figma
kits are for internal IBMers. To learn more about installing Figma Libraries and
@@ -99,10 +99,7 @@ available external libraries visit the Figma tutorial
Support for v11 Figma kits are prioritized, but
[Figma v10 kits](https://next.carbondesignsystem.com/design-kits?q=v10&tool[]=figma)
-are also available with limited support. Visit the
-[design kit catalog](https://next.carbondesignsystem.com/design-kits) to see a
-comprehensive list of all design kits, including v10 Figma kits and kits for
-tools that are no longer maintained. In
+are also available with limited support. In
[Other resources](/designing/design-resources/), you'll find links to icon
libraries, color palettes, plugins, and more. The Adobe XD kit is no longer
prioritized or maintained, but you may access it
diff --git a/src/pages/designing/kits/figma.mdx b/src/pages/designing/kits/figma.mdx
index f461595bbd3..98486e8df0b 100644
--- a/src/pages/designing/kits/figma.mdx
+++ b/src/pages/designing/kits/figma.mdx
@@ -15,10 +15,9 @@ contains all resources you need to get started.
-**v11 themes are now available!** All themes for the v11 libraries are available
-to IBM's internal users and the public community. We have leveraged Figmas
-latest features in this release which may result in breaking changes to some of
-our components.
+**All themes are now available in one Figma library!** We have implemented Figma
+modes and theming variables, allowing us to combine all four themes into one
+library file.
@@ -41,14 +40,11 @@ You should be added to the IBM Figma organization automatically once you sign
in. You do not need to join or request to join any specific team to access the
libraries.
-#### 2. Turn on the v11 theme libraries
+#### 2. Turn on the Carbon themes library
-There are four Carbon v11 theme libraries, two light (White and Gray 10) and two
-dark (Gray 90 and Gray 100). Each theme lives in its own Figma library. You can
-turn on as many libraries as youβd like. The v11 theme libraries are now
-available to IBMβs internal users and the public community. We have leveraged
-Figmas latest features in this release which may result in breaking changes to
-some of our components.
+The `(v11) All themes - Carbon Design System` library (previously referred to as
+(v11) White theme - Carbon Design System) includes all four Carbon themes,
+including two light (White and Gray 10) and two dark (Gray 90 and Gray 100).
Inside of a design file, navigate to the **Main menu** panel in the top left of
the toolbar (A). Open the menu and select **Libraries** from the list (B).
@@ -62,8 +58,8 @@ the toolbar (A). Open the menu and select **Libraries** from the list (B).
Then in the Libraries modal that appears, find the team called
-`IBM Design Systems` (C) and switch the toggle beside a themed library, for
-example the `(v11) White Theme - Carbon Design System` to on (D).
+`IBM Design Systems` (C) and switch the toggle beside the
+`(v11) All Themes - Carbon Design System` library to on (D).
@@ -75,51 +71,18 @@ example the `(v11) White Theme - Carbon Design System` to on (D).
-To preview the four v11 Carbon theme libraries, visit the following view-only
-links. To access the v10 Figma libraries, see
+To preview the All themes library, visit the following view-only link. To access
+the v10 Figma theme libraries, see
[v10 Design Kits](https://v10.carbondesignsystem.com/designing/kits/figma).
fathom.trackGoal('P0OEN9TS', 0)}
- subTitle="v11 White theme"
+ subTitle="v11 All themes"
href="https://www.figma.com/file/YAnB1jKx0yCUL29j6uSLpg/(v11)-White-Theme---Carbon-Design-System"
actionIcon="launch">
-![Figma icon](/images/figma.svg)
-
-
-
-
- fathom.trackGoal('T7D1HJ3L', 0)}
- subTitle="v11 Gray 10 theme"
- href="https://www.figma.com/file/0sd447WTcazDI6Dq9tjXOe/(v11)-Gray-10-Theme---Carbon-Design-System"
- actionIcon="launch">
-
-![Figma icon](/images/figma.svg)
-
-
-
-
- fathom.trackGoal('LYFJTPDE', 0)}
- subTitle="v11 Gray 90 theme"
- href="https://www.figma.com/file/fH8rkv1VUTw5pvFDvO1kPO/(v11)-Gray-90-Theme---Carbon-Design-System"
- actionIcon="launch">
-
-![Figma icon](/images/figma.svg)
-
-
-
-
- fathom.trackGoal('3XH0SIBJ', 0)}
- subTitle="v11 Gray 100 theme"
- href="https://www.figma.com/file/XhRIHF6qGiJQaJ5eOSSBRm/(v11)-Gray-100-Theme---Carbon-Design-System"
- actionIcon="launch">
-
![Figma icon](/images/figma.svg)
@@ -205,14 +168,11 @@ Design Language libraries or visit these view-only links.
#### 2. Get the theme libraries
-There are four Carbon v11 theme libraries, two light (White and Gray 10) and two
-dark (Gray 90 and Gray 100). Each theme lives in its own Figma library. You can
-turn on as many libraries as youβd like. The v11 theme libraries are now
-available to IBMβs internal users and the public community. We have leveraged
-Figmas latest features in this release which may result in breaking changes to
-some of our components.
+The `(v11) All themes - Carbon Design System` library (previously referred to as
+(v11) White theme - Carbon Design System) includes all four Carbon themes,
+including two light (White and Gray 10) and two dark (Gray 90 and Gray 100).
-Navigate to the **Community** tab in the left side panel (A).
+Navigate to the **Community** icon in the header (A).
@@ -222,8 +182,8 @@ Navigate to the **Community** tab in the left side panel (A).
-Select the **Design Systems** category (B) and search for **Carbon Design
-System** (C).
+Select the **Design Systems** category and search for **Carbon Design System**
+(B).
@@ -233,7 +193,7 @@ System** (C).
-See the Carbon Design System libraries that are available.
+See the `(v11) All themes - Carbon Design System` library file.
@@ -247,56 +207,24 @@ See the Carbon Design System libraries that are available.
#### 4. Publish as a library to your workspace
-To preview the four Carbon v11 theme libraries, visit these view-only links.
+To preview the `(v11) All themes - Carbon Design System` library, visit the
+following view-only link.
fathom.trackGoal('P0OEN9TS', 0)}
- subTitle="v11 White theme"
+ subTitle="v11 All themes"
href="https://www.figma.com/community/file/1157761560874207208"
actionIcon="launch">
-![Figma icon](/images/figma.svg)
-
-
-
-
- fathom.trackGoal('T7D1HJ3L', 0)}
- subTitle="v11 Gray 10 theme"
- href="https://www.figma.com/community/file/1157763433354586090"
- actionIcon="launch">
-
-![Figma icon](/images/figma.svg)
-
-
-
-
- fathom.trackGoal('LYFJTPDE', 0)}
- subTitle="v11 Gray 90 theme"
- href="https://www.figma.com/community/file/1157763622355802091"
- actionIcon="launch">
-
-![Figma icon](/images/figma.svg)
-
-
-
-
- fathom.trackGoal('3XH0SIBJ', 0)}
- subTitle="v11 Gray 100 theme"
- href="https://www.figma.com/community/file/1157763881353486317"
- actionIcon="launch">
-
![Figma icon](/images/figma.svg)
-#### 3. Bring in additional colors and icons
+#### 5. Bring in additional colors and icons
Use these additional IBM Design Language libraries to have access to color
styles, hover color styles, text styles, icons, and pictograms.
@@ -395,7 +323,7 @@ To learn more about applying color styles in Figma, see the
### Text styles
To apply a text style, select a text layer, then in the properties panel, choose
-a text style from the '(v11) Text styles - IBM Design Language' library
+a text style from the `(v11) Text styles - IBM Design Language` library
depending on which version you are on. Use color styles to change the color of a
text style.
diff --git a/src/pages/designing/kits/images/axure-icon.png b/src/pages/designing/kits/images/axure-icon.png
deleted file mode 100644
index b41d7ce2a77..00000000000
Binary files a/src/pages/designing/kits/images/axure-icon.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/axure-updates.png b/src/pages/designing/kits/images/axure-updates.png
deleted file mode 100644
index 21a9f445fc8..00000000000
Binary files a/src/pages/designing/kits/images/axure-updates.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/kit-adobexd-1.png b/src/pages/designing/kits/images/kit-adobexd-1.png
deleted file mode 100644
index cfbe6ec3900..00000000000
Binary files a/src/pages/designing/kits/images/kit-adobexd-1.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/kit-adobexd-2.png b/src/pages/designing/kits/images/kit-adobexd-2.png
deleted file mode 100644
index a7afdac94bf..00000000000
Binary files a/src/pages/designing/kits/images/kit-adobexd-2.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/kit-adobexd-3.png b/src/pages/designing/kits/images/kit-adobexd-3.png
deleted file mode 100644
index 660069aff51..00000000000
Binary files a/src/pages/designing/kits/images/kit-adobexd-3.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/kit-adobexd-4.png b/src/pages/designing/kits/images/kit-adobexd-4.png
deleted file mode 100644
index 4f6716c2ab7..00000000000
Binary files a/src/pages/designing/kits/images/kit-adobexd-4.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/kit-adobexd-5.png b/src/pages/designing/kits/images/kit-adobexd-5.png
deleted file mode 100644
index 6ece8c87e6c..00000000000
Binary files a/src/pages/designing/kits/images/kit-adobexd-5.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/kit-adobexd-6.png b/src/pages/designing/kits/images/kit-adobexd-6.png
deleted file mode 100644
index 0c4cb6a0471..00000000000
Binary files a/src/pages/designing/kits/images/kit-adobexd-6.png and /dev/null differ
diff --git a/src/pages/designing/kits/images/kit-figma-1.png b/src/pages/designing/kits/images/kit-figma-1.png
index 44e349a41c0..f57f0a19c3d 100644
Binary files a/src/pages/designing/kits/images/kit-figma-1.png and b/src/pages/designing/kits/images/kit-figma-1.png differ
diff --git a/src/pages/designing/kits/images/kit-figma-2.png b/src/pages/designing/kits/images/kit-figma-2.png
index 7760ef04f94..e30b191d08c 100644
Binary files a/src/pages/designing/kits/images/kit-figma-2.png and b/src/pages/designing/kits/images/kit-figma-2.png differ
diff --git a/src/pages/designing/kits/images/kit-figma-3.png b/src/pages/designing/kits/images/kit-figma-3.png
index 1a8836623f8..fbcaf5457e6 100644
Binary files a/src/pages/designing/kits/images/kit-figma-3.png and b/src/pages/designing/kits/images/kit-figma-3.png differ
diff --git a/src/pages/designing/kits/images/kit-figma-4.png b/src/pages/designing/kits/images/kit-figma-4.png
index f89bf4481e9..b8363b3af46 100644
Binary files a/src/pages/designing/kits/images/kit-figma-4.png and b/src/pages/designing/kits/images/kit-figma-4.png differ
diff --git a/src/pages/designing/kits/images/kit-figma-5.png b/src/pages/designing/kits/images/kit-figma-5.png
index 92378c6ee1c..6506cf59424 100644
Binary files a/src/pages/designing/kits/images/kit-figma-5.png and b/src/pages/designing/kits/images/kit-figma-5.png differ
diff --git a/src/pages/developing/frameworks/vue.mdx b/src/pages/developing/frameworks/vue.mdx
index 43ddaa82c1e..f6e0180349f 100644
--- a/src/pages/developing/frameworks/vue.mdx
+++ b/src/pages/developing/frameworks/vue.mdx
@@ -62,36 +62,45 @@ contact the
Assuming we're starting with a new Vue CLI project:
```bash
-vue create --default my-project
-cd my-project
+npm create vue@latest
+cd vue-project
```
-Using Yarn
-
-```bash
-yarn add @carbon/vue
-```
-
-Or npm
-
```bash
npm install @carbon/vue
```
-In src/main.js, after "import Vue from 'vue'", add the following to include the
-carbon styles and components.
+In src/main.js, after `import App from './App.vue'`, add the following to
+include the carbon styles and components.
```js
import 'carbon-components/css/carbon-components.css';
import CarbonComponentsVue from '@carbon/vue';
-Vue.use(CarbonComponentsVue);
+
+const app = createApp(App);
+app.use(CarbonComponentsVue);
+app.mount('#app');
+// remove the line: createApp(App).mount('#app')
```
Replace the contents of src/components/HelloWorld.vue with the following
```html
+
+
-
+
Example use of @carbon/vue
Hello {{yourName}}
- Welcome to @carbon/vue {{yourName}}
-
+ Welcome to @carbon/vue {{yourName}}
+
Lorem ipsum dolor sit amet, consectetur adipisicing elit, seed do
eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
@@ -113,27 +122,7 @@ Replace the contents of src/components/HelloWorld.vue with the following
-
-
-
@@ -151,21 +139,15 @@ Replace the contents of src/components/HelloWorld.vue with the following
That's it! Now start the server and start building.
-Using Yarn
-
-```bash
-yarn serve
-```
-
-Or npm
-
```bash
-npm run serve
+npm run dev
```
_Note: This isn't the only way to bootstrap a_ `carbon-components-vue`
_application, but the combination of_ `Vue CLI` _and the_ `carbon-components`
-_scss is our recommended setup._
+_scss is our recommended setup._ See
+[Hello carbon vue3](https://github.com/IBM/hello-carbon-vue3) for a complete
+example app.
### List of available components
diff --git a/src/pages/developing/frameworks/web-components.mdx b/src/pages/developing/frameworks/web-components.mdx
index 8b8039f2265..48cfd2a6b9a 100644
--- a/src/pages/developing/frameworks/web-components.mdx
+++ b/src/pages/developing/frameworks/web-components.mdx
@@ -33,7 +33,8 @@ This library uses Custom Elements v1 and Shadow DOM v1 specs.
For support, contact the
[Carbon Web Components team](https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/new/choose).
-v11 upgrade for Carbon Web Components is coming soon.
+Info on Carbon Web Components v1 can be found
+[here](https://v10.carbondesignsystem.com/developing/frameworks/web-components).
@@ -53,7 +54,7 @@ v11 upgrade for Carbon Web Components is coming soon.
@@ -75,13 +76,13 @@ version `v1.16.0`):
```
@@ -94,6 +95,7 @@ These are the list of available components via CDN:
- code-snippet.min.js
- combo-box.min.js
- content-switcher.min.js
+- copy.min.js
- copy-button.min.js
- data-table.min.js
- date-picker.min.js
@@ -102,7 +104,7 @@ These are the list of available components via CDN:
- floating-menu.min.js
- form.min.js
- inline-loading.min.js
-- input.min.js
+- layer.min.js
- link.min.js
- list.min.js
- loading.min.js
@@ -123,9 +125,11 @@ These are the list of available components via CDN:
- structured-list.min.js
- tabs.min.js
- tag.min.js
+- text-input.min.js
- textarea.min.js
- tile.min.js
- toggle.min.js
+- toggle-tip.min.js
- tooltip.min.js
- ui-shell.min.js
@@ -136,13 +140,13 @@ extention from `.min.js` to `.rtl.min.js`. For example:
```
@@ -157,25 +161,23 @@ directly used once the script tag has been added to the page. For example: