a436c7bfe6
* Empty commit for release pull request * Add changelog to readme. * Update metadata for release * Testing notes for release * Apply suggestions from code review Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> * Apply suggestions from code review * Bumping version strings to new version. Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: Darren Ethier <darren@roughsmootheng.in> Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| block-client-apis | ||
| blocks | ||
| contributors | ||
| extensibility | ||
| testing | ||
| theming | ||
| readme.md | ||
readme.md
WooCommerce Blocks Handbook
The WooCommerce Blocks Handbook provides documentation for designers and developers on how to extend or contribute to blocks, and how internal developers should handle new releases.
| Document | Description |
|---|---|
| Contributing | These documents explain how you can contribute to the development of the blocks plugin, development best practices, and how to help with testing. |
| Blocks | This documentation covers functionality specific to certain Blocks. |
| Block Client APIs | This documentation covers API interfaces within Blocks. In most cases, these docs describe APIs and interfaces that are internal only, and thus are provided to assist with developing the blocks in this repository. Documentation will tend to focus on high level overviews. |
| Store API (REST API) | These documents cover the Store API used to get product data on the frontend. |
| Extensibility | These documents cover extensibility of WooCommerce Blocks. |
| Theming | These documents cover theming for blocks, styles, CSS classnames and other theming best practices. |