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 |
||
---|---|---|
.. | ||
README.md | ||
block-assets.md | ||
coding-guidelines.md | ||
components.md | ||
css-build-system.md | ||
getting-started.md | ||
javascript-testing.md | ||
js-build-system.md | ||
smoke-testing.md |
README.md
Contributing
This folder contains documentation for developers and contributors looking to get started with WooCommerce Block Development.
Document | Description |
---|---|
Getting Started | This doc covers tooling and creating builds during development. |
Coding Guidelines | This doc covers development best practices. |
Smoke Testing | This doc explains how to smoke test key Blocks functionality. |
JavaScript Testing | This doc explains how to run automated JavaScript tests. |
Developing Components (& Storybook) | This doc outlines where our reusable components live, and how to test them in Storybook. |
Block Script Assets | This doc explains how Block Script Assets are loaded and used. |
JS build system | This doc explains how JavaScript files are built. |
CSS build system | This doc explains how CSS is built. |