5168a21920
* Add “Address line 2” toggle
* Allow apartment field to be required
* Add changefile(s) from automation for the following project(s): woocommerce-blocks
* Rename “Apartment, suite, etc.” to “Address line 2”
* Remove unused dependency
* Add key to fragment
* Simplify keys
* Address failing e2e tests
* Change “Optional (Recommended)” to “Optional”
* Toggle address line 2 visibility in editor
* Add e2e tests
* Add changefile(s) from automation for the following project(s): woocommerce-blocks, woocommerce
* Update e2e tests
* Update e2e tests
* Ensure the address 2 field stays open when the seller empties it
* Optimise hasAddress2FieldValue
* Move address 2 filed related functionality into separate component
* Rmove + sign from address 2 field links
* WIP: Introduce AddressField component
* Update AddressFields component
* Refactor AddressFields and Address2Field components
* Fix CSS lint error
* Fix JS lint error
* Fix failing e2e tests
* Fix typo in e2e tests
* Improve e2e selector
* Fix core e2e tests
* Use address line 2 label for the link text
* Lazy initialise the “isFieldVisible” state
* Remove obsolete code
* Add inline comments for clarity
* Fix JS lint error
* Improve e2e tests
* Revert "Remove obsolete code"
This reverts commit
|
||
|---|---|---|
| .. | ||
| block-references | ||
| contributors | ||
| designers/theming | ||
| examples | ||
| internal-developers | ||
| third-party-developers/extensibility | ||
| README.md | ||
README.md
WooCommerce Blocks Handbook
Table of Contents
- Contributors
- Internal developers
- Third-party developers
- Designers
- Block References
- Developer Resources
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.
Contributors
Want to contribute to the WooCommerce Blocks plugin? The following documents offer information that can help you get started.
Internal developers
Are you an internal developer? The following documents offer information about the different blocks, the Block Client APIs, the Store API, the templates and the testing process.
- Blocks
- Block Data
- Block Client APIs
- Data store
- Editor Components
- Icons
- Store API (REST API)
- Storybook
- Templates
- Testing
- Translations
Third-party developers
Are you a third-party developer? The following documents explain how to extend the WooCommerce Blocks plugin with your custom extension.
- Extensibility
- Hooks
- REST API
- Checkout Payment Methods
- Checkout Blocks
Designers
Are you a designer? The following documents explain how to apply design-changes to the WooCommerce Blocks plugin.
Block References
Developer Resources
Tools
- @woocommerce/extend-cart-checkout-block This is a template to be used with @wordpress/create-block to create a WooCommerce Blocks extension starting point. It also showcases how to use some extensibility points, e.g. registering an inner block in the Checkout Block, applying filters to certain texts such as the place order button, using Slot/Fill and how to change the behaviour of the Store API.
Articles
The following posts from developer.woo.com provide deeper insights into the WooCommerce Blocks development.
- Store API is now considered stable
- Available Extensibility Interfaces for The Cart and Checkout Blocks
- How The Checkout Block Processes An Order
- New @wordpress/data stores in WooCommerce Blocks
Tutorials
The following tutorials from developer.woo.com help you with extending the WooCommerce Blocks plugin.
- 📺 Tutorial: Extending the WooCommerce Checkout Block
- Hiding Shipping and Payment Options in the Cart and Checkout Blocks
- Integrating your Payment Method with Cart and Checkout Blocks
- Exposing Payment Options in the Checkout Block
We're hiring! Come work with us!
🐞 Found a mistake, or have a suggestion? Leave feedback about this document here.