Merge pull request #152 from infinum/develop

Main deploy kickstart

website/blog/2022-03-03-adding-blocks-wpcli.md

@@ -44,7 +44,9 @@ wp boilerplate use_block --name=example
 Since our blocks use a predefined structure to make everything register automatically, adding Example block with WP-CLI will generate all required files. After it's added, feel free to rename the folder, as well as files with the name of your block and start modifying all the files. Simply replace "example" with the name of your block.
 
 ### Further reading
+
 Our documentation has all this covered in a lot more detail, so if you would like to better understand the structure of our blocks and components, here are some chapters covering these topics:
-- [Structure](/docs/basics/the-structure)
+
+- [Architecture concepts](/docs/basics/architecture-concepts)
 - [Block Structure](/docs/basics/block-structure)
 - [Component Structure](/docs/basics/blocks-component-structure)

website/docs/basics/architecture-concepts.md

@@ -5,7 +5,6 @@ title: Architecture concepts
 
 ## Project structure
 
-
 [![docs-source](https://img.shields.io/badge/source-eightshift--libs-blue?style=for-the-badge&logo=php&labelColor=2a2a2a)](https://github.com/infinum/eightshift-libs)
 
 Eightshift Development Kit follows a strict project structure to support autoloading, dependency injection and `wp boilerplate` commands, as well as conventions to increase codebase understanding between developers. As an added benefit, following this structure and conventions makes your codebase more consistent and organized.

website/src/theme/sections/showcase-grid/showcase-grid.js

@@ -1,4 +1,4 @@
-import React from 'react';
+import React, { useEffect, useState } from 'react';
 import useBaseUrl from '@docusaurus/useBaseUrl';
 import Heading from '../../components/heading/heading';
 import Container from '../../components/container/container';