de91ead0db
* lots of release process doc tweaks:
- add outcomes for all H4s (we may be able to remove some similar material from "body" content)
- mention that svn is needed
- clarify relationship to PR and PR checklist in a few places
- we have 2 docs to follow now, which could be confusing
- clarify release metadata step - this is metadata, not version number
- clarify relationship to woo core
- add dev blog post as final happy 🎉 step
* fix typo
Co-authored-by: Darren Ethier <darren@roughsmootheng.in>
Co-authored-by: Darren Ethier <darren@roughsmootheng.in>
|
||
|---|---|---|
| .. | ||
| block-client-apis | ||
| blocks | ||
| contributors | ||
| extensibility | ||
| releases | ||
| 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. |
| Releases | These documents cover how to release and test new versions of the blocks plugin. |
| 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. |