From db2a1ca8dc0a352c1d9164d92199c0a4e21f41f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivan=20Ruz=CC=8Cevic=CC=81?= Date: Fri, 26 Jan 2024 08:16:14 +0100 Subject: [PATCH] fixing note issue --- .../2023-09-05-wrapper-as-a-standalone-component.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/website/blog/2023-09-05-wrapper-as-a-standalone-component.md b/website/blog/2023-09-05-wrapper-as-a-standalone-component.md index 5c209c426..c2814fafb 100644 --- a/website/blog/2023-09-05-wrapper-as-a-standalone-component.md +++ b/website/blog/2023-09-05-wrapper-as-a-standalone-component.md @@ -12,7 +12,7 @@ hide_table_of_contents: false As one of the most powerful features in the Eightshift DevKit, the Wrapper is a part of every Eightshift block in the Gutenberg editor, but what about WordPress templates? -:::Note +:::note [Wrapper](https://eightshift.com/docs/basics/blocks-wrapper/) is designed to be the ultimate top-level component that controls how your block behaves in the website layout. It is a sort of a 'section' in traditional builders. By default, you can control a whole lot of stuff, but there is an option to add custom attributes and tailor the Wrapper to the needs of your project. ::: @@ -20,7 +20,7 @@ As one of the most powerful features in the Eightshift DevKit, the Wrapper is a Before the days of [Full Site Editing](https://developer.wordpress.org/block-editor/getting-started/full-site-editing/) in WordPress, we used [template files](https://developer.wordpress.org/themes/basics/template-hierarchy/) to add custom layouts to a blog page or post archives. -:::Note +:::note While Full-site editing (FSE) _is_ supported in Eightshift Libs, a couple of modifications have to be done in your project to make it work. ::: @@ -30,7 +30,7 @@ Depending on your setup, you might still use those as they are still a core part Thanks to the `Components` helper, we can easily `render()` any component in our template. -:::Note +:::note Interested in how to use components in a block? Take a look at [our docs](https://eightshift.com/docs/basics/blocks-component-in-block#i-have-a-component-that-i-want-to-use-manually). ::: @@ -72,7 +72,7 @@ use InfinumLibsVendor\EightshiftLibs\Helpers\Components; If we look deeper into the `render` method, we'll see that for the `$component` parameter, we can pass the _component's name or the full path (ending with .php)_. We made it simple, so use `wrapper`. -:::Note +:::note If you are upgrading from an older version (supported since [Libs v6.5.7] (https://github.com/infinum/eightshift-libs/releases/tag/6.5.7) and [Frontend Libs v8.6.2](https://github.com/infinum/eightshift-frontend-libs/releases/tag/8.6.2)) copy code from [wrapper.php](https://github.com/infinum/eightshift-frontend-libs/blob/develop/blocks/init/src/Blocks/wrapper/wrapper.php) into your project. ::: @@ -100,7 +100,7 @@ echo Components::render( true ); ``` -:::Note +:::note Setting the `$useComponentDefaults` to `true` will save you the trouble of setting a lot of additional properties by using default values defined in your manifest. ::: @@ -117,7 +117,7 @@ To make the Card component look even better, we'll use some of the powerful prop 'wrapperSpacingBottomLarge' => 50, ``` -:::Note +:::note For the list of all available properties, look at the Wrapper's `manifest.json`. :::