fbd86f8762
* Block scaffolding * Rename to store notices * Register only in the site editor * Update description * Add woocommerce class * Add tests * Delete old test file * Update notices message in the editor * Remove customization * Disable the block server side * Fix TS error * Add custom classes * Reprashed test description * Escape notices * Remove unnecessary disabled component * Only allow to insert the block once * Improve class name * Merge edit and block files * Fix copy * Simplify test case * Remove align support * Remove attributes * Change editor markup * Use the Notice component to display the notice placeholder on the editor * Use sprintf to improve readability * Inline component * Remove styles and unregister scripts * Use ordered placeholders Co-authored-by: Tung Du <dinhtungdu@gmail.com> * Use info as the notices status Co-authored-by: Tung Du <dinhtungdu@gmail.com> * Fix php lint error Co-authored-by: Tung Du <dinhtungdu@gmail.com> |
||
---|---|---|
.. | ||
active-filters | ||
attribute-filter | ||
cart | ||
cart-checkout-shared | ||
catalog-sorting | ||
checkout | ||
classic-template | ||
customer-account | ||
featured-items | ||
filter-wrapper | ||
handpicked-products | ||
mini-cart | ||
price-filter | ||
product-best-sellers | ||
product-categories | ||
product-category | ||
product-new | ||
product-on-sale | ||
product-query | ||
product-results-count | ||
product-search | ||
product-tag | ||
product-top-rated | ||
products | ||
products-by-attribute | ||
rating-filter | ||
reviews | ||
shared/styles | ||
single-product | ||
stock-filter | ||
store-notices | ||
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.