Title: FSE Program Block Theme Switching Summary Author: annezazu Published: October 5, 2021 Last modified: December 19, 2023 --- [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 2:19 pm _on_ October 5, 2021 Tags: [fse-outreach-experiment ( 20 )](https://make.wordpress.org/test/tag/fse-outreach-experiment/), [fse-outreach-program ( 111 )](https://make.wordpress.org/test/tag/fse-outreach-program/), [fse-testing-summary ( 27 )](https://make.wordpress.org/test/tag/fse-testing-summary/) # FSE Program Block Theme Switching Summary This post is a summary of blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. theme switching exploration for the FSE outreach program. This was the first of its kind, enabling folks to share very early feedback on something that has yet to be robustly defined. Thank you to everyone who participated, whether through sharing feedback directly or sharing the exploration with others.  Shout out to [@richtabor](https://profiles.wordpress.org/richtabor/) [@elmastudio](https://profiles.wordpress.org/elmastudio/) [@anariel-design](https://profiles.wordpress.org/anariel-design/) who officially got badges for responding, despite having engaged with surveys the program has done in the past.  Big thank you to [@piermario](https://profiles.wordpress.org/piermario/) for [the Italian translation](https://it.wordpress.org/team/2021/09/28/esplorazione-per-il-programma-fse-aiuto-con-il-futuro-passaggio-tra-temi-a-blocchi/) and [@greenshady](https://profiles.wordpress.org/greenshady/) for the [WP Tavern article](https://wptavern.com/fse-program-insights-into-switching-between-block-themes), which both help bring the exploration to even more folks. **High level summary** Overall, the current experience proves to be frustrating and inconsistent, especially when taking into account custom block styles, keeping customized templates, etc. Thinking long term about what folks would want to be able to have across themes, there was mass consensus around being able to retain templates, template parts, and menus. There was somewhat mixed feedback around whether Global Styles should persist as some saw those as differentiating a theme. When it came to ideas for how to best manage the switching process, it quickly became clear that there’s a balance to strike between not adding too much friction to the process while also offering users options to pick and choose what can come with them when they switch. Ideally, there can be a simple and visual way to intuitively guide users and help them take advantage of the power of what block themes unlock without discouraging them with too many options.  **On templates and template parts** There was mass agreement around the desire to keep customized templates and template parts across themes, with many expressing surprise and frustration at the current experience. This was previously [documented and discussed here](https://github.com/WordPress/gutenberg/issues/31954) as part of an earlier call for testing. > _I’m very surprised that any templates I’ve created are tied to the theme that > was active when I created them. I’d expect that my custom templates should remain > applied to pages when the new theme is active, instead of being disregarded. I’m > not sure why templates are omitted when a theme is changed. _ > @richtabor in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2037). > _I would like to be able to use templates and templates that I have created and > saved, no matter which theme that is active. I know that I can view them under > appearance templates/template parts, open them, copy the code and paste it into > a new template, but I don’t think that is a good experience. It should be easier._ > @poena in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2030). **On menus** Similar to templates and template parts, this was another area that folks inherently expected would persist across changing block themes.  > _An issue I’ve ran into now a few times when trying out different Full Site Editing > themes is that losing menu data is frustrating. I think as a non-technical user > it would be confusing, because you are prompted to “Add an existing menu”, which > I would think would be my menu from the last theme I was using. _ > @timothyblynjacobs in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2018) > _I think it is important that navigation blocks that I have set up remains. The“ > Add existing menu” feature in the navigation block assumes that I have already > created a menu in the navigation screen. If I only setup the navigation block > as part of a headerHeader The header of your site is typically the first thing > people will experience. The masthead or header art located across the top of your > page is part of the look and feel of your website. It can influence a visitor’s > opinion about your content and you/ your organization’s brand. It may also look > different on different screen sizes. template part in the previous theme, then > I can’t re-apply or reuse that navigation block. Perhaps navigation blocks should > also work the other way around? I mean why can’t I select a name for my navigation > block as I create it in the editor, save that in isolation like I can save the > site blocks in isolation, and have that navigation menuNavigation Menu A theme > feature introduced with Version 3.0. WordPress includes an easy to use mechanism > for giving various control options to get users to click from one place to another > on a site. present on the navigation screen? _ > @poena in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2030). > _Keeping any menus created in the Site Editor available would be important, I > think this is one of the biggest issues right now. _ > @elmastudio in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2038). **On Global Styles** Global Styles left folks a bit split with some seeing them as being theme dependent and others wanting the option to carry settings/styles across themes. [There’s currently a discussion around what can and can’t be standardized](https://github.com/WordPress/gutenberg/issues/29568) which will impact how this could be implemented.  > _I see Global Styles tied to the theme, but it could be helpful if some common > settings are taken from one theme to the next. _ > @elmastudio in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2038). > _Understandably global styles settings would adapt when a theme is changed (just > like the customizerCustomizer Tool built into WordPress core that hooks into most > modern themes. You can use it to preview and modify many of your site’s appearance > settings.) – and I like how my custom GS settings persist when I change back to > a theme (just like the customizer as well). _ > @richtabor in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2037). > _When you export the demo and import it to the other installation, theme.jsonJSON > JSON, or JavaScript Object Notation, is a minimal, readable format for structuring > data. It is used primarily to transmit data between a server and web application, > as an alternative to XML. file styles are not imported. As a theme developer, > I would love to develop one theme with different demos for example. When I export > the demo file I would love that global and block type styles are exported too > and imported to other installations._ > @anariel-design in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2032) > _Have the option to keep Global styles modifications. Perhaps a kind of dialog > box that shows up when entering the Site Editor listing adjustments I made to > the previous theme, asking if I wanted to keep these adjustments or to start anew._ > @paaljoachim in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2003). > _One question that keeps me up at night is how cross-theme compatibility will > work on the content level. Default block output should translate from one theme > to the next with little or no issues. However, custom block styles, font sizes, > colors, and the full range of presets are already a problem area. _ > @greenshady in this [WP Tavern article](https://wptavern.com/fse-program-insights-into-switching-between-block-themes). **On ideas for how to manage the process** Outside of a desire for the experience to be overall easier and more seamless, the following ideas were shared with a split in terms of folks who wanted decisions upfront vs after switching:   * Create a [directory for templates and template parts](https://github.com/WordPress/gutenberg/issues/34081), similar to block plugins or patterns, to make it easier to keep and reuse various templates/template parts. * Offer an option to pick and choose what you want to keep before switching themes. * Make switching easy upfront but, after switching, offer an option to import various items from the previous theme.  * Offer a side by side visual comparison of various parts of a theme before switching( templates, patterns, etc).  * Offer a way to import a color palette or template into your current theme so you don’t have to switch fully but can take advantage of different pieces.  > _I have experimented with one theme but figured out along the way that it does > not have the patterns or finished templates or something else I had hoped for. > Instead of creating the patterns and templates myself I switch themes. When I > click to switch a theme I get a warning message saying that switching themes will > remove the adjustments I made to the current active theme, but I have an option > to save these adjustments in a kind of twilight zone between one theme and another. > I select to save changes I made, and notice that these carry over to the new theme > that I activate. I check and notice that the changes do carry over. I am relieved > that I am able to create adjustments in one theme and have these with me to the > next time…In the Site Editor I can check out what the new theme offers and when > I feel ready for it I can either say yes to bringing over the changes or no because > I notice that the new theme has what I need. _ > @paaljoachim in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2003). > _I actually don’t want to be prompted with having to make several decisions_ _as > soon as I activate a new theme. I would find that stressful. I want to take my > time. I want to understand what the differences are between the themes, and what > changes I need to make. Perhaps there would be a side-by-side comparison of common > page templates_ _like page, single post, home? Like a revision?  _ > @poena in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2030). > _It needs to be easier for the users. They already needed to deal with the domain, > hosting, choosing a theme etc. _ > @anariel-design in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2032) > _It could also be awesome to pull a color palette and drop it into an existing > theme. Sort of like having a Colour Lovers directory to pick color schemes from > but keep all the other bits. This could be fun for people who can recognize a > palette that they like but would never be able to handpick all those colors. I’ve > often seen color schemes that I’d love to use from other themes but didn’t like > other things about them. _ > @greenshady in this [WP Tavern article](https://wptavern.com/fse-program-insights-into-switching-between-block-themes). **On reasons for switching and the experience** Of the various questions folks could answer, some touched on both reasons for switching and the current experience. I’ve listed each response below since only a few folks addressed this area specifically. I’m also including images from [@greenshady](https://profiles.wordpress.org/greenshady/)’ s post where he took a simple blog post with some custom block styles, gradient colors, and font sizes and compared the output across three different themes highlighting current problems with theme switching. [[ [[ [[ > _To see prebuilt template layouts (could be done in a template mosaic view to > where I can choose various prebuilt layouts instead of switching themes). To have > a base that I want to start from. A design that I would like to use and modify._ > @paaljoachim in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2003). > _I think the most common scenario is a missing functionality in one theme like > WooCommerce support. Next would be outdated design and lack of updates and support > from the theme author. _  > @elmastudio in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2038). > _When I switched to the Quadrat I mostly lost everything that I set up in the > Clove theme. That means, About page doesn’t look anything similar, colors, fonts > are now from the Quadrat theme and button style too. From the user’s side, this > is very confusing. If u ever used Elementor for example, and many are using it > they are used to the similar overflow. If I create a template and change the look > and styles and switch to any other theme this template will look the same and > it will remain available. _ > @anariel-design in [this comment](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/#comment-2032) > _I am not one for switching themes. Since I learned how to design for WordPress > well over a decade ago, I have never moved from one theme to the next. At least > not in the same way that the average user would. Instead, every time I have added > a new coat of paint on my websites, I have simply switched over the foundation > to whatever I had been working on at the given moment. WordPress themes, for me, > were always just an iteration upon the last project…The first thing I do when > testing any theme is to load a demo post. Lately, this has been the “Welcome to > the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. > The editor improves the process and experience of creating new content, making > writing rich content much simpler. It uses ‘blocks’ to add richness rather than > shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) > Editor” test post. The primary question: Can I read the content comfortably? If > I do not get past this stage, I simply deactivate the theme. _ > @greenshady in this [WP Tavern article](https://wptavern.com/fse-program-insights-into-switching-between-block-themes). **What’s next?** [@critterverse](https://profiles.wordpress.org/critterverse/) is exploring how to approach these flows from a design perspective and has been following along as feedback has come in. You can expect to see a more in depth design exploration shared soon enough with some of these pieces of feedback and ideas integrated in! I’ll flag this in the outreach program channel when the time comes and will see how we can explore these experiences in future calls for testing.  [#fse-outreach-experiment](https://make.wordpress.org/test/tag/fse-outreach-experiment/), [#fse-outreach-program](https://make.wordpress.org/test/tag/fse-outreach-program/), [#fse-testing-summary](https://make.wordpress.org/test/tag/fse-testing-summary/) ### Share this: * [ Threads ](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/?share=threads) * [ Mastodon ](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/?share=bluesky) * [ X ](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/?share=x) * [ Facebook ](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/?share=linkedin) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F10%2F05%2Ffse-program-block-theme-switching-summary%2F%23respond&locale=en_US) ### Like this: Like Loading… ### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/test/2021/10/05/fse-program-block-theme-switching-summary/?output_format=md#respond)󠁿 You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftest%2F2021%2F10%2F05%2Ffse-program-block-theme-switching-summary%2F&locale=en_US) to post a comment. # Post navigation [← Week in Test – 4 Oct 2021](https://make.wordpress.org/test/2021/10/04/week-in-test-4-oct-2021/) [5.9 End-to-End (e2e) Strategy Session Summary →](https://make.wordpress.org/test/2021/10/06/5-9-end-to-end-e2e-strategy-session-summary/)