# Theme Convert Blocks Styles for admin view

**URL:** https://forum.pinegrow.com/t/theme-convert-blocks-styles-for-admin-view/5566
**Category:** WordPress
**Created:** [August 23, 2021, 11:56am UTC](https://forum.pinegrow.com/t/theme-convert-blocks-styles-for-admin-view/5566 "2021-08-23T11:56:50Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ryanb](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@ryanb](https://forum.pinegrow.com/u/ryanb)
#### Post date: [August 23, 2021, 11:56am UTC](https://forum.pinegrow.com/t/theme-convert-blocks-styles-for-admin-view/5566/1 "2021-08-23T11:56:50Z")

</div>

When you create a block for Gutenberg. The styling is correct on the front end but the back in in Gutenberg builder the styling is not showing properly.

 ![2021-08-23_07-55-24](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/b/bd64dbca179b297573274085eeff3e2f97f67005.jpeg)

 ![2021-08-23_07-56-21](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/b/b77c7b84ed8d2c28864f3dce7a243c7dec4de150.jpeg)

---

<div class="post-metadata">

### Author: ![Emmanuel](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/emmanuel/32/6294_2.png) [@Emmanuel](https://forum.pinegrow.com/u/Emmanuel)
#### Post date: [August 23, 2021, 12:45pm UTC](https://forum.pinegrow.com/t/theme-convert-blocks-styles-for-admin-view/5566/2 "2021-08-23T12:45:42Z")

</div>

> **[Block | Pinegrow Web Editor](https://pinegrow.com/docs/wordpress/actions/block/#styling-the-block)**
>
> Use Block Smart action to turn any HTML element into a WordPress visual editor block.

The styles must also be defined for the admin interface. This is one of the less pleasant aspects of building blocks, knowing that the backend already has predefined styles etc… and that it is not recommended at all to load a full CSS framework (Bootstrap/Tailwind/Foundation) in the admin.

Note: I’m talking about the layout/grid mostly, as inline styles related to colors/bg color and so on can be visible on the backend and frontend.

Short: this is not a bug, but a feature 🙂