d53551d4a7
* Add hover & focus styles for component buttons We are using an old version of the "@wordpress/component" package, that's why we are not getting the latest style fixes from Gutenberg. The reason to not using the latest version is that we had some issues with the bundle size. The current solution is to set our own focus & hover styles * Replace raw value with Sass variable * Fix hover style for the mini cart block We don't have the outlined button yet. This styles is unique for the mini cart button. To refactor this code, maybe we should create a reusable outlined button * Add variant to the Woo Block Button component To refactor our code, adding a "variant" prop looks logical since we are have already "contained" & "outlined" buttons. So, for future need for an outlined button, no need to manually apply the same style again. The "contained" variant is set by default for legacy reasons. Our Button component was first built as a contained one. * Fix height difference: oulined & contained buttons The outlined buttons have more height because of the added border value. To fix it we can replace the border with the inner shadow. Co-authored-by: Saad Tarhi <saad.tarhi@automattic.com> |
||
|---|---|---|
| .. | ||
| active-filters | ||
| attribute-filter | ||
| cart-checkout | ||
| checkout | ||
| featured-category | ||
| featured-product | ||
| handpicked-products | ||
| legacy-template | ||
| price-filter | ||
| product-best-sellers | ||
| product-categories | ||
| product-category | ||
| product-new | ||
| product-on-sale | ||
| product-search | ||
| product-tag | ||
| product-top-rated | ||
| products | ||
| products-by-attribute | ||
| reviews | ||
| single-product | ||
| stock-filter | ||
| README.md | ||
README.md
Blocks
Our blocks are generally made up of up to 4 files:
|- block.js
|- editor.scss
|- index.js
|- style.scss
The only required file is index.js, this sets up the block using registerBlockType. Each block has edit and save functions.
The scss files are split so that things in style are added to the editor and frontend, while styles in editor are only added to the editor. Most of our blocks should use core components that won't need CSS though.
Editing
A simple edit function can live in index.js, but most blocks are a little more complicated, so the edit function instead returns a Block component, which lives in block.js. By using a component, we can use React lifecycle methods to fetch data or save state.
The Newest Products block is a good example to read over, this is a simple block that fetches the products and renders them using the ProductPreview component.
We include settings in the sidebar, called the Inspector in gutenberg. See an example of this.
Other blocks have the concept of an "edit state", like when you need to pick a product in the Featured Product block, or pick a category in the Products by Category block.