77aa2a33a3
* add high-level docs about our components & remove stale detail info * use current collection/folder naming in docs: - let's rename js/components in a separate PR - split paragraphs on to separate lines to improve future diffs * rename storybook.md => components.md and update link/summary * tweak component collection docs: - base have more stringent requirements, since they can be used anywhere - editor components are less strict and can assume editor context * clarify js/base/components readme in line with main doc * remove line about editor components being specialised to woo blocks |
||
---|---|---|
.. | ||
block-title | ||
edit-product-link | ||
error-placeholder | ||
feedback-prompt | ||
grid-content-control | ||
grid-layout-control | ||
heading-toolbar | ||
page-selector | ||
product-attribute-term-control | ||
product-category-control | ||
product-control | ||
product-orderby-control | ||
product-tag-control | ||
products-control | ||
text-toolbar-button | ||
toggle-button-control | ||
utils | ||
view-switcher | ||
README.md |
README.md
WooCommerce Blocks - Editor Components
These are shared components used in WooCommerce blocks for the editor (Gutenberg) UI.
Many of our blocks need rich, smart components to provide an interface for selecting or configuring blocks with WooCommerce data. Often there are multiple blocks that need such components. Components in this collection are used in multiple blocks, and may include logic for working with Woo data specifically (e.g. products, shipping methods, product categories).
See Components & Storybook doc for more information.