13311e7bee
The internal ID has been kept after a comment by @tjcafferkey. This causes a bit of inconsistency in the internal code, but it was deemed that it would have been better as users who have customized templates using this blocks ID will have saved this in their database, and it would result in a corrupt block when loaded, and we didn't want to support both IDs at the moment. Otherwise, most other references to the legacy template, are now using the word “classic”. Co-authored-by: Alba Rincón <alba@albasauatticmbp.home> |
||
---|---|---|
.. | ||
block-client-apis | ||
blocks | ||
contributors | ||
examples | ||
extensibility | ||
templates | ||
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. |
Templates | These documents provide a technical overview of WooCommerce block template (parts) functionality. |
We're hiring! Come work with us!
🐞 Found a mistake, or have a suggestion? Leave feedback about this document here.