# Full Site Editing (not with Gutenberg Editor capabilities)

**URL:** <https://forum.pinegrow.com/t/full-site-editing-not-with-gutenberg-editor-capabilities/6424>\
**Category:** Pinegrow WP\
**Created:** [March 26, 2022, 10:20am UTC](https://forum.pinegrow.com/t/full-site-editing-not-with-gutenberg-editor-capabilities/6424 "2022-03-26T10:20:18Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![jonroc](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/jonroc/32/2805_2.png) [@jonroc](https://forum.pinegrow.com/u/jonroc)\
**Post date:** [December 10, 2022, 6:19pm UTC](https://forum.pinegrow.com/t/full-site-editing-not-with-gutenberg-editor-capabilities/6424/15 "2022-12-10T18:19:03Z")

</div>

I’m also already creating all new themes in FSE… I get that some people will always use the old way but there are too many benefits with FSE (even in beta) not to use it. I’m not really sure how PG can adapt to FSE as most of it will require building patterns/templates in WP first. The only thing that would be nice while PG “waits to see” is [automatically exporting files in the parts/templates directories](https://forum.pinegrow.com/t/have-fse-directories-automatically-include-files-in-wp/7329) to WP as those are the standard directories for FSE templates/parts. I believe the patterns folder already automatically exports the files in it.

---

_[View the full topic](https://forum.pinegrow.com/t/full-site-editing-not-with-gutenberg-editor-capabilities/6424)._