Skip to content

Commit db2a1ca

Browse files
committed
fixing note issue
1 parent 3fcb68b commit db2a1ca

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

website/blog/2023-09-05-wrapper-as-a-standalone-component.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,15 +12,15 @@ hide_table_of_contents: false
1212
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?
1313
<!--truncate-->
1414

15-
:::Note
15+
:::note
1616
[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.
1717
:::
1818

1919
## What are WordPress templates?
2020

2121
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.
2222

23-
:::Note
23+
:::note
2424
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.
2525
:::
2626

@@ -30,7 +30,7 @@ Depending on your setup, you might still use those as they are still a core part
3030

3131
Thanks to the `Components` helper, we can easily `render()` any component in our template.
3232

33-
:::Note
33+
:::note
3434
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).
3535
:::
3636

@@ -72,7 +72,7 @@ use InfinumLibsVendor\EightshiftLibs\Helpers\Components;
7272

7373
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`.
7474

75-
:::Note
75+
:::note
7676
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.
7777
:::
7878

@@ -100,7 +100,7 @@ echo Components::render(
100100
true
101101
);
102102
```
103-
:::Note
103+
:::note
104104
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.
105105
:::
106106

@@ -117,7 +117,7 @@ To make the Card component look even better, we'll use some of the powerful prop
117117
'wrapperSpacingBottomLarge' => 50,
118118
```
119119

120-
:::Note
120+
:::note
121121
For the list of all available properties, look at the Wrapper's `manifest.json`.
122122
:::
123123

0 commit comments

Comments
 (0)