# Radicle + Full Site Editing **URL:** https://discourse.roots.io/t/radicle-full-site-editing/25109 **Category:** radicle **Tags:** gutenberg, fse **Created:** 2023-04-05T20:15:05Z **Posts:** 11 ## Post 1 by @ajisilva — 2023-04-05T20:15:05Z What are the best practices for Full Site Editing using Radicle? I tried adding the html templates files to `resources/views/templates/index.html` but it does not activate the editor. It does however work when the html files are located in `public/content/themes/radicle/templates/index.html` although that seems to go against the idea of having the templates located in the `resources/views` directory. --- ## Post 2 by @strarsis — 2023-04-05T20:39:45Z I have not tried Radicle yet, but as it is based off of Sage, this Sage 10 FSE template may be useful: > **[GitHub - strarsis/sage10-fse: Sage 10 theme adjusted for Gutenberg Full Site...](https://github.com/strarsis/sage10-fse)** > > Sage 10 theme adjusted for Gutenberg Full Site Editing (FSE) - GitHub - strarsis/sage10-fse: Sage 10 theme adjusted for Gutenberg Full Site Editing (FSE) --- ## Post 3 by @ajisilva — 2023-04-05T21:04:35Z Ahh interesting. Thanks for the link! --- ## Post 4 by @ben — 2023-04-05T22:23:15Z I haven’t yet looked into FSE with Radicle. Are you wanting to use a combination of Blade templates and FSE templates, or are you wanting a strictly FSE setup for your theme? It _might_ not be possible for the `templates/` directory that FSE is expecting to be compatible with Radicle’s top level `resources/` directory. --- ## Post 5 by @ajisilva — 2023-04-05T22:50:21Z In this particular instance, I was exploring a strictly FSE setup. Mostly out of curiosity to see if FSE could be a viable tool for certain clients. Seems like maybe right now Radicle and FSE are not compatible. I imagine it won’t be a high priority for Radicle to integrate with FSE soon right? I’ll continue to explore the codebase and see what I can learn. --- ## Post 6 by @ben — 2023-04-05T23:48:20Z It’s likely a bit incompatible right now but we can figure out a way to make it not so complicated to use FSE instead of Blade. There’s this PR from @strarsis for Acorn that has some good discussion in it: [Template hierarchy filter: Preserve existing paths by strarsis · Pull Request #141 · roots/acorn · GitHub](https://github.com/roots/acorn/pull/141) The comment about unbinding the [template filters](https://github.com/roots/acorn/blob/4d902cc6fca9134b97a6b95ccdbe9ae05a1d1575/src/Roots/Acorn/Sage/SageServiceProvider.php#L31-L32) is probably the way to go, but you will likely need to use the `public/content/themes/radicle/templates/` directory instead of one within `resources/`. While it isn’t a high priority right now, if there’s a demand for an FSE setup then I will absolutely revisit all of this. --- ## Post 7 by @ajisilva — 2023-04-06T03:20:50Z Ok, I can confirm that patching in the pull request from @strarsis and removing the `block-templates` item from the `remove` array in `config/theme.php` will allow FSE with the caveat that the templates are located in `public/content/themes/radicle/templates/index.html` Lost a few hours before realizing `block-templates` theme support was being removed by default :sweat_smile: --- ## Post 8 by @strarsis — 2023-04-06T13:08:47Z > [@ajisilva](#): > > `block-templates` theme support was being removed by default This happened to me twice as well as to others, so I added an additional note about this to the PR and Sage 10 FSE theme --- ## Post 10 by @cim — 2023-04-21T08:21:15Z The solution offered here works for me too (so far, not tested a lot) > [@ben](#): > > f there’s a demand for an FSE setup then I will absolutely revisit all of this. Yes, I think an option for FSE out of the box is definitely worth having, both for Sage and Radicle --- ## Post 11 by @strarsis — 2023-04-21T20:01:52Z If some things are useful in [GitHub - strarsis/sage10-fse: Sage 10 theme adjusted for Gutenberg Full Site Editing (FSE)](https://github.com/strarsis/sage10-fse), please put/request them into Sage/acorn upstream. The PR/patch for the template loader is the most critical part. There are some new `bud` features that help with managing block template features like block style registration I had not fully looked into yet. Also the editor styles extraction `bud` [extension](https://github.com/talss89/wp-editor-query-plugin) (thanks @talss89) is very useful.